virtualbox.org

Virtualbox 4.1.12r77245
Host 64 Bit Windows 2012 R2 64GB Memory Available
Guest Additions not installed
Guest: OMG: 64 Bit Windows 2008 r2 16GB Memory Available
Guest: CTA: 32 Bit Windows 2003 4GB Memory Available

We found this issue while performing a Disaster Recovery Test. I have two guest machines restored from StorageCraft backups with Storage Craft's Virtual Boot program which utilizes Virtualbox.

OMG is the primary domain controller and file sharing server. We tested in the production environment and found that client PC's, as well as the other virtualized server (like CTA), are unable to access file sharing on OMG. When navigating to the UNC (\\OMG) we get an error message "Windows cannot find "\\omg" check the spelling and try again." and when executing "net view \\omg" at the CLI we get a system error 53, "The network path was not found."

Client PC's do receive an IP address from DHCP on OMG, they also successfully resolve host names with DNS running on OMG. If OMG navigates to \\CTA it can access the file shares on CTA. Client PC's can access the file shares on CTA.

Currently I am running both servers in a lab environment on an internal network. They are the only two VM's on the internal network. In this environment I am getting the same results. My boss believes something is blocking NETBIOS over TCP/IP. Any thoughts are greatly appreciated.

Can you ping the IPs? If yes, this is not a Virtualbox problem. If you can't, make sure firewalls are off and try again.
Try using the FQDN and make sure you get a DNS resolution of it.

Yes, I can ping the IPs. It's very strange since the physical machine doesn't have this problem. It's only the virtualized version of this machine that I cannot access the shares on. I can access the shares on the other virtual server, just not OMG.

Update:

I was also having stability issues with this VM. It turned out the Virtualbox and Extensions were not the same version. I installed the extensions that matched the version of Virtualbox we are using, rebuilt the VM from the backups, and it would still display a critical error/guru meditation. I switched the motherboard chipset to ICH9 and the server stopped crashing. Still could not access file shares. I installed the guest additions and still could not access the file shares. Just to reiterate, the physical server does not have this problem. There are two servers that were virtualized in the same fashion. Server A can see it's own file shares, but neither server B, nor any client computers on the network, are able to connect to the shares. When I try to connect via UNC path, or ip address, I receive an error message. Both server A, B, and client computers CAN navigate to the file shares on server B. Has anyone ever seen behavior like this before?

When I run net use \\servera, or \\192.168.10.6 (server A's IP address) from server B, I get error 67, the network name cannot be found. Pinging Server A by name results in a successful ping of the correct IP address.