Re: Client log-on slow to 2k3 from XP SP2
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 6 Dec 2006 21:39:24 -0000
Hi
GPOs can delay the logon, as loading profiles, and startup programs, etc... test with a clean User profile in a clean machine and check if the delay still remains...
for DNS Follow
Assuming DNS AD Integrated Zone
-Make sure that each DNS server points to itself under NIC preferred DNS. If the Server IP-Address is 192.168.0.1 then the preferred DNS should also be 192.168.0.1.
- Clients: Make sure that the clients only use their local available DNS server(s) on their NIC DNS configuration. Do not place the ISP DNS server or any other DNS on the client or DNS Server NIC properties, this is a common mistake. The clients should use their local DNS server to resolve all queries. It’s up to the local DNS server to handle the Internet resolution as any other Zone that the DNS is not authoritative for. Check the link for configuring DNS for Internet resolution.
Note: The DNS client does not utilize each of the DNS servers listed in TCP/IP configuration for each query. By default, on startup the DNS client will attempt to utilize the server in the Preferred DNS server entry. If this server FAILS to respond for any reason, the DNS client will switch to the server listed in the alternate DNS server entry. The DNS client will continue to use this alternate DNS server.
Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/kb/825036/en-us
How to configure DNS for Internet access in Windows Server 2003
http://support.microsoft.com/kb/323380/
--
*************************************************
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA + Exchange + MSCE
*************************************************
"Maki" <Maki@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:5652CF1D-5D37-441B-A679-805846C1FA69@xxxxxxxxxxxxxxxx
I'm sure alot of people have come accross this before. It used to take me
about 5 minutes to log on from a domain connected machine hosting XP SP2 to a
DC that has 2003 Servers running. I then pointed the DNS from client to DC
and cut down the log on time to 80 seconds. Still takes quite a bit of time
(80 seconds from clicking on log on to having all the items on desktop ready).
Others have suggested that perhaps the redirection of the folder is an issue
or someone posted and said that a solution is to either let the AD map the
home drive or to have a script but not both. I should also mention that I am
running deep freeze, so it does not cache and every time someone logs on
after the machine restarts (computer is refreshed) they create a profile on
computer all over again and download the Group policy, etc.
Upon going to the Userenv.log file (windows/debug folder) i found this line.
It takes about 45 seconds (this will reduce the login to 35 seconds from 80
if sorted if this is the issue). Can somebody tell me what to do? Thanks.
GetGPOInfo: Local GPO's gpt.ini is not accessible, assuming default state.
.
- Follow-Ups:
- Re: Client log-on slow to 2k3 from XP SP2
- From: Maki
- Re: Client log-on slow to 2k3 from XP SP2
- Prev by Date: Re: Rollback Solution / Password Reset
- Next by Date: Re: Mandatory profile will not load on multiple computers at one t
- Previous by thread: Re: Language Pack Error on DCs
- Next by thread: Re: Client log-on slow to 2k3 from XP SP2
- Index(es):
Relevant Pages
|
