[Courtney]

This one is driving me nuts:
We have a remote warehouse using DSL to connect to the HQ domain via Linksys
VPN router. If a user signs in as Adminstrator@domain.local then everything
works fine, nslookup works, gp works, netdiag seems ok, domain resources are
available. All other sign ons take a very long time to apply settings,
netdiag shows errors, eventviewer shows it's not finding the domain, and all
resources are unavailable. These same users can sign in without any problems
at Hq I don't think this is a DNS issue as nslookup resolves ip and names
and I have put the ip address for our DNS in the preferred DNS entry menu.
When I do an ipconfig it only lists our DNS server We also another warehouse
with a similar setup and they don't show these problems. I have reloaded XP
on one of the machines and updated the nic drivers to see if that fixed the
problem but it didn't. Hope someone can help.

[Courtney]

Called Microsoft. We forced kerberos to use TCP. It is possible that the
real issue is in distance between the warehouse and the CO using DSL. I'm
not complaining, since it gives them broadband but I wish these things could
be trouble shot easier.

"Courtney" wrote:

> This one is driving me nuts:
> We have a remote warehouse using DSL to connect to the HQ domain via Linksys
> VPN router. If a user signs in as Adminstrator@domain.local then everything
> works fine, nslookup works, gp works, netdiag seems ok, domain resources are
> available. All other sign ons take a very long time to apply settings,
> netdiag shows errors, eventviewer shows it's not finding the domain, and all
> resources are unavailable. These same users can sign in without any problems
> at Hq I don't think this is a DNS issue as nslookup resolves ip and names
> and I have put the ip address for our DNS in the preferred DNS entry menu.
> When I do an ipconfig it only lists our DNS server We also another warehouse
> with a similar setup and they don't show these problems. I have reloaded XP
> on one of the machines and updated the nic drivers to see if that fixed the
> problem but it didn't. Hope someone can help.