Slow NT Login and Share Access Loss

[Roger Price]

I have a Windows XP Pro client logging into a Windows 2K NT domain. The XP
client takes quite a long time logging in ... but it seems like all is well
after it finally does log in. Doing well means that the XP client can
access all shares and printers in the domain that the login user has
permissions
to access.

If you walk away from the XP client and come back after a period of time the
XP client will lose all access to any and all network shares. If you try to
look at a server or another peer using \\compname command.. You just get a
prompt asking for a username and password.

If you reboot the computer or log off and re login... the XP client can
access all shares and printers in the domain again..

Any help would be greatly appreciated

 

[Robert L [MS-MVP]]

You may have two issues here.
1. DNS issue: check this page for the details, http://www.chicagotech.net/winslow.htm#Q: Running slower while logon
2. autodisconnection issue: check this page, http://www.chicagotech.net/winfaqs.htm#Q: How to change the auto disconnection settings

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.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.


I have a Windows XP Pro client logging into a Windows 2K NT domain. The XP
client takes quite a long time logging in ... but it seems like all is well
after it finally does log in. Doing well means that the XP client can
access all shares and printers in the domain that the login user has
permissions
to access.

If you walk away from the XP client and come back after a period of time the
XP client will lose all access to any and all network shares. If you try to
look at a server or another peer using \\compname command.. You just get a
prompt asking for a username and password.

If you reboot the computer or log off and re login... the XP client can
access all shares and printers in the domain again..

Any help would be greatly appreciated

 

[Guest]

This might also help:

http://www.experts-exchange.com/Networking/WinNT_Networking/Q_21093961.html

 

[Kevin D. Goodknecht Sr. [MVP]]

In

I have a Windows XP Pro client logging into a Windows 2K NT domain.
The XP client takes quite a long time logging in ... but it seems
like all is well after it finally does log in. Doing well means that
the XP client can access all shares and printers in the domain that
the login user has permissions
to access.

If you walk away from the XP client and come back after a period of
time the XP client will lose all access to any and all network
shares. If you try to look at a server or another peer using
\\compname command.. You just get a prompt asking for a username and
password.

If you reboot the computer or log off and re login... the XP client
can access all shares and printers in the domain again..

Any help would be greatly appreciated

Is the DC and XP client only using the local AD DNS server?
No ISP or external DNS allowed in any position of TCP/IP properties of any
AD domain member.

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

 

[Warren Postma]

Is the DC and XP client only using the local AD DNS server?
No ISP or external DNS allowed in any position of TCP/IP properties of any
AD domain member.

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

This solved the problem we were having similarly with slow NETLOGON
processing (XP clients taking a long time to log in or access shares).

Is there any problem with an XP Client that is a member of the local AD
domain having an ISP's DNS server in its dns client settings? Or must
XP client boxen also only point to the W2K AD server's DNS?

Warren

 

[Kevin D. Goodknecht Sr. [MVP]]

In

This solved the problem we were having similarly with slow NETLOGON
processing (XP clients taking a long time to log in or access shares).

Is there any problem with an XP Client that is a member of the local
AD domain having an ISP's DNS server in its dns client settings? Or
must XP client boxen also only point to the W2K AD server's DNS?

No ISP DNS allowed on any member of an AD domain.