some machines cant access server

[bookouri]

I have a win2k member server. My 2000 workstations have no problem accessing shares on it. Sporadically we are finding win98 workstations that can not access the server, and I have another win2k member server that gets and error stating that it cant access the machine because the server service is not started on that server. The server is working fine. I can ping the servername and the server ip, I can ping -a and resolve the ip to the correct servername from the win98 workstations and the other win2k server. I dont get any other errors to point me toward solving this problem. I have tried putting an lmhosts file on the machines even though I can ping them and the names are resolving correctly, but I can not get these isolated machines to access the server.


Any suggestions would be appreciated...

 

[bookouri]

to add to the above.... I can also see the server in network neighborhood from all the machines that cant access its resources. I have also tried uninstalling and reinstalling the networking components on a couple of the machines and it made no difference.

 

[rubmyback]

I am having similar difficulty and could use some suggestions. I have 2 Win2k servers and an NT 4.0. My Win2K clients have no problem with access or login, but sporatically either a 9x unit is not allowed to access a server or the user that is using the 9x unit is locked out, or both. (Since I have two W2K Servers the users are not always totally knocked off of the network, but just one server.) Generally, rebooting gets a pc to come back with access to the network, but I have to unlock the user account if a user gets locked out. (I hope this is constructive. It sounds to me like bookouri and I may have the same or a similar problem.)

 

[NYR]

Microsoft has a article "Q306927" that might give some clues.

 

[rubmyback]

We are getting either just no connection, or an access lockout type message. Maybe my particular error has to do with the way 95/98/Me accesses the server and logs in vs. 2000 clients.

 

[bookouri]

The MS article mentioned above basically says to unjoin your machine from the network, join WORKGROUP and then after rebooting, re-join the network to reset the clients credentials. I tried it with a 98 machine and there's no change in the client. If I try to access the server, start - run - \\servername\c$, the client still sits there for at least three or four minutes and then times out with no errors, but the connection just doesnt work...

any other suggestions????