Windows 98 laptop does not find domain controller when moved to differentsite in AD

Hi,

I have 7 site Windows 2003 network using AD at 5 sites and windows
domains at 2 sites. When a laptop user comes from one of the child AD
site to forest root site, it can't logon because domain controller was
not found. Below is my configuration.

Main Site:
enterprise.local

Child AD Sites:
chicago.enterprise.local
la.enterprise.local
peoria.enterprise.local
newyork.enterprise.local
detroit.enterprise.local

NT 4.0 sites:
atlanta <<== domain netbios name
charlotte

Each site is using a /24 ip subnet. e.g. 192.168.100.0 through
192.168.108.0. Each site has it's own dns & domain controller. DNS zone
is delegated for child domain to remote site controller.

When a windows 98 laptop user from detroit site visits main site, he
changes his ip address to 192.168.100.X but leaves WINS and DNS settings
pointing to his site(192.168.105.0). The name resolution seems to work
fine since I can ping anywhere to anywhere using name. Just can't logon
to domain.

Any advise,

Thanks,
Sam Munzani

W98 is not really very good at using AD/DNS, even if it has the AD client
installed. A W98 client is usually set to log into an NT domain, using the
domain's Netbios name. Your W98 client probably tries to log into the domain
controller in Detroit. So it will send a NS request for <detroit 1c>
to the Detroit WINS server. Can you resolve names in the Detroit WINS
database from HO?

"msnews.microsoft.com" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I have 7 site Windows 2003 network using AD at 5 sites and windows
> domains at 2 sites. When a laptop user comes from one of the child AD
> site to forest root site, it can't logon because domain controller was
> not found. Below is my configuration.
>
> Main Site:
> enterprise.local
>
> Child AD Sites:
> chicago.enterprise.local
> la.enterprise.local
> peoria.enterprise.local
> newyork.enterprise.local
> detroit.enterprise.local
>
> NT 4.0 sites:
> atlanta <<== domain netbios name
> charlotte
>
> Each site is using a /24 ip subnet. e.g. 192.168.100.0 through
> 192.168.108.0. Each site has it's own dns & domain controller. DNS zone
> is delegated for child domain to remote site controller.
>
> When a windows 98 laptop user from detroit site visits main site, he
> changes his ip address to 192.168.100.X but leaves WINS and DNS settings
> pointing to his site(192.168.105.0). The name resolution seems to work
> fine since I can ping anywhere to anywhere using name. Just can't logon
> to domain.
>
> Any advise,
>
> Thanks,
> Sam Munzani

All my 2003 servers are in backward compatible mode and do have WINS in
place. When I brought this PC to main site, I also tried setting the domain
to main site domain name. No matter what I try, it doesn't want to logon.

I have 3 more such laptops in same boat.

Thanks,
Sam
"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> W98 is not really very good at using AD/DNS, even if it has the AD
client
> installed. A W98 client is usually set to log into an NT domain, using the
> domain's Netbios name. Your W98 client probably tries to log into the
domain
> controller in Detroit. So it will send a NS request for <detroit 1c>
> to the Detroit WINS server. Can you resolve names in the Detroit WINS
> database from HO?
>
> "msnews.microsoft.com" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi,
> >
> > I have 7 site Windows 2003 network using AD at 5 sites and windows
> > domains at 2 sites. When a laptop user comes from one of the child AD
> > site to forest root site, it can't logon because domain controller was
> > not found. Below is my configuration.
> >
> > Main Site:
> > enterprise.local
> >
> > Child AD Sites:
> > chicago.enterprise.local
> > la.enterprise.local
> > peoria.enterprise.local
> > newyork.enterprise.local
> > detroit.enterprise.local
> >
> > NT 4.0 sites:
> > atlanta <<== domain netbios name
> > charlotte
> >
> > Each site is using a /24 ip subnet. e.g. 192.168.100.0 through
> > 192.168.108.0. Each site has it's own dns & domain controller. DNS zone
> > is delegated for child domain to remote site controller.
> >
> > When a windows 98 laptop user from detroit site visits main site, he
> > changes his ip address to 192.168.100.X but leaves WINS and DNS settings
> > pointing to his site(192.168.105.0). The name resolution seems to work
> > fine since I can ping anywhere to anywhere using name. Just can't logon
> > to domain.
> >
> > Any advise,
> >
> > Thanks,
> > Sam Munzani
>
>

Can't think of any reason why it would not work if you change it to the
local domain. Did you also set it to look at the local WINS and DNS server?

"Sam Munzani" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> All my 2003 servers are in backward compatible mode and do have WINS in
> place. When I brought this PC to main site, I also tried setting the
domain
> to main site domain name. No matter what I try, it doesn't want to logon.
>
> I have 3 more such laptops in same boat.
>
> Thanks,
> Sam
> "Bill Grant" <not.available@online> wrote in message
> news:(E-Mail Removed)...
> > W98 is not really very good at using AD/DNS, even if it has the AD
> client
> > installed. A W98 client is usually set to log into an NT domain, using
the
> > domain's Netbios name. Your W98 client probably tries to log into the
> domain
> > controller in Detroit. So it will send a NS request for <detroit
1c>
> > to the Detroit WINS server. Can you resolve names in the Detroit WINS
> > database from HO?
> >
> > "msnews.microsoft.com" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Hi,
> > >
> > > I have 7 site Windows 2003 network using AD at 5 sites and windows
> > > domains at 2 sites. When a laptop user comes from one of the child AD
> > > site to forest root site, it can't logon because domain controller was
> > > not found. Below is my configuration.
> > >
> > > Main Site:
> > > enterprise.local
> > >
> > > Child AD Sites:
> > > chicago.enterprise.local
> > > la.enterprise.local
> > > peoria.enterprise.local
> > > newyork.enterprise.local
> > > detroit.enterprise.local
> > >
> > > NT 4.0 sites:
> > > atlanta <<== domain netbios name
> > > charlotte
> > >
> > > Each site is using a /24 ip subnet. e.g. 192.168.100.0 through
> > > 192.168.108.0. Each site has it's own dns & domain controller. DNS
zone
> > > is delegated for child domain to remote site controller.
> > >
> > > When a windows 98 laptop user from detroit site visits main site, he
> > > changes his ip address to 192.168.100.X but leaves WINS and DNS
settings
> > > pointing to his site(192.168.105.0). The name resolution seems to work
> > > fine since I can ping anywhere to anywhere using name. Just can't
logon
> > > to domain.
> > >
> > > Any advise,
> > >
> > > Thanks,
> > > Sam Munzani
> >
> >
>
>