WinNt 4 Workstation join W2K3 Domain

Hello all,

I'm trying to join a WinNT 4.0 WKS to a W2K3 Domain, but it keeps telling
me:
No domain controller found.

The WKS is on a different subnet. WKS(192.168.100.0) SRV(192.168.200.0)

This is what I've tried so far:
Installed Active Directory Client for WinNT. (No need to configure?)
Ping - Works perfectly on both sides.

http://support.microsoft.com/?kbid=150800
I've edited my lmhosts file on the WKS the way the articel describes it and
nbtstat -c shows that it's ok.

http://support.microsoft.com/?kbid=823659/
I changed the following things:
Domain member: Require strong (Windows 2000 or later) session key ->
Disabled
Domain member: Digitally encrypt or sign secure channel data (always) ->
Disabled
Microsoft network client: Digitally sign communications (always) -> Disabled
Microsoft network server: Digitally sign communications (always) -> Disabled
Network access: Do not allow anonymous enumeration of SAM accounts ->
Disabled
Network access: Do not allow anonymous enumeration of SAM accounts and
shares -> Disabled
Network security: Lan Manager authentication level -> Send LM & NTLM - use
NTLMv2 session security if negotiated

Is there anything else I can do? There must be something I've missed.

Thanks in advance for any help.
Michel Metzler

Make sure the NT Workstation has SP4 or later.

"Michel Metzler" <(E-Mail Removed)> wrote in message
news:uHiuZxL%(E-Mail Removed)...
> Hello all,
>
> I'm trying to join a WinNT 4.0 WKS to a W2K3 Domain, but it keeps
telling
> me:
> No domain controller found.
>
> The WKS is on a different subnet. WKS(192.168.100.0)
SRV(192.168.200.0)
>
> This is what I've tried so far:
> Installed Active Directory Client for WinNT. (No need to configure?)
> Ping - Works perfectly on both sides.
>
> http://support.microsoft.com/?kbid=150800
> I've edited my lmhosts file on the WKS the way the articel describes
it and
> nbtstat -c shows that it's ok.
>
> http://support.microsoft.com/?kbid=823659/
> I changed the following things:
> Domain member: Require strong (Windows 2000 or later) session key ->
> Disabled
> Domain member: Digitally encrypt or sign secure channel data
(always) ->
> Disabled
> Microsoft network client: Digitally sign communications (always) ->
Disabled
> Microsoft network server: Digitally sign communications (always) ->
Disabled
> Network access: Do not allow anonymous enumeration of SAM accounts ->
> Disabled
> Network access: Do not allow anonymous enumeration of SAM accounts and
> shares -> Disabled
> Network security: Lan Manager authentication level -> Send LM & NTLM -
use
> NTLMv2 session security if negotiated
>
> Is there anything else I can do? There must be something I've missed.
>
> Thanks in advance for any help.
> Michel Metzler
>
>

make sure they are i the same subnet. It could be the name resolution issue
too. quoted from http://www.ChicagoTech.net
"No domain server was available to validate your password"

Symptoms: when trying to logon a domain from win9x, you may receive a
message "The following error occurred while loading protocol number 0. Error
38: The computer name you specified is already in use..." and then "No
domain server was available to validate your password".

Resolution: 1) make no two host name in the network. 2) check WINS and make
sure no one host uses two IPs. If it does, delete all of them and reboot the
computer.
--
For more and other information, go to http://www.ChicagoTech.net


Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
Networking Solutions, http://www.chicagotech.net/networksolutions.htm
VPN Solutions, http://www.chicagotech.net/vpnsolutions.htm
VPN Process and Error Analysis, http://www.chicagotech.net/VPN%20process.htm
VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
This posting is provided "AS IS" with no warranties.
"Michel Metzler" <(E-Mail Removed)> wrote in message
news:uHiuZxL%(E-Mail Removed)...
> Hello all,
>
> I'm trying to join a WinNT 4.0 WKS to a W2K3 Domain, but it keeps telling
> me:
> No domain controller found.
>
> The WKS is on a different subnet. WKS(192.168.100.0) SRV(192.168.200.0)
>
> This is what I've tried so far:
> Installed Active Directory Client for WinNT. (No need to configure?)
> Ping - Works perfectly on both sides.
>
> http://support.microsoft.com/?kbid=150800
> I've edited my lmhosts file on the WKS the way the articel describes it
> and nbtstat -c shows that it's ok.
>
> http://support.microsoft.com/?kbid=823659/
> I changed the following things:
> Domain member: Require strong (Windows 2000 or later) session key ->
> Disabled
> Domain member: Digitally encrypt or sign secure channel data (always) ->
> Disabled
> Microsoft network client: Digitally sign communications (always) ->
> Disabled
> Microsoft network server: Digitally sign communications (always) ->
> Disabled
> Network access: Do not allow anonymous enumeration of SAM accounts ->
> Disabled
> Network access: Do not allow anonymous enumeration of SAM accounts and
> shares -> Disabled
> Network security: Lan Manager authentication level -> Send LM & NTLM - use
> NTLMv2 session security if negotiated
>
> Is there anything else I can do? There must be something I've missed.
>
> Thanks in advance for any help.
> Michel Metzler
>