Slow login from XP client to Win2K server

[Gary B. Levy]

My Windows XP Pro clients have a much slower login to my
domain
controller than a Windows 2000 Pro client. To further
exacerbate the problem,
I am temporarily without internet access at work owing to
a recent move.

I am running a Windows 2000/Small Business Server 2000
domain controller. The domain controller is running the
DNS service,
but not DHCP as There is a Netgear firewall which provides
DHCP services.
In DNS, I have configured forward lookup, reverse lookup,
and forwarders.


The server has a hardwired IP address mapped from the
firewall.


For the XP client workstations, I have experiemented with
variations of:

IP and DNS servers derived from the firewall's DHCP
services.
IP from the firewall's DHCP service and specific
(external) DNS server addaresses hardwired
in the network setup.

When an XP client logs into the domain, if there is no
WINS server identified
at the client side, the user can authenticate to the
domain but CANNOT see or
access domain resources (shares, printers, etc). I don't
get that behavior with
Win2K Pro clients.

Any suggestions or pearls of wisdom???

Thank You :>)

[Robert L [MS-MVP]]

quoted from http://www25.brinkster.com/ChicagoTech
Why is XP running slower while logon 1

When I login into a Windows 2000 active directory from a new xp pro machine
the login in is extremely slow. After logged on, everything works fine. But
other windows versions don't have this problem.
A: This is almost like name resolution issue. Comparing with previous
versions, XP is heavily dependent on DNS to find DC. If the DNS is
configured incorrectly, XP will take longer time waiting for it to timeout
before it tries using NetBIOS. Make sure
1) The DNS setup correct and have the server information.
2) XP clients can find the DNS server.
3) XP machine's DNS server is pointed to your internal DNS server rather
than your ISP's DNS server.
4) Make sure no errors on logon scripts or GPO's that could be causing
the delay.
5) Check any errors on event viewer.
6) Disable NetBIOS on the interfaces that client will not use.
--
For more and other information, go to
http://www25.brinkster.com/ChicagoTech

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.

"Gary B. Levy" > wrote in message
...
> My Windows XP Pro clients have a much slower login to my
> domain
> controller than a Windows 2000 Pro client. To further
> exacerbate the problem,
> I am temporarily without internet access at work owing to
> a recent move.
>
> I am running a Windows 2000/Small Business Server 2000
> domain controller. The domain controller is running the
> DNS service,
> but not DHCP as There is a Netgear firewall which provides
> DHCP services.
> In DNS, I have configured forward lookup, reverse lookup,
> and forwarders.
>
>
> The server has a hardwired IP address mapped from the
> firewall.
>
>
> For the XP client workstations, I have experiemented with
> variations of:
>
> IP and DNS servers derived from the firewall's DHCP
> services.
> IP from the firewall's DHCP service and specific
> (external) DNS server addaresses hardwired
> in the network setup.
>
> When an XP client logs into the domain, if there is no
> WINS server identified
> at the client side, the user can authenticate to the
> domain but CANNOT see or
> access domain resources (shares, printers, etc). I don't
> get that behavior with
> Win2K Pro clients.
>
> Any suggestions or pearls of wisdom???
>
> Thank You :>)
>