XP worstations take forever to log on???

[Chris]

A win2k server, the XP workstation take forever to log on
to the system. Is this a known issue, and how do I fix??

 

[Jonathan Maltz [MS-MVP]]

It sounds like a DNS issue. Are the XP clients set to use ISP DNS servers
or your AD DNS server(s)?

--
--Jonathan Maltz [Microsoft MVP - Windows Server]
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
tutorial site
Only reply by newsgroup. Any emails I have not authorized are deleted
before I see them.

 

[Hank Arnold]

It also could be mapped drives that are not connecting?

--
Regards,
Hank Arnold

It sounds like a DNS issue. Are the XP clients set to use ISP DNS servers
or your AD DNS server(s)?

--
--Jonathan Maltz [Microsoft MVP - Windows Server]
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
tutorial site
Only reply by newsgroup. Any emails I have not authorized are deleted
before I see them.

A win2k server, the XP workstation take forever to log on
to the system. Is this a known issue, and how do I fix??

 

[chris]

The DNS is picked up from the dhcp on the linksys router.
Which is actually the router address. The router in turn
uses the ISP DNS addresses. Should I be running DNS on
the server or WINS??

-----Original Message-----
It sounds like a DNS issue. Are the XP clients set to use ISP DNS servers
or your AD DNS server(s)?

--
--Jonathan Maltz [Microsoft MVP - Windows Server]
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
tutorial site
Only reply by newsgroup. Any emails I have not authorized are deleted
before I see them.

A win2k server, the XP workstation take forever to log on
to the system. Is this a known issue, and how do I

fix??


.

 

[Jonathan Maltz [MS-MVP]]

When you set-up Active Directory, it asked you if you wanted to set up DNS.
When you setup DNS (as I'm hoping that you did) it created the relevant DNS
entries for your domain (for example, your AD domain is hi.local, when you
set up DNS during the AD setup, it created hi.local on the DNS server). So
in order for your XP clients to "see" hi.local, they need to be pointed to a
DNS server that has that information. Your ISP's DNS servers don't have
that info, but your local DNS server(s) do. Try pointing the XP clients to
use your AD server as their DNS server...

--
--Jonathan Maltz [Microsoft MVP - Windows Server]
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
tutorial site
Only reply by newsgroup. Any emails I have not authorized are deleted
before I see them.

The DNS is picked up from the dhcp on the linksys router.
Which is actually the router address. The router in turn
uses the ISP DNS addresses. Should I be running DNS on
the server or WINS??

-----Original Message-----
It sounds like a DNS issue. Are the XP clients set to use ISP DNS servers
or your AD DNS server(s)?

--
--Jonathan Maltz [Microsoft MVP - Windows Server]
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
tutorial site
Only reply by newsgroup. Any emails I have not authorized are deleted
before I see them.

A win2k server, the XP workstation take forever to log on
to the system. Is this a known issue, and how do I

fix??


.