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 :>)