XP hangs logon to Domain

[Guest]

I bought 15 new Dell computers. One Poweredge 1800 w/ W2k3 Standard x64 and
14 WXP clients. The clients take 90 seconds to logon to the Domain.

 

[Malke]

I bought 15 new Dell computers. One Poweredge 1800 w/ W2k3 Standard
x64 and
14 WXP clients. The clients take 90 seconds to logon to the Domain.

This is usually caused by incorrect DNS settings, so start there. Your
server should only look to itself for DNS with forward and reverse
lookup zones set for Internet access. Workstations should only look to
the server for DNS. Here are some links to help you:

How Domain Controllers Are Located in Windows XP -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

Setting Up the Domain Name System for Active Directory -
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675

HOW TO: Configure DNS for Internet Access in Windows 2000 (applicable to
Win2003 also) -
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

DNS and AD FAQs - http://support.microsoft.com/?id=291382

Malke

 

[Guest]

This is usually caused by incorrect DNS settings, so start there. Your
server should only look to itself for DNS with forward and reverse
lookup zones set for Internet access. Workstations should only look to
the server for DNS. Here are some links to help you:

How Domain Controllers Are Located in Windows XP -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

Setting Up the Domain Name System for Active Directory -
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675

HOW TO: Configure DNS for Internet Access in Windows 2000 (applicable to
Win2003 also) -
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

DNS and AD FAQs - http://support.microsoft.com/?id=291382

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

I guess reading a few books and passing and couple of MCP exams isn't worth
much. Give me a day to check things out.

 

[Malke]

I guess reading a few books and passing and couple of MCP exams isn't
worth much. Give me a day to check things out.

No comment.

Malke

 

[Guest]

No comment.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

I can ping both the IP Address and FQDN of the server successfully. Doesn't
that mean DNS and TCP/IP are working ok?

Also the problem is almost the same as KB Q329457 except that the clients
are new and don't have large profiles yet. Do you know anything about this
issue?
It takes about 2 minutes for the clients to get past the "applying your
settings screen".

 

[Malke]

I can ping both the IP Address and FQDN of the server successfully.
Doesn't that mean DNS and TCP/IP are working ok?

No. You have to check the DNS on the server and the workstations as I
described.

Also the problem is almost the same as KB Q329457 except that the
clients are new and don't have large profiles yet. Do you know
anything about this issue?
It takes about 2 minutes for the clients to get past the "applying
your settings screen".

Check your DNS before you start worrying about hot fixes.

Malke

 

[Guest]

No. You have to check the DNS on the server and the workstations as I
described.

Check your DNS before you start worrying about hot fixes.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

I pointed the client to use the server for DNS and registered the ip
configuration with ipconfig/registerdns. Now all is speedy.

 

[Malke]

I pointed the client to use the server for DNS and registered the ip
configuration with ipconfig/registerdns. Now all is speedy.

Great. Glad to hear you got it sorted. Thanks for taking the time to let
me know.

Malke