WinXP PCs take 10 minutes to login to Windows 2000 Server


M

Mik

Hi,

Not sure if this is the right place to post this but here goes :

NetWare 5.0 SP6a server running DHCP server
Windows 2000 Server
DNS request are handled by DSL router whose IP address is primed as
the DNS server when a PC is allocated an IP address by the Novell DHCP
server
Windows 95 (Yes, still!!), 98SE, and 2000 workstations (Novell
Client 3.40)
Two new Windows XP SP1 Workstations (Novell Client 4.90 SP2)
--------------------
All Windows 95, 98, ME, 2000 workstations connect to both servers
without problems, and access the Internet fine too.

The two new WinXP PCs, custom-built , with Windows XP SP1 and all
patches, initially would not connect to the Windows 2000 Server till
we modified the HOSTS file to add the IP address of the Windows 2000
Server. They both login to the NetWare server instantly. However,
when it comes to login in to the Windows 2000 Server, it takes 10
minutes for them to complete "Loading policies, security settings,
personal profile, etc..., etc...". There are no policies defined on
the Windows 2000 Server. Once the XP PCs have logged in after 10
minutes, everything works fine, but it takes 10 minutes to get there !

My question : Is this a DNS issue, specific to XP, is it a WINS
issue, or, possibly, a Novell Client issue ? (Remember, none of the
other PCs, 60 of them running Win95/98/ME/2000, have this problem).
Also, if I disable the Client for Microsoft Networks so that the XP
PCs only login to the Novell Server, the login is then instantaneous.


Thanks for any help.

Mik
 
Ad

Advertisements

R

Robert L [MS-MVP]

more likely DNS issue. what do you get is using nslookup?

--
For more and other information, go to http://www.ChicagoTech.net

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
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
L

Lanwench [MVP - Exchange]

Mik said:
Hi,

Not sure if this is the right place to post this but here goes :

NetWare 5.0 SP6a server running DHCP server
Windows 2000 Server
DNS request are handled by DSL router whose IP address is primed as
the DNS server when a PC is allocated an IP address by the Novell DHCP
server
Windows 95 (Yes, still!!), 98SE, and 2000 workstations (Novell
Client 3.40)
Two new Windows XP SP1 Workstations (Novell Client 4.90 SP2)
--------------------
All Windows 95, 98, ME, 2000 workstations connect to both servers
without problems, and access the Internet fine too.

The two new WinXP PCs, custom-built , with Windows XP SP1 and all
patches, initially would not connect to the Windows 2000 Server till
we modified the HOSTS file to add the IP address of the Windows 2000
Server. They both login to the NetWare server instantly. However,
when it comes to login in to the Windows 2000 Server, it takes 10
minutes for them to complete "Loading policies, security settings,
personal profile, etc..., etc...". There are no policies defined on
the Windows 2000 Server. Once the XP PCs have logged in after 10
minutes, everything works fine, but it takes 10 minutes to get there !

My question : Is this a DNS issue, specific to XP, is it a WINS
issue, or, possibly, a Novell Client issue ? (Remember, none of the
other PCs, 60 of them running Win95/98/ME/2000, have this problem).
Also, if I disable the Client for Microsoft Networks so that the XP
PCs only login to the Novell Server, the login is then instantaneous.

In AD, remember that all servers and workstations should specify *only* the
internal AD-integrated DNS server's IP address in their network settings.
The AD-integrated DNS server should be set up with forwarders to your ISP's
DNS servers for external resolution. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202 for more
info. This is the most common cause of this problem.
 
Ad

Advertisements

L

Lanwench [MVP - Exchange]

Glad it helped!
Thanks Lanwench,

That was the solution.


Mik

"Lanwench [MVP - Exchange]"
In AD, remember that all servers and workstations should specify
*only* the internal AD-integrated DNS server's IP address in their
network settings. The AD-integrated DNS server should be set up with
forwarders to your ISP's DNS servers for external resolution. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202 for
more info. This is the most common cause of this problem.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top