I've got a Win98SE machine in my network that is refusing to see the NT domain. The funny part is that once I get past this error message: No domain server was available to validate you password. You may not be able to gain access to some network resources. I am able to double-click on Network Neighborhood and see all the machines in the network. My original problem was that I couldn't access any of the machines per say, because it would never give me a login field when I tried to access protected shares on the network (just the password field). I've checked all the settings against other Win98SE machines that are working on the network, and everything checks out. Any ideas?

Have you tried removing all of the network settings and putting them back again after a restart? Also, is the server allowing the PC, as in have you set only certain workstations as allowing access? Another potential prob is the liscencing - I can't remember how this is set up in NT4 but I believe it has its own control panel, but if you don't have enough enabled you can't log all machines on. Good luck!

Thanks rhawkes241, I'll give those suggestions a try in the morning, they just locked me out of the room :p. I'll let you know what happens then.

I removed all the goodies under Network Neighboorhood, and re-installed them. Nothing has changed, I'm still able to see the network and use the internet, but I can't login to the NT domain. The server isn't set to not allow and certain workstations, so that should be fine. I believe our licenses are in order as well. I should mention that this computer is using a Linksys 802.llg PCI card. I have tested laptops using wireless to access the NT network without any problems.

I am experiencing the same problem. The only difference is that I am using the Linksys 802.11g notebook adapter, but otherwise the symptoms are the same. Previously, I was using an Addtron adapter, and had no problems, so I feel fairly certain that it is a Linksys problem of some kind that is preventing proper network connection at the time that the logon is processed.

Interesting...someone should notify Linksys of the issue (unless they are already aware of it).