Re: W2K Authenticating to NT 4.0 Domain Not working....
From: roy (roy.wiggins@smdc.army.mil)
Date: 07/31/02
- Next message: Sean: "Can I restore an event log from backup?"
- Previous message: dontemailme@no.com: "is it possible to share but hide a dir ?"
- In reply to: Bugs the Bunny: "Re: W2K Authenticating to NT 4.0 Domain Not working...."
- Next in thread: Michael Giorgio - MS MVP: "Re: W2K Authenticating to NT 4.0 Domain Not working...."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "roy" <roy.wiggins@smdc.army.mil> Date: Wed, 31 Jul 2002 15:37:35 -0500
You are partially correct. I have a network trace from a W2K system in
Domain P succesfully allowing me to grant privleges in Domain A. I do WINS
replcation with Doman A. I also can succesfully connect to Domain O for
which I have static WINS entries. I see the W2K system actually do an DNS
lookup and an NBT lookup at the same time. It then uses that information to
make a NETBIOS over IP connection. As part of the process, the W2K station,
actually passes my userid to the Trusting DC and then it gets back a list of
users. However, when attempting to contact the DC for the Trusting domains
that fail, it does not pass any credentials or logon ID. What I do not
know, is why the different behavior. It works with Domains I have static
WINS entries and with domains that I have WINS replication. Conversly, it
fails with Domains I have static WINS entries and with Domains I do WINS
replication with.
VR,
Roy
"Bugs the Bunny" <michaelremmert@hotmail.com> wrote in message
news:ehkOHZMOCHA.360@tkmsftngp13...
> 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
> >
> >
> >
> >
>
>
- Next message: Sean: "Can I restore an event log from backup?"
- Previous message: dontemailme@no.com: "is it possible to share but hide a dir ?"
- In reply to: Bugs the Bunny: "Re: W2K Authenticating to NT 4.0 Domain Not working...."
- Next in thread: Michael Giorgio - MS MVP: "Re: W2K Authenticating to NT 4.0 Domain Not working...."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
