Re: W2K Authenticating to NT 4.0 Domain Not working....

From: Bugs the Bunny (michaelremmert@hotmail.com)
Date: 07/31/02 

From: "Bugs the Bunny" <michaelremmert@hotmail.com>
Date: Wed, 31 Jul 2002 15:13:30 -0400

Roy, From my experience, your problem revolves around the way that NT4 and
Win2K resolve names. NT4 uses Netbios, while Win2K used DNS. If I understand
correctly, Netbios is not routable. Therefore the Win2k server / workstation
is not able to resolve the NT4 names. An LMHOSTS file (from my experience
will not work). I believe that you will have to implement a WINS server on
each domain and use that to help resolve the names to the Win2K systems.
Since WINS is routable, it should be able to carry the name resolution to
all of the systems in your entire domain structure.

My problem with this was two sites, Main and Remote. We established a VPN
tunnel between the two locations. Main Site is NT4 domain. Remote site has
Win9x and Win2K Pro workstations. All the Win9s systems can validate a
logon, but the Win2K cannot. When WINS is implemented, then the logon will
succede. Hope this all helps

"roy" <roy.wiggins@smdc.army.mil> wrote in message
news:#vVz72IOCHA.1796@tkmsftngp09...
> I posted this earlier but got no responses... So am trying again...
>
> I have the following scenario:
>
> A: NT Domain P with W2K member Servers
> B: Two way Domain Trusts from Domain P with Doman A; Domain S; Domain C;
> Domain O and Domain K Only Domain O is an W2K domain and it is not in
NATIVE
> mode.
> C: All servers in my NT Domain P use the same WINS server and have no
> LMHOST files.
> D: From any NT 4.X server or workstatin in Domain P I can grant users in
> all the other Domains rights to a local directory.
> E: From any W2K server/workstation in Domain P I can grant users in
Domain
> P/A/O access rights to a local directory.
> F: From any W2K server/workstaion in Domain P I cannot even get a list of
> users from Domains C/S/K.
> G: I immediatly go to an NT 4.0 server/workstation and have no problems.
>
> Any ideas as to where to begin looking?
>
> Roy
>
>
>
>

Relevant Pages

  • 401.2 error
    ... Domain and a Win2k (not on a NT4 WS) ... Logon Failed due to server ...
    (microsoft.public.backoffice.smallbiz)
  • Which one?
    ... It seems that at this point in time, win2k is probably ... they are migrating from NT4 to win2k servers and XP ... Although XP dows have some server ...
    (microsoft.public.cert.exam.mcse)
  • Login failed for user (null). Active Directory issue?
    ... Our client machines are a mix of WIN2K and NT4. ... Our primary production database server is NT4. ... backup system during the upgrade. ...
    (microsoft.public.sqlserver.security)
  • Re: W2K Authenticating to NT 4.0 Domain Not working....
    ... > is not able to resolve the NT4 names. ... I believe that you will have to implement a WINS server on ... > each domain and use that to help resolve the names to the Win2K systems. ... When WINS is implemented, then the logon will ...
    (microsoft.public.win2000.security)
  • RE: Failed to create a trust relationship between NT4 and 2003 AD
    ... For Windows 2000 and 2003 these settings may be applied/configured via ... Digitally sign communications (if server ... With NT4 the only way to verify the settings is with the Regedt32 tool. ... Failed to create a trust relationship between NT4 and 2003 AD ...
    (microsoft.public.windows.server.migration)