Newsgroup: it.comp.os.win.win2000
Titolo: Loading Personal Settings takes 20 minutes

Hi,
My office has a Win 2k server and about 20 Win 2k Pro workstations.
Recently, many of the workstations have begun taking 15-20 minutes to
load and apply "personal settings".
It's very inconsistent though.  Not all the machines do it and the
machines that do, don't do it 100% of the time.
When they do though, it's torture.  
Can anyone tell me what the issue might be and suggest a possible
solution?
Thanks very much.
Ron


Are there any errors in the event viewer both on the server and
workstations?
It might be also a DNS issue. How did you configure it?
Bye,
Memmo
--------------------------------
Inviato via 
http://usenet.libero.it

It might be also a DNS issue. How did you configure it?
Have the stations set to "obtain DNS automatically.
Have the server handling DNS.  Would it be better to have the server's
IP entered as the DNS?  
Thanks,
Ron

IP entered as the DNS?  
Since the server is handling DNS through DHCP, type ipconfig /all both
on the server and workstations and verify that the primary DNS server
for them is the server's IP address (I hope external DNS resolution is
correctly handled by forwarders).
Bye,
Memmo

 correctly handled by forwarders).
... or root hints.
ciao


ciao
... or root hints, yes (I never use root hints for external name
resolution so I tend to forget about them)   ;-)
Ciao
Memmo


Ok, getting a little over my head here.
Not at all familiar with root hints.
Also, the real ignorant question of the week is:
Does it matter that DNS is being handled by the server and DHCP is
being handled by the router?
Is it better to have them both done by one of them?
Is one preferable to the other?
Thanks again,
Ron

 Is one preferable to the other?
If everything always worked correctly, i'd have them both handled by win 
2000.
However, this means that if the server goes down, so will web browsing. 
This bugs me because if you have a router you shouldn't NEED a server to 
be able to browse the web. Usually, a router is less failure-prone than 
a hardware router. DNS availability is also more "critical" than dhcp 
availability, because dns is needed all the time as opposed to dhcp 
which is needed only at boot time.
My personal solution to this is the following:
Win 2000 AND the router BOTH do dns. My router simply "behaves" like a 
dns server, but simply forwards all queries to my ISP's dns.
dhcp is handled by windows 2000, and passes BOTH its own ip (primary) 
AND the router's ip (secondary) as dns.
In case of minor server downtime, clients access the web as usual 
(clients will revert to secondary dns if primary is not available).
In case of major downtime, dhcp on the router is configured and ready to 
be "fired"... but kept switched OFF for normal use.
 > Ok, getting a little over my head here.
 > Not at all familiar with root hints.
Using forwarders means that queries are passed to another (typically 
your ISP's) dns server.
Using root hins means that your dns handles the query by itself.
I prefer using root hints because I don't like someone caching names for 
me without my control, however it does increase traffic to/from your 
network.
I usually use forwarders in low-bandwidth situations, such ad ADSL's 
with 128k upstream.
regards
