Networking Login Too Slow??

hey guys. I'm having a really bad problem. I just recently set up at win2k advanced server domain with 3 workstations and two laptops. everything is working fine, but each computer takes 5 minutes to get to the log-in screen and then another 5 minutes to complete the login process and get into windows fully. I have tried disabling profiles and I have tried disabling policies but to no avail. All of the computers are running Win2k. What should I do??

 

[Vegito]

you're probably loading all the ie temp files, goto my computer and user profile and see how many meg is each profiles..
what u can do is exclude them

or

ie, make a c:\InetTemp directory and goto each user and change the temp file directory into c:\inettemp so it' doesn't get send back..

hmm, maybe something else too..

 

[Garion]

Also check your DNS settings. Messed up DNS can make some very strange things happen during logins and normal operations..

 

[Vegito]

Oh yeah, DNS, it's like gold when using w2k.. client need dns for ad servers...

 

[Shadow07]

You have a DNS issue. THe problem is that your clients are trying to contact the local Dynamic DNS server for the Domain they are members of. You will need to check to make sure that DNS has been properly installed on you DC.

Let me know if you have additional questions.

 

forcesho: its not something with the profiles because i disabled them and it still took long

about the dns, that could very well be the problem. since i don't have a domain name and all the stuff with the whole dns setup i just made one up and then assigned some random ips to it. what should i do to correct this so that it will run faster?

 

[Shadow07]

Did you install Active Directory (DCPROMO) on your Advanced Server?

 

[Shingy]

yes, i did set up active directory and thats where i set up the dns stuff

 

anyone have any idea??

 

[spidey07]

<< about the dns, that could very well be the problem. since i don't have a domain name and all the stuff with the whole dns setup i just made one up and then assigned some random ips to it. what should i do to correct this so that it will run faster? >>



Well, for starters you could not just make up network addresses. take out the DNS ip addresses. your clients and servers are trying to register them selves with a dynamic DNS, what's worse is that you made up the IPs so it is taking forever to timeout to a server that doesn't exist.

sounds like you need to reinstall your server without active directory (i don't do windows so I'm not really sure)

or correctly setup an active directory (i have no clue here) SHADOW07 knows alot about this

search MS for more info...found this in 10 seconds

 

[Shadow07]

Spidey - Stay out of this conversation! Just kidding around. What you need to do is set all of your internal PC's DNS server IP Address to your Domain Controller that you installed Active Directory and DNS on (including your DC). Spidey is correct in saying that if you set your clients to a non-existing DNS server, the client will try to update their DNS record. And since the IP doesn't exist, your clients are timing out. Thus, increasing the logon time. This is why your clients are taking SOO long to log in.

Let me know if you need me to clarify anything. You can IM me if you want to.

EDIT: Sorry. Morning time and I still haven'e had my first cup of coffee yet. NEED CAFFEINE!

 

well, I actually figured out the problem. It was the DNS. Once I set the DNS IPs on the clients to the server's IP it worked beautifully. But I have one more that you guys might be able to help me with. I made a policy file with Poledit and put it in the netlogon folder on the server. So, when I log on to the network, the policies aren't active. But, when I just log in to the workstation itself, the policies have replicated and are working. Any idea why the policies wouldn't be active when logged into the server?? Thanks for all your help.

 

[Woodie]

Use GPO's rather than NT4 type policies. Leverage much more effectively, and have way more settings.

GPOs are linked to various domain/OUs. MS creates two policies by default: Default Domain Policy and Default Domain Controllers Policy.

The DC shouldn't pick up the netlogon type policy, since you're doing a &quot;local&quot; logon (to the console).

--Woodie

 

[Shadow07]

POLEDIT policies whould only be used on legacy OS's (i.e. Windows 95, 98, NT 4). If you want to set user/computer policies, you need to edit the Group Policy Object either within Active Directory Users and Computers, or Actvie Directory Sites and Services. You will need to make sure that the ADVANCED FEATURES is check marked in the VIEW menu within AD Users and Computers.

If you don't know which setting does what, leave it alone or post a question about it here.

 

[Shingy]

thanks for the info guys. Ill have to try that out tomorrow. Had no idea that win2k had a different policy setup. One question though. You said poledit was only for older OSes, so how come when I log in to the computers themselves and not on the network do the policies that I set in Poledit work? Just wondering... Thanks again.

-shingy