NT4

I have recently replace one of our Domain Controllers that housed all the
Operation Master roles. I transfered them to another DC during the process
and eventual transfered them back once the new sever was in place. Eveything
works fine in my network with the exception of the one NT4 workstation and
two NT4 member servers. I get an error saying no domain controller could
be found when attempting to logon but will have to use cashed credentials.
These machines can ping everything my name and ip address without a problem.
The resolution I used was that I created a LMHost file and imported that. Is
there a better solution to this problem. They can browse to every computer
in the network except the new replaced DC. What is the best way to resolve
this issue.

You'll need to edit the lmhosts file to reflect the
new DC as the primary.

"George Schneider" <(E-Mail Removed)> wrote in message
news7FAE60E-02EC-4ADE-8945-(E-Mail Removed)...
>I have recently replace one of our Domain Controllers that housed all the
> Operation Master roles. I transfered them to another DC during the
> process
> and eventual transfered them back once the new sever was in place.
> Eveything
> works fine in my network with the exception of the one NT4 workstation and
> two NT4 member servers. I get an error saying no domain controller could
> be found when attempting to logon but will have to use cashed credentials.
> These machines can ping everything my name and ip address without a
> problem.
> The resolution I used was that I created a LMHost file and imported that.
> Is
> there a better solution to this problem. They can browse to every
> computer
> in the network except the new replaced DC. What is the best way to
> resolve
> this issue.

thats exactly what I did. But I never had to do this prior to swamping out
the DC. I replaced it with a new DC that had the same name. I went through
the whole demotion process with the old server before promoting the new one.
I heard some peiople suggest to me to insatll DSClient to get it to see the
w2000 domain. I mean what I'm doing is woking its just curious that i never
had to this prior.

"Michael Giorgio - MS MVP" wrote:

> You'll need to edit the lmhosts file to reflect the
> new DC as the primary.
>
> "George Schneider" <(E-Mail Removed)> wrote in message
> news7FAE60E-02EC-4ADE-8945-(E-Mail Removed)...
> >I have recently replace one of our Domain Controllers that housed all the
> > Operation Master roles. I transfered them to another DC during the
> > process
> > and eventual transfered them back once the new sever was in place.
> > Eveything
> > works fine in my network with the exception of the one NT4 workstation and
> > two NT4 member servers. I get an error saying no domain controller could
> > be found when attempting to logon but will have to use cashed credentials.
> > These machines can ping everything my name and ip address without a
> > problem.
> > The resolution I used was that I created a LMHost file and imported that.
> > Is
> > there a better solution to this problem. They can browse to every
> > computer
> > in the network except the new replaced DC. What is the best way to
> > resolve
> > this issue.
>
>
>

This time you swapped out the PDC role holder

Open a dos prompt and run nbtstat -c on the NT client
and post the results. You can mask the tcp/ip and domain
name but make sure the masked domain name is the same
amount of characters as the actual NetBIOS name of your
new W2k domain.

"George Schneider" <(E-Mail Removed)> wrote in message news:
> thats exactly what I did. But I never had to do this prior to swamping
> out
> the DC. I replaced it with a new DC that had the same name. I went
> through
> the whole demotion process with the old server before promoting the new
> one.
> I heard some peiople suggest to me to insatll DSClient to get it to see
> the
> w2000 domain. I mean what I'm doing is woking its just curious that i
> never
> had to this prior.
>
>

The following is the result of the Netbios Remote Cache. Everything listed
has the same host address. Wouldn't the LMHOST file i imported to get it to
work interfee with this.



NAME TYPE HOST ADDRESS LIFE [SEC]
SERVER1 <03> Unique XXX.X.X.X -1
SERVER1 <00> Unique XXX.X.X.X -1
SERVER1 <20> UNIQUE XXX.X.X.X -1
DOMAIN.COM <1C> GROUP XXX.X.X.X -1
DOMAIN.COM. <03> UNIQUE XXX.X.X.X -1
DOMAIN.COM. <00> UNIQUE XXX.X.X.X -1
DOMAIN.COM. <20> UNIQUE XXX.X.X.X -1

"Michael Giorgio - MS MVP" wrote:

> This time you swapped out the PDC role holder
>
> Open a dos prompt and run nbtstat -c on the NT client
> and post the results. You can mask the tcp/ip and domain
> name but make sure the masked domain name is the same
> amount of characters as the actual NetBIOS name of your
> new W2k domain.
>
> "George Schneider" <(E-Mail Removed)> wrote in message news:
> > thats exactly what I did. But I never had to do this prior to swamping
> > out
> > the DC. I replaced it with a new DC that had the same name. I went
> > through
> > the whole demotion process with the old server before promoting the new
> > one.
> > I heard some peiople suggest to me to insatll DSClient to get it to see
> > the
> > w2000 domain. I mean what I'm doing is woking its just curious that i
> > never
> > had to this prior.
> >
> >
>
>
>

I don't think Domain.com is the NetBIOS name
of your domain, that looks like the FQDN. I
suspect the default is domain for example.

Also I would add a line in your lmhosts file
to
point towards your PDC role holder e.g.,
XXX.X.X.X "Domain \0x1B" #PRE

Make sure there are 20 characters in the between
the quotation marks or this won't work; you have
to add spaces after the domain name to reach 15
characters for the domain name. The \ should be
the sixteenth character.

Once you make the change open a dos prompt
and run nbtstat -R to purge and reload the cache
then nbtstat -c to verify your changes are correct.

"George Schneider" <(E-Mail Removed)> wrote in message news:
> The following is the result of the Netbios Remote Cache. Everything
> listed
> has the same host address. Wouldn't the LMHOST file i imported to get it
> to
> work interfee with this.
>
>
>
> NAME TYPE HOST ADDRESS LIFE [SEC]
> SERVER1 <03> Unique
> -1
> SERVER1 <00> Unique
> -1
> SERVER1 <20> UNIQUE XXX.X.X.X -1
> DOMAIN.COM <1C> GROUP XXX.X.X.X -1
> DOMAIN.COM. <03> UNIQUE XXX.X.X.X -1
> DOMAIN.COM. <00> UNIQUE XXX.X.X.X -1
> DOMAIN.COM. <20> UNIQUE XXX.X.X.X -1
>

my lmhost file works great. I guess there was some confussion. Is this the
only way to get a nT4 machine to be able to log onto the domain and see this
new domain controller.

"Michael Giorgio - MS MVP" wrote:

> I don't think Domain.com is the NetBIOS name
> of your domain, that looks like the FQDN. I
> suspect the default is domain for example.
>
> Also I would add a line in your lmhosts file
> to
> point towards your PDC role holder e.g.,
> XXX.X.X.X "Domain \0x1B" #PRE
>
> Make sure there are 20 characters in the between
> the quotation marks or this won't work; you have
> to add spaces after the domain name to reach 15
> characters for the domain name. The \ should be
> the sixteenth character.
>
> Once you make the change open a dos prompt
> and run nbtstat -R to purge and reload the cache
> then nbtstat -c to verify your changes are correct.
>
> "George Schneider" <(E-Mail Removed)> wrote in message news:
> > The following is the result of the Netbios Remote Cache. Everything
> > listed
> > has the same host address. Wouldn't the LMHOST file i imported to get it
> > to
> > work interfee with this.
> >
> >
> >
> > NAME TYPE HOST ADDRESS LIFE [SEC]
> > SERVER1 <03> Unique
> > -1
> > SERVER1 <00> Unique
> > -1
> > SERVER1 <20> UNIQUE XXX.X.X.X -1
> > DOMAIN.COM <1C> GROUP XXX.X.X.X -1
> > DOMAIN.COM. <03> UNIQUE XXX.X.X.X -1
> > DOMAIN.COM. <00> UNIQUE XXX.X.X.X -1
> > DOMAIN.COM. <20> UNIQUE XXX.X.X.X -1
> >
>
>
>

No. There is broadcast name resolution (assuming
they are on the same subnet) and the Windows
Internet Naming Service (WINS). Immediately
after a failed attempt at logging on to the domain
open a dos prompt and run nbtstat -c. What do
you now see?

Also, the NT machine will cache the DC that responds
to its logon a request and use that DC. It is also possible
there are security features on the new DC preventing the
machine from setting up a secure channel with the new
DC.

"George Schneider" <(E-Mail Removed)> wrote in message
news:...
> my lmhost file works great. I guess there was some confussion. Is this
> the
> only way to get a nT4 machine to be able to log onto the domain and see
> this
> new domain controller.
>
> "Michael Giorgio - MS MVP" wrote:
>
>> I don't think Domain.com is the NetBIOS name
>> of your domain, that looks like the FQDN. I
>> suspect the default is domain for example.
>>
>> Also I would add a line in your lmhosts file
>> to
>> point towards your PDC role holder e.g.,
>> XXX.X.X.X "Domain \0x1B" #PRE
>>
>> Make sure there are 20 characters in the between
>> the quotation marks or this won't work; you have
>> to add spaces after the domain name to reach 15
>> characters for the domain name. The \ should be
>> the sixteenth character.
>>
>> Once you make the change open a dos prompt
>> and run nbtstat -R to purge and reload the cache
>> then nbtstat -c to verify your changes are correct.