This may get a little confusing so I will try my best to explain it correctly. Here at my employer we have two facilty's. One facilty is where the computer room is and all the servers. The second facilty is about 100 yards away in which connects to the network via a wireless bridge. we are running windows 2000 server. Anybody running windows 98 in our second facilty has a terrible time getting validated on our network. If you are running windows 2000 or above you have no problems getting validated on our network. We use DHCP to give out IP adresses and the second facilty's system are getting IP addresses cause they can surf the web. Now I have checked everbody's machine that have windows 98 and the setings are exact. They (systems with windows 98) don't get validated on our network so they have to reboot 5-6 times before they get a logon script which then gets them into our network. If this is confusing I am sorry but there is so much to tell. Any clue what is wrong? By the way our facilty where the servers are? No problem what so ever with any operating system getting validated on the network.

It look like a dns problem. Manually enter a static DNS server ip address in the tcpip settings. Danny

I forgot to mention that. We have tried that route and didn't work. When the user has trouble getting a logon script he or she calls me and I can delete them off the server and usually that works. Remeber this ony happens with windows 98 machines. Windows 2000 or xp the are no issues. Do you think its a timing issue with the BIOS time and the server time?