B
Brent B.
I have a system running Windows 2K server SP4 in workgroup mode - not AD. If
someone logs in on the server, using any of the valid local users, then the
other systems in the workgroup when they try to access the resources of the
server - \\server\shareddata they get an error saying it is not
accessible. The network name cannot be found.
From the workstation, I can ping the server by name and by IP and vice
versa - I can ping the from the server the name of the workstation and IP.
If I try to use the net use command to map a drive letter to the server's
shared data, I'm prompted to give a password which I do but then a system
error 67 is returned and I'm dropped back to the command line.
TCP/IP is the only protocol being used. Wins is not implemented and lmhost
file lookup is not enabled.
The only way I've been able to clear out this problem is by rebooting the
server and making sure no one logs in on the server console otherwise it
gets hosed again.
Any response would be appreciated.
Brent
someone logs in on the server, using any of the valid local users, then the
other systems in the workgroup when they try to access the resources of the
server - \\server\shareddata they get an error saying it is not
accessible. The network name cannot be found.
From the workstation, I can ping the server by name and by IP and vice
versa - I can ping the from the server the name of the workstation and IP.
If I try to use the net use command to map a drive letter to the server's
shared data, I'm prompted to give a password which I do but then a system
error 67 is returned and I'm dropped back to the command line.
TCP/IP is the only protocol being used. Wins is not implemented and lmhost
file lookup is not enabled.
The only way I've been able to clear out this problem is by rebooting the
server and making sure no one logs in on the server console otherwise it
gets hosed again.
Any response would be appreciated.
Brent