Problem using \\vboxsrv from 3rd party utility

[Giangi]

Hi!

I do heavily use FreeCommander almost everywhere, I use it portable.

Since the last two/three Virtual Box build I cannot use it anymore on VM to reference a shared folder as \\vboxsvr.
At first I thought on a FC problem because I updated it from build 740 to 760 but today I was wrking on an old Win7 vm with build 740 and it's not working!

Right now I'm using the latest VirtualBox 5.2.0 r118431 on a Windows 10 (1703) 64bit host

• I do not have any problem browsing \\vboxsvr from Windows Explorer
• from FreeCommander I can browse \\vboxsvr (I guess it's using some os API)
  
• ...but when I select a folder from the above browse list (or when I type it directly)
  
• ...I get the error "network name cannot be found" (not sure if on a real english system the error is called like this!), the same error one will get when trying to use a mispelled name or a powered off system
  

Is it possibile that something has been changed on the VirtualBox Shared Folders networking??

Addendum: if I map a \\vboxsvr share then I can use it from the mapped drive!

[mpack]

Unless the FreeCommand people can indicate the problem in their source code, and show that it's a VirtualBox problem, then I'm not sure this will go anywhere. As you say, Windows Explorer works, which implies that the VirtualBox feature is working too. There are many instances where simple GA shared folders are slightly less capable then a full network share.

[Giangi]

I posted the same question other their forum, let's see... But do not forget that it was working perfectly since a few VB builds ago...
Thanks

[mpack]

But do not forget that it was working perfectly since a few VB builds ago.

Yes, I did understand that.