Windows share keeps disconnecting

[jcenter]

Hi,

I recently installed VB 2.2.4 on Ubuntu 9.04. I created a WinXP VM & registered it with AD. Everything works, but the windows share that has My Documents keeps disconnecting. I constantly getting a message that the volume has gone offline. Does anyone have an idea why this is occurring & what I can do to fix it?

Thanks.

-John

[Perryg]

Screen saver? Power management?

[jcenter]

No, neither of these. The disconnect occurs in less than a minute once the VM comes up. If I force sync, it will work for about a minute, then disconnect again.

[Perryg]

Maybe you should explain a little better what and exactly how you are sharing the "volume".
Also if you could explain what you meant about registering it with "AD", that would help as well.

[jcenter]

Thanks for your help! I registered the VM as a workstation in our AD. I followed the directions in the advanced section of the VBox user manual to mount the shares: copied over the VBoxGINA.dll & ran the VBoxManage command to set up the AD credentials. This all worked pretty well. I was able to log into our AD domain & mount the volume that holds the share that contains "My Documents". Within a short while, I got the first popup saying that I was now offline from that share. I hadn't sync'd with it, so I no longer had an offline copy of my files & directories. I enabled working offline & began to sync, but after it reconnected & began to sync, it disconnected again. It did this over & over again, syncing a little more each time. Meanwhile, I can access the web, etc. Any ideas?

Thanks, again.

-John

[baf]

What are your guests network settings? Nat or bridged?

[Perryg]

And this is in the Windows guest that you are trying to setup the share. I would first look at the adapter that you are using in VBox. You might get better performance switching to the Intel Pro/1000. How is the data transfer in the guest? Does it seem adequate? And does it kick you out of the domain or just the share? Also you can setup a ping with the T switch ping <ipaddress> -t to the computer with the folder you are mapping to watch for replies and see if they are all over the place with the timing.

[jcenter]

The guest VM is NAT'd. Within the guest, ping times vary from 1ms to over 500ms. From the host, times vary from less than 1ms to over 4ms. I'll download the Intel Pro driver & give that a try.

[vbox4me2]

It might be an AD policy issue when it comes to NAT'd shares.

[jcenter]

I changed the NIC to the Intel Pro & installed a new driver. It worked a little better, but not by much. I then changed the networking from NAT to bridged & it worked much better. I was able to complete an entire sync w/o much of a problem. It stayed up for about 20 minutes, syncing everything except 3 files. I ran it again & it sync'd those, too. I guess NAT has more issues when it comes to Windows shares in VBox.

Thanks.

-John

[wilbur.harvey]

I am having the same problems.
My host is Jaunty, my guest is Windows 7.
The network adapter is bridged (I couldn't get NAT to work at all)
The adapter is the Pro/1000 MT Desktop.

The windows network goes offline after a few minutes and I cannot access anything on the network.
Then after a few more times trying it will suddenly work.
Basically the same as the other people are experiencing.

[vbox4me2]

Can be anything from power save modes to lan drivers and their settings, I'm inside a virtual machine right now via rdp, bridged, with multiple shares active all day, the one thing I do extra to keep shares alive is to have explorer open all the time listing(selected) on a share. I do see security entries in the eventlog of my server of periodic re-authentication but thats normal for windows.

[jcenter]

Once I installed the new Intel driver, I made sure to turn off any power saving settings. I also did this in the control panel. If I had to do this over again, I would have unchecked the APCI setting on the VM, just to be on the safe side.

HTH

-John