Shared Folder Issue [FIXED IN SVN]

[cmccarron]

Environment

Host: Windows 7 64bit Virtual Machine: Windows 7 32bit

It seems that something is wrong with Shared Folder mapping/access. The previous version (4.3.28) would allow me to share both network drives and local drives to the virtual machine. I can map both local and network drives from the host computer but when I try to access a shared folder mapped to a network drive I get the following error: "F:\ is not available The parameter is incorrect.". Access shared folders mapped to host local drives/folders seems to be working fine.

F:\ is a Host Network drive mapped to a Windows Domain Controller H:\ is a Host Local drive Z:\ is a Host Network drive mapped to a Windows Domain Controller

If more information is needed, logs etc, please let me know what you need and I will provide it.

Thanks VirtualBox Team for all the hard work on this software.

[cmccarron]

Error Message when access Shared Folder mapped to Host Network Drive

[cmccarron]

Windows XP Guest Error

[cmccarron]

VM Mapped Shared Folders

[cmccarron]

VM Shared Folder Settings

[cmccarron]

Host Drive Mapping

[cmccarron]

Windows 7 Log File

[cmccarron]

Windows XP Guest Log File

[cmccarron]

This problem also effects my Windows XP Guest and has been an issue in both Windows 7 and XP since 5.0 Beta.

[sunlover]

I did some tests and can not reproduce the problem with VirtualBox 5.0.0, i.e. the Windows 32 guest can access shared folder mapped to a host network drive.

I wonder what is different in your setup. Do you run VirtualBox as admin or as a regular user on the host?

Maybe you could get a procmon log on the host?

​https://technet.microsoft.com/en-us/library/bb896645.aspx

Filter can be set to "Path contains F:\" (where f: is the _host_ drive mapped to the domain controller). Then the guest should access the corresponding shared folder to reproduce the problem. The procmon log will contain all accesses to the host drive and result codes. Maybe this will help to find out what is wrong.

[cmccarron]

I am running Virtualbox as a user that is part of the Administrator group. I am not having this problem with VirtualBox 4.3.28.

Thanks for your help.

[cmccarron]

Virtual Machine Config File

[cmccarron]

I disconnected the F: and Z: drive then browsed using
vboxsvr and received the following error.

[cmccarron]

Error trying to Access via
vboxsvr

[cmccarron]

When I ran ProcMon on the host I did not get any results. So I ran it on the guest and got a result. It is attached.

[cmccarron]

Guest Procmon Log access F:\

[cmccarron]

Guest Procmon Log access using
vboxsvr\Projects

[sunlover]

Unfortunately the procmon log does not contain any accesses to any host paths. Could you please retry:

• start the VM where you get the error;
• start elevated procmon on the host ("Run as administrator")
• Open Filter/Filter.. menu in procmon
• in the dialog remove all conditions
• then add a new condition: "Path" "contains" "F:\" then "Include"

of course if F:\ is not the host drive letter mapped to the domain controller, then replace F:\ with correct drive letter

• click 'Add' and 'OK'
• in the guest try to access the corresponding shared folder (where the host drive F: is mapped) to reproduce the problem
• make sure that procmon shows some events related to F:
• attach the new procmon file

Thanks.

[cmccarron]

Did you look at GuestLogfile.7z and GuestLogfile2.7z? They were generated on the Guest and do have some entries in it. Working on creating a new host procmon log file on the host.

[cmccarron]

Ok, I added a filter where the path contains ElecWorkfile and got some results. I have updated the Procmon.7z log file.

[cmccarron]

Updated Host Procmon Log File

[sunlover]

Thanks for the updated procmon host log. It shows the "incorrect parameter" error. However it is still not clear why the error occurs.

Would it be possible for you to get similar procmon logs for VBox 4.3.28 and 4.3.30?

[rastakajakwanna]

I ran into the same issue but using Vagrant (​ticket what pointed me here)

[cmccarron]

Yes, sorry for the delay, I am out of town. I can provide Procmon for 4.3.28 and 4.3.30. I will try to get them uploaded before Sunday.

[cmccarron]

Attached is the Procmon log file from v4.3.28. It was captured using a VPN connection but I was able to successfully browse the F: drive which is a network drive on the host.

[cmccarron]

ProcMon from v4.3.28 (successfull)

[cmccarron]

ProcMon from v4.3.30 (successfull)

[cmccarron]

Replying to sunlover:

Thanks for the updated procmon host log. It shows the "incorrect parameter" error. However it is still not clear why the error occurs.

Would it be possible for you to get similar procmon logs for VBox 4.3.28 and 4.3.30?

Done

[sunlover]

Thanks. I'll compare these logs. Unfortunately I still could not reproduce the problem.

[sunlover]

Please test if this build works for you:

https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101732-Win.exe

[bird]

I've reproduced and (hopefully) fixed the issue now. It only happens if the server directory we're trying to list contains a lot of files and is a windows server (samba shows no such issues). (The buffer size of the NtQueryDirectoryInformation call had to be reduced to 64KB or less for it to work. Seems the server side of things return larger buffers and handles it in a non obvious way. No trouble if the directory only contains a handful of files.)

Could you please try the following build and report back whether it fixes the problem?

https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101738-Win.exe

[cmccarron]

I just tried build 5.0.1-101732 and it worked. I have uploaded a log file for that version. I will download 101738 and try that one right now. Thanks for your help in fixing this issue.

[cmccarron]

Procmon from v5.0.1-101732

[cmccarron]

Build 5.0.1-101738 also works. ProcMon log file is attached.

Thank you.

[cmccarron]

Procmon from v5.0.1-101738

[bird]

Great! Thanks for testing!!

[cmccarron]

Ok there appears to still be something wrong. While it is working, when I try to view another drive attached to the root share from the domain controller I get 0 results.

[cmccarron]

Z: drive on host

[cmccarron]

Z: drive on guest

[cmccarron]

Procmon from v5.0.1-101738 Browsing Z: Drive

[cmccarron]

Replying to bird:

Great! Thanks for testing!!

There is still something wrong. It does not show any files or folders if you are mapped to a root share. If I am sharing
elecworkfile from the server and map Z: to
elecworkfile when you open z: you get no results. If I map F: to
elecworkfile\projects, I can see all files and folders.

Thanks

[bird]

Yeah, definitely something wrong. But it seems to depend on the server side. I've redone the fix and I think this time it will work for all servers. Here's a new testbuild:

https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101771-Win.exe

[cmccarron]

Everything seems to be working now.

Thank you!

[Frank Mehnert]

Fix is part of VBox 5.0.2.