BDC Authenication after W2K upgrade

[NYR]

Hello,
We had recently upgraded our NT4 domain to W2K. We got a new server, added it to the domain as a BDC, promoted it to PDC and upgraded it to W2K server (mixed mode). All went well.

Now, it appears that the BDC is authenciating the clients, not the new W2K PDC server(running the "set" command in DOS). These are W2K Pro desktops. I also found when I took my laptop, joined it to the domain, I was authenicated by the PDC. The other machines who were already in the domain authenicate to the BDC.

We have changed the DNS settings in the clients to reflect the changes. We have run DCDiag, and Netdiag on the server, all checks passed.

Any ideas why or how to fix....
Thanks.

 

[NYR]

Now we have tried a few more machines, all still authenicating to the BDC..anybody else had this happen after upgrading?

 

[GlenJohnson]

Is browsing running in the desktop's services? Disable it if they are. Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@nellsgiftbox.com


"What really happens is trivial in comparison to what could occur."
Robert von Musil (1880-1942); Austrian author.

 

[NYR]

Yeah, browsing is enabled. But when if I disable that, it will prevent me from browsing the network... How will disabling that allow me to authenticate to the PDC?

 

[GlenJohnson]

I had browsing enabled on my w2k machines. They thought other w2k machines were the master browser, so I couldn't get them to join the domain. Once I figured this out, by disabling browsing, they joined the domain in no time. These were only the w2k machines. In your event log, you should see who the machine thinks the master browsers are. Good luck. Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@nellsgiftbox.com


"What really happens is trivial in comparison to what could occur."
Robert von Musil (1880-1942); Austrian author.

 

[NYR]

Great, thanks for the info. I will be heading out there tomorrow and try that. I also found a Microsoft article: Q309273 that might be helpful as well.