virtualbox.org

Host: Vista 64 bit
Guest: Windows XP 32 bit
Network Settings: PCnet-FAST III (NAT)
Other Settings: VT-X/AMD-V, Nested Paging, 3D Acceleration

Problem: Connection to my mapped drives to work server stops working or unable to find.

I installed VB and installed initially with PCnet-FAST III (NAT). I was able to find and connect to servers at my work and so I mapped the drives. Everything worked perfectly. Then after I shutdown VB and restarted, the drives were unable to be found and typing in the hard pathway to the server returned a negative result. So I thought it was the network setting so I uninstalled VB and reinstalled using PCnet-FAST II (NAT). Again I was able to find the servers and map without any problem. Thinking this solved the problem I shut down and then restarted VB. Unfortunately I could not reconnect again to the drives. Anyone else having this problem? I am not too familiar with bridging and the other network options but since it worked upon initial installation and settings then I would think it should be fine upon reboot of VB...

Try the Intel/PRO1000T Server adapter. XP has the drivers for that one too. There are quite some reports of failing AMD PCNet adapters with VB, while the Intel ones keep on going. It's the only adapter I use these days for VMs and have not had any issues with them so far.

Which is something I don't get, I only use the pcnet ones (vb 2.08) and they blast the intel ones away, must be vb 2.2 and above that this relates to.

Older versions had some issues with the PCNet adapters too, but it's quite selective too. It depends on the environment that is in use amongst other variables. Pretty hard to figure out where the exact problem comes from. It's at least worth a shot to try the Intel adapter, as it fixed things before. Sometimes the other way around was needed, where a user used an Intel one and needed to use the PCNet adapter for better connections.

It is quite bizarre, I logged into VB yesterday and it found the mapped drives perfectly and then today Bzzztt!!! Frustrating.. I will try the Intel 1000 server network adapter and report.... sheesh....

Sigh.... no dice...
Maybe the network adapter only connects on every other day... this can be a problem ... any other sugestions?

If possible, check the eventlogs on the server and VM, it might indicate something.

Looked at the logs and did not provide information that could provide a clue. But then again, I am not sure exactly what I am looking for. This whole thing is odd...

Okay update...

I did not mention this before but I brought my computer from home and did not shutdown. I am thinking some network settings were still in place and so when I connected to the work network it did not "flush" the network settings from home. Anyway to make a long story short, I rebooted and now I can connect to my mapped network drives at work.

Hopefully this continues to work but it may change tomorrow....

If not then use ipconfig/release and restart the VM.