I have a W2K12 host with a W2K12 DC. Suddenly today, after installing Microsoft Updates and rebooting systems, I started having network problems with VMs.
* No problem with ping or nslookup via the DC's DHCP and DNS from any machine to any machine.
* The ARP tables look OK.
* File and Printer Sharing are enabled everywhere.
* The network is coded as "domain" for domain members and "private" everywhere else.
* The Computer Browser was disabled on both the DC and Host but running on a Windows 8 VM.
* I was getting System Error 6118 on the DC and Host when executing "net view".
* After starting their Computer Browser services, I get Error 53 - well sort of...
Here is the weird Part. I get different results depending upon the user that is logged in to the DC. I log onto the host console as Admin1 but not as Admin2. The difference is that Admin1 is a normal admin account that is an "Administrator" and "Domain Admin" while Admin2 is not (its the "Enterprise Admin".
When I started, Admin1 still had a mapped drive to the Host. It could be umpapped and mapped back no problem. Now, after rebooting, it can no longer be mapped. Here is the current status...
No Drive Map, No Computer Browsers:
----------- Run on . Run on
----------- Host --- DC
Admin1
net view .. . . . . 6118 .. 6118
net view host . . . Ok .... Ok
net view dc . . . . 53 .... 53
Admin2
net view .. . . . . - . 6118
net view host . . . - . 53
net view dc . . . . - . Ok
No Drive Map, Computer Browser Running:
----------- Run on . Run on
----------- Host --- DC
Admin1
net view .. . . . . Ok - Ok
net view host . . . Ok - 53
net view dc . . . . Ok - Ok
Admin2
net view. . . . . . - . Ok
net view host . . . - . 53
net view dc . . . . - . Ok
(Sorry - the Technet Submit screen doesn't allow tabbing very well.)
Error6118 = No Browser
Error50 = Request is not supported
Error53 = The network path was not found
There are times after stopping the Computer Browser Services that Admin got Error 50 when doing "net view".
I have tried this with the firewall off, Symantec uninstalled too, and the WAP powered down.
I always figured "net view" was fairly low level like ping and nslookup, except for actually accessing a remote share, which could give an error 5 if unauthenticated. I do not understand how one user could get Error 53 and another connect Ok.
The fact that one user connected ok all along while it had a permanent map to the Host, and could no longer after disconnecting the map and rebooting, tends to suggest that mechanisms near boot time are different than after a steady state has been reached.
Can anyone explain why I get an Error 50 at times, and then a 53 when pings and security have not changed? And how having a mapped drive gave one user access but after removing it, access was completely lost?
Thanks,
Bob.
* No problem with ping or nslookup via the DC's DHCP and DNS from any machine to any machine.
* The ARP tables look OK.
* File and Printer Sharing are enabled everywhere.
* The network is coded as "domain" for domain members and "private" everywhere else.
* The Computer Browser was disabled on both the DC and Host but running on a Windows 8 VM.
* I was getting System Error 6118 on the DC and Host when executing "net view".
* After starting their Computer Browser services, I get Error 53 - well sort of...
Here is the weird Part. I get different results depending upon the user that is logged in to the DC. I log onto the host console as Admin1 but not as Admin2. The difference is that Admin1 is a normal admin account that is an "Administrator" and "Domain Admin" while Admin2 is not (its the "Enterprise Admin".
When I started, Admin1 still had a mapped drive to the Host. It could be umpapped and mapped back no problem. Now, after rebooting, it can no longer be mapped. Here is the current status...
No Drive Map, No Computer Browsers:
----------- Run on . Run on
----------- Host --- DC
Admin1
net view .. . . . . 6118 .. 6118
net view host . . . Ok .... Ok
net view dc . . . . 53 .... 53
Admin2
net view .. . . . . - . 6118
net view host . . . - . 53
net view dc . . . . - . Ok
No Drive Map, Computer Browser Running:
----------- Run on . Run on
----------- Host --- DC
Admin1
net view .. . . . . Ok - Ok
net view host . . . Ok - 53
net view dc . . . . Ok - Ok
Admin2
net view. . . . . . - . Ok
net view host . . . - . 53
net view dc . . . . - . Ok
(Sorry - the Technet Submit screen doesn't allow tabbing very well.)
Error6118 = No Browser
Error50 = Request is not supported
Error53 = The network path was not found
There are times after stopping the Computer Browser Services that Admin got Error 50 when doing "net view".
I have tried this with the firewall off, Symantec uninstalled too, and the WAP powered down.
I always figured "net view" was fairly low level like ping and nslookup, except for actually accessing a remote share, which could give an error 5 if unauthenticated. I do not understand how one user could get Error 53 and another connect Ok.
The fact that one user connected ok all along while it had a permanent map to the Host, and could no longer after disconnecting the map and rebooting, tends to suggest that mechanisms near boot time are different than after a steady state has been reached.
Can anyone explain why I get an Error 50 at times, and then a 53 when pings and security have not changed? And how having a mapped drive gave one user access but after removing it, access was completely lost?
Thanks,
Bob.