Andornot Consulting Inc.
Home Page
Home Page
 |  | 

Tuesday, May 22, 2007

Virtual PC 2007 and NVIDIA nForce networking conflict on Vista

I have Vista 32-bit on an Intel x86 NVIDIA nForce4 motherboard. Ever since I installed Vista, networking has been... dicey. Any time the computer went to sleep/hibernate, networking would no longer work. Some BSODs on wake. Installing the KB931671 Windows Update reduced the number of BSODs, but not the problem itself.

Updating to the latest nForce4 drivers (15.00, released Feb 5 2007) caused networking to simply stop working from startup. No ethernet, no internet, no connection to other workgroup computers, no ping to gateway even (transmit failed, error code 1231).

Through a process of trial and error, I found that disabling Virtual Machine Networking Services on the nForce Networking Controller, plus netsh interface ipv6 reset from the command line, restored networking. (Virtual Machine Networking Services are installed by Virtual PC 2007 as part of its Virtual Machine Additions.)

So I'm left with no network connectivity on my virtual machines. Perhaps I should count myself lucky I have connectivity on the host, but instead I think, no, a steaming pile of curse words followed by a new NIC will be the answer.

UPDATE June 8, 2007 - Bought a new network card and disabled nVidia networking. All problems resolved. Cost? $35.

Labels: ,

2 Comments:

Anonymous said...

Let's say that Vista and networking do not come along... well, in my case! Running OpenSuse 10.2 64B w/Wmware 1.0.3 on AMD 5000+ w/Nforce 570 and only my Vista virtual machine dosen't run find on the network... If I do change manually static route, and delete the 0.0.0.0 static route that Vista add (don't know why 'cause it's in the dynamic routing table by default...) I do loose my default gateway... And once again, I've got some error code 1231 on the ping command... My Win XP/Windows 2000 dosen't have any probs with the same operations, so... Let's say that we're waiting for Vista SP1!

9:34 AM  
Anonymous said...

i have this exact problem. after working with the internet company replacing everything else, i gave up. i've recently discovered, however, that if you bring up network connections and show properties on the internet connection.. disable ip4 and let the 1231 errors roll for a few seconds. then, open properties again and re-enable it and the pings come right back.

when the problem happens, i lose ping to everything.. dns servers, even the modem itself.

i hope a permanent fix comes out sometime.

3:32 PM  

Post a Comment

<< Home