LAN here has an NT4 server running Exchange 5.5, and a 2K server just as file & print for now. 2K server is a member server, not even a PDC,BDC, or DC. No ADS.
Users report they regularly get the 'no domain controller/bad password' error starting up and during the day when they reload Win98 mostly. Problem is, they are logging onto the wrong server somehow, and it takes them up to 9 tries to get the right server to respond.
I checked the event logs, and after a user got the bad password message, the NT server does *not* show a failed or successful attempt. The 2K server *does* show a failed login by them, and there are no accounts on that machine since it's not a controller. Try to log in again, and success first time...
Among other things, WINS server shows 1250+ queries, 800 failed/400 successful (I think this is normal, since looking for something not there is what Win98 does as lot..) DHCP is being given out by a Linksys BEFSR41, and WINS is being given out for the NT server, right address, and clients are getting it. This may have started when the NT server got bogged down with hoggy Backup Exec processes (becom.exe using 80% cpu and +380MB ram on a 512M server) that we seem to have solved.
Why are users not logging into the intended PDC/server?
My local guru says go through the process of making this an AD domain, making the NT box a member. He also says check the network. We have 16 users and 7 other devs on a Linksys 24-port switch. Nothing obvious, and pings are fine.
I've shut down the Browser service for now on the 2K server, and set the registry key to not maintain a browser list, hopefully making it NOT a master or backup.
whatcha think?
rick
Users report they regularly get the 'no domain controller/bad password' error starting up and during the day when they reload Win98 mostly. Problem is, they are logging onto the wrong server somehow, and it takes them up to 9 tries to get the right server to respond.
I checked the event logs, and after a user got the bad password message, the NT server does *not* show a failed or successful attempt. The 2K server *does* show a failed login by them, and there are no accounts on that machine since it's not a controller. Try to log in again, and success first time...
Among other things, WINS server shows 1250+ queries, 800 failed/400 successful (I think this is normal, since looking for something not there is what Win98 does as lot..) DHCP is being given out by a Linksys BEFSR41, and WINS is being given out for the NT server, right address, and clients are getting it. This may have started when the NT server got bogged down with hoggy Backup Exec processes (becom.exe using 80% cpu and +380MB ram on a 512M server) that we seem to have solved.
Why are users not logging into the intended PDC/server?
My local guru says go through the process of making this an AD domain, making the NT box a member. He also says check the network. We have 16 users and 7 other devs on a Linksys 24-port switch. Nothing obvious, and pings are fine.
I've shut down the Browser service for now on the 2K server, and set the registry key to not maintain a browser list, hopefully making it NOT a master or backup.
whatcha think?
rick