Domain logon

[kwicks]

Hello All,

I will try to explain this the best I can. I joined a XP Pro laptop to our
W2Kdomain and it joined with no problem. I restarted and logged in locally
as administrator and went into user accounts and attempted to set up a user
for the domain I just joined and it told me that the trust between the
client and server failed even though I just joined that domain. I then
proceeded to logout and log into the domain as the user I was trying to
create. It logged in fine and I went back to user accounts and added the
account through there using the administrators credentials so I could give
that account admin rights.

Now the problem that I have is that on initial login after the machine has
been off or restarted the login will take about 2 to 5 minutes, but it only
happens with the user that I created for the domain. The local accounts log
right in. The funny thing is this will happen if I log into that account
while connected to the network or not. Once it finally goes through I can
log in and out in no time, just the first login is the problem.

If I am connected to the network and login, although the initial login is so
long once I get in I have no problems accessing the network or any of it's
resources. I just need to find out what is causing this extended login.

I have taken the laptop off of the domain and rejoined it, I have even
rejoined under a different machine name. I have taken all references to this
machine off of the DNS so it would see it as a completely new machine and no
luck. I joined one last week with no issues at all.

I want to thank you all in advance and I apologize for being so long winded
I just wanted to be descriptive.

KW

 

[Tomasz Onyszko]

Hello All,


(...)

I want to thank you all in advance and I apologize for being so long winded
I just wanted to be descriptive.

So If I understand corectlly the problem is in the slow domain logon for
domain users when connected to network. And what is Your DNS
configuration on this workstation - it should point in TCP/IP NIC
configuration to DNS which holds AD domain information - mostly the DC.

Also check the connection parameters like NIC speed and duplex option on
both sides, switch (or hub) and workstation.

 

[kwicks]

The problem exsists in only one laptop. Everyone else is fine and I have
joined this one the same way I have joined so many others in the past. We
use a VPN/Firewall appliance as a gateway and all workstaions are set to
DHCP which they get thier IPs from the gateway. The DNS settings on the
gateway are public from the ISP.

It does not seem to matter whether I am physically connected to the network
or not the one one domain user account on this machine will log in very
slowly on the initial logon. if I just sit this laptop on a desk connected
to nothing the local accounts on it can logon quickly but the one domain
user is still very slow.

 

[ptwilliams]

Internal clients *HAVE* to point to internal DNS for proper DNS resolution,
and therefore correct AD functionality.

Let the internal DNS server do the external lookups for your clients.

--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


The problem exsists in only one laptop. Everyone else is fine and I have
joined this one the same way I have joined so many others in the past. We
use a VPN/Firewall appliance as a gateway and all workstaions are set to
DHCP which they get thier IPs from the gateway. The DNS settings on the
gateway are public from the ISP.

It does not seem to matter whether I am physically connected to the network
or not the one one domain user account on this machine will log in very
slowly on the initial logon. if I just sit this laptop on a desk connected
to nothing the local accounts on it can logon quickly but the one domain
user is still very slow.

 

[kwicks]

It doesn't seem to have helped. Not sure where to go from there.

Internal clients *HAVE* to point to internal DNS for proper DNS resolution,
and therefore correct AD functionality.

Let the internal DNS server do the external lookups for your clients.

--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


The problem exsists in only one laptop. Everyone else is fine and I have
joined this one the same way I have joined so many others in the past. We
use a VPN/Firewall appliance as a gateway and all workstaions are set to
DHCP which they get thier IPs from the gateway. The DNS settings on the
gateway are public from the ISP.

It does not seem to matter whether I am physically connected to the network
or not the one one domain user account on this machine will log in very
slowly on the initial logon. if I just sit this laptop on a desk connected
to nothing the local accounts on it can logon quickly but the one domain
user is still very slow.