Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 252940

Win 2000 Server vm network issue - can't map shared drive

$
0
0

I have a Win 2000 Server SP4 vm on ESXi 5.1. I screwed up and disabled some services I shouldn't have and the vm started BlueSreening on boot.

 

I was able to recover and successfully boot by using the 'Last Known Good Configuration'. I then tried to turn back on any services that appeared to be needed. The server seems to be working ok and I can do everything except map a network drive or access a shared network drive on another server.

 

I can ping other servers. Applications on this server are communicating over the network. DNS is working. Ipconfig information all looks good.

 

If I try and right click on Local Area Connections and select Properties, explorer appears to crash as the desktop resets (All icons disappear and come back). I thought maybe this was a winsock corruption error but I can't follow http://support.microsoft.com/kb/837333 because I can't right click on the Local Area connection successfully. I also tried these commands to reset the winsock with no success:

 

netsh <enter>
interface reset all
routing reset all
routing
dump
bye
exit

 

It seems like everything works except being able to access a shared folder on another server. When I try to map, I get the error: The network location cannot be reached. It displays this error immediately as if it isn't even trying. I see no authentication attempt on the remote server share but I'm not sure if I should see one or not.

 

The command:  net view \\server   yields a 'System Error 53 has occured - the network path was not found'

The command:  net use \\server    yields a 'System Error 1231 has occured - The network location cannot be reached'

 

I'm not sure what else to try. Any ideas? TIA


Viewing all articles
Browse latest Browse all 252940

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>