Wrong BDC 1

[DRDAVIDBANNER]

Hi,

My company uses Windows NT 4.0 and Workstation, we are currently in the process of moving to Win2k.

I have today received a hard drive with a Win 2k build on it from one of our other offices, although the build is working correctly it is authenticating to the BDC in the other office, this is a problem because there is only a 256k link between the two offices.

I have edited the LMHOST files and enabled it in the TCPIP properties but I still have the same problem, in fact after I edit the LMHOST file the computer (after a restart) re-adds the entries that I removed?!

Does anyone have a solution to this problem, I basically want it to authenticate to the local BDC.

Thanks in advance!

 

[kippy13]

If the local BDC is an NT system and there is an active directory server available then this is the issue.
This is a function of how the
system actually works. Windows 2000 Professional will always logon to an
Active Directory server over a Windows NT server. It's designed that way
(and documented as well). There are good reasons for that. But the answer
is - you cannot "force" a W2KPro to logon to a Windows NT domain controller
as long as there is an AD server available. And - the solution is to
provide your W2KPro machines with AD servers to logon to. That's by
design - and well documented.

If not:
Have you read the information here:

http://support.microsoft.com/defaul...port/kb/articles/q180/0/94.asp&NoWebContent=1

It would probably be usefull to create a LMHOST
file on the client(s) with at least the following entry. This will most
likely solve your problem.

192.1.168.1 <Logon Server> #PRE #DOMomain_name



&quot;Sometimes I do not know but I try hard&quot;- R.F. Haughty 1923

 

[DRDAVIDBANNER]

Thanks for the response.

We are still running in a mixed mode domain. So AD is not setup.

Would the 2000 work station authenticate to a 2000 DC rather than a NT DC??

 

[kippy13]

Hi,
2000 will authenticate to a 2000 server ahead of to an NT server.
Is the Local BDC NT?
If so you have to Upgrade the BDC to
Windows 2000, and establish each remote location as a Site.


&quot;Sometimes I do not know but I try hard&quot;- R.F. Haughty 1923

 

[kippy13]

Hi,
You may also want to take a look at this although I dont think its relevant. Have a read though anf let me know.

http://support.microsoft.com/defaul...port/kb/articles/q181/1/71.asp&NoWebContent=1

I have done a good deal of reading on this in the past while and apparently Windows 2000 will always authenticate to a 2000 server if there is one available and the only workaround is to upgrade the local BDC to 2000.


&quot;Sometimes I do not know but I try hard&quot;- R.F. Haughty 1923

 

[DRDAVIDBANNER]

Kippy your a star, problem solved.

The other office has a 2000 BDC.

I am installing new clients in a brand new office tomorrow and bringing up a Windows 2000 BDC in the new office so it should authenticate to that then.

Thanks again!!!

The Hulk..

 

[kippy13]

That'll solve the problem.
Good luck.

&quot;Sometimes I do not know but I try hard&quot;- R.F. Haughty 1923