Hello:
I am having an issue with Shared Folders, using VirtualBox 3.0.2 up to 3.0.8. My host is Fedora 10, and the guest is Windows XP Pro, with SP3. The issue is that when accessing a Shared Folder, it works fine but from time to time, it loses its connection and an error pops up: "The request is not supported" in Windows Explorer. When this happens, the contents of Windows Explorer is empty, and I have to press F5 to refresh a couple of times, then everything comes back and works fine again. So it seems like it's getting disconnected intermittently. Permissions are fine on the Linux host, as I can create files/folders OK. It seems to happen when I'm opening larger files from the guest, when this happens.
I've looked around but I cannot find a solution to this particular problem.
If anybody has any thoughts on this, please let me know.
Thank you very much!
--
Chris
Shared folder, "request is not supported"
-
mrvas
- Posts: 2
- Joined: 1. Feb 2010, 07:34
- Primary OS: Ubuntu other
- VBox Version: OSE other
- Guest OSses: XP and Windows 7
Re: Shared folder, "request is not supported"
Same issue here, Windows XP Pro (SP3) as guest, and Ubuntu 9.10 (x64) as host.
-
aug_aug
- Posts: 1
- Joined: 17. Jun 2011, 17:24
- Primary OS: MS Windows Vista
- VBox Version: OSE other
- Guest OSses: Ubuntu, Windows XP
Re: Shared folder, "request is not supported"
Anyone figure this out? I am having the same issues w/4.0.8 Windows Vista x64 host and Windows XP guest. Intermittent error...
Re: Shared folder, "request is not supported"
This is still an issue with VirtualBox 4.1.6 when running a Windows XP virtual machine under RedHat 5.7. So it looks like nobody gives a crap.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Shared folder, "request is not supported"
I see one report a year and no indications as to what the error is caused by. To fix errors like this it must be reproducible to the point that it can be detected and fixed by the DEVs. So the no one gives a crap is invalid. It is just that no one that knows what to do has seen the error and no one that has this error has provided enough information to be able to reproduce the problem.
Feel free to post a ticket at bugtracker but look for an existing ticket first.
Feel free to post a ticket at bugtracker but look for an existing ticket first.