Win2k Pro client logon is slowwww 3

[energy4life]

2 mysteries:

(1) Win2k network here, with 15 CALs (13 currently used). the logon is taking longer at the "loading personal settings" point of the login. For ex: Step 3 below

1. boot PC (network/computer settings applied)
2. enter ID/pwd
3. wait while personal settings are applied
4. see active desktop

The more users, the slower it gets... WHAT MIGHT BE GOING ON?

second question:
(2) users are getting "your pwd will expire in 15 days" msgs. However, they were set up with a default pwd, which they changed at login... no other configuration. I've handled thus far by resetting the members in this OrgUnit (OU). But I'd like to solved. Any thoughts on what's causing this?

 

[brontosaurus]

1) Do you use roaming profiles, local profiles, or mandatory profiles? How is DNS set up?

2) I believe, by default, W2K sets up a Domain password expiration policy of 41 days (I think). So, you'd have to edit the Domain group policy to your preference.

 

[energy4life]

1) roaming profiles definitely (though a netwk admin guy set it up). For DNS: the server has a static IP. The clients use dynamic IPs, with the server IP as their default gw. The server then forwards to the router.

2) didn't know about the pwd expiration thing... I'll browse through the OU's group policy settings... thx

 

[brontosaurus]

Yeah, check the DNS settings. Make sure your DC (or server)points to itself as Primary DNS on properties of it's NIC. Then make sure clients are pointing to your server only (not ISP) for DNS resolution. Check out one of the profiles, how big is it?

 

[mozingod]

Are you running 10 or 100 base? I've notticed that even on a small 20 computer network w/normal sized profiles, it takes for ever on 10. Might want to consider an upgrade if it is. Darrell Mozingo
MCSA, A+, Network+, i-Net+, MOUS 2000 Master

 

[energy4life]

mozingod: it *is* a 10 base-T 16 port Linksys hub... (surprising it matters on such a small, simple netw)

brontosaurus: yep, the clients point SOLELY to the server for DNS. Now as for the server settings (DNS, profile size, etc), i got this weird AD msg: &quot;Naming information cannot be located because: The specified domain either does not exist or could not be contacted&quot;. lemme do some basic troubleshooting (rebooting - lol); I sure hope this isn't a big deal about to implode... <sigh >

**********
the more i work with computers, the more i love my garden.

 

[brontosaurus]

also check the W32 Time Service on the server. Is it started? Any event errors on the workstations relating to that?

 

[koquito]

if you need roaming profiles, then i think you should upgrade your network to higher speeds (Switches, NICs,etc)(also use switches instead of hubs), otherwise you will keep with those delays while log in.If you dont need roaming profiles or dont have the money to upgrade your network, then get rid of them, and let the users know that a change will come so they can save everything they want. For me the best solution is upgrade the network to handle higher speeds, because in the future you will be adding more users (hope so) and this will affect even more your network performance. A+, MCP, CCNA
marbinpr@hotmail.com

Keep fighting for your knowledge!

 

[trimelater]

If you have AD setup, DHCP, and DNS, I would suggest you go to Active Directory Users and Computers, edit your group policy, then going to Administrative Templates/System/Group Policy/
You should see Group Policy slow link detection and change it to enable and put 0 in the connection speed.

I don't know if roaming profile has anything to do with your situation and maybe those guys are right up above.


Trimelater

 

[RadioActiveLamb]

Roaming profiles are killing your logon/logoff performance. Each time a user logs-off, their client box copies the &quot;documents & settings/username&quot; folder to the server. Each time they log-on, it is duplicated from the server to the client. These profiles get HUGE. Notice the size of your PST files, if you use Outlook. It's not uncommon for those to exceed 50MB for a heavy email user.

If you MUST have roaming profiles, have your users clean-out their email and &quot;my documents&quot;. Have them save their files to a shared location on a file server.