You have to change it on the clients - i.e. the DHCP server options, not WINS.
------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA > -----Original Message----- > From: Weatherly, Rob [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 16, 2002 10:35 AM > To: NT 2000 Discussions > Subject: RE: logging onto wrong server > > > Well thanks to both of you I will look into that > Should I change that for each WINS server or if I change one will it > change the others? > > -------------------------------- > Rob Weatherly > -------------------------------- > > -----Original Message----- > From: Malcolm Reitz [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 16, 2002 10:05 AM > To: NT 2000 Discussions > Subject: RE: logging onto wrong server > > We changed our NetBIOS node type, as Roger describes, for that exact > reason. It seems to work pretty well in keeping our legacy clients > logging into the local DCs. > > Malcolm > -----Original Message----- > From: Roger Seielstad [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 16, 2002 9:06 AM > To: NT 2000 Discussions > Subject: RE: logging onto wrong server > > Sorry - its standard non-ad authentication. The machine queries WINS, > gets a > list of up to 25 domain controllers, and starts at the top of > the list. > There is no order to the list, so its quite possible that the first > server > listed is on the other side of the globe. > > One possible solution is to change your NetBIOS node type > (option 044 or > 046 > in DHCP) from H-node (0x8) to p-node, which will go broadcast first, > then > WINS. > > ------------------------------------------------------ > Roger D. Seielstad - MCSE > Sr. Systems Administrator > Inovis - Formerly Harbinger and Extricity > Atlanta, GA > > > > -----Original Message----- > > From: Weatherly, Rob [mailto:[EMAIL PROTECTED]] > > Sent: Monday, December 16, 2002 9:53 AM > > To: NT 2000 Discussions > > Subject: RE: logging onto wrong server > > > > > > That is kind of a blanket statement. > > I figured something was wrong. > > Can anyone elaborate and give me some ideas of what to check > > or look for > > > > -------------------------------- > > Rob Weatherly > > -------------------------------- > > > > -----Original Message----- > > From: Roger Seielstad [mailto:[EMAIL PROTECTED]] > > Sent: Monday, December 16, 2002 9:49 AM > > To: NT 2000 Discussions > > Subject: RE: logging onto wrong server > > > > Without the AD Client, that's going to happen - there's no > easy way to > > force > > it to authenticate locally. > > > > With the AD client, if its still doing that, I'd suspect > that your AD > > sites > > aren't correctly configured. > > > > ------------------------------------------------------ > > Roger D. Seielstad - MCSE > > Sr. Systems Administrator > > Inovis - Formerly Harbinger and Extricity > > Atlanta, GA > > > > > > > -----Original Message----- > > > From: Weatherly, Rob [mailto:[EMAIL PROTECTED]] > > > Sent: Monday, December 16, 2002 9:44 AM > > > To: NT 2000 Discussions > > > Subject: logging onto wrong server > > > > > > > > > Problem: > > > I have a large amount of windows 98 workstations that are > > > authenticating > > > to a remote DC that is in a different Site > > > With or without the AD client the workstations will > > > authenticate to the > > > same remote DC. > > > > > > Environment: > > > 3 Sites > > > 1 corp. > > > 2 remote > > > All FSMO roles are at corp. site including PDC emulator > > > 1 GC at each site > > > > > > Question: > > > Why are these 98 workstations going to a remote DC to > > > authenticate when > > > the PDC emulator is here (local)? They are actually going to > > > a different > > > site to logon. Normally this may not be a big deal but I > > need to have > > > then pull files from there "logon server" as they logon, so > > > if they are > > > logging on to a server at a different site it will take a > > long time to > > > copy the files needed as you could imagine. > > > > > > > > > -------------------------------- > > > Rob Weatherly > > > -------------------------------- > > > > > > > > > ------ > > > You are subscribed as [EMAIL PROTECTED] > > > Archives: http://www.swynk.com/sitesearch/search.asp > > > To unsubscribe send a blank email to %%email.unsub%% > > > > > > > ------ > > You are subscribed as [EMAIL PROTECTED] > > Archives: http://www.swynk.com/sitesearch/search.asp > > To unsubscribe send a blank email to %%email.unsub%% > > > > ------ > > You are subscribed as [EMAIL PROTECTED] > > Archives: http://www.swynk.com/sitesearch/search.asp > > To unsubscribe send a blank email to %%email.unsub%% > > > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to %%email.unsub%% > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to %%email.unsub%% > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to %%email.unsub%% > ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
