Slow domain log-in

[CGIMana]

Hello,

I'm running a Windows XP 2003 Server
I have 13 clients running WIndows XP Pro
Most of the newer computers are running gig-a-bit NIC's

I'm getting many complaints about how long it's taking to log-in and get to the desktop on some computers it's almost 5 minutes, is this an issue of the speed of the server, network speed, something with my firewall(which when deactivated still occurs) or some unknown MS-BS?

-Hoped I helped. Don't forget this site is Member supported.

 

[WhoKilledKenny]

Are you using Group Policies?
Are you using logon Scripts?
Are you having any errors in your event logs?
Are you redirecting folders to a file server?
What is the size of the SYSVOL folder on your DC?
What is the size of the NETLOGON folder on your DC?

 

[pgaliardo]

In addition to WhoKilledKenny's suggestions, are you using roaming profiles? Also make sure DNS is set up correctly on the workstations.

 

[Fatboy0341]

I'd also ask what other apps are installed on these systems - ie - are they laptops that run VPN software or just plain old desktop PCs?

How much stuff is being loaded and started during the boot/logon process?

Try this - let one of the systems boot up and let it sit for about 10 minutes - and then log in. That will tel you whether it's a boot/load issue or something that is taking place during the logon/authenticaton process.



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[Daveyd123]

Make sure you have all your workstations DNS settings pointing to your Domain Controller and not you ISP.

 

[CGIMana]

Daveyd123

This is only a file server for flyers, and our internal database system (DacEasy, I hate cheap companies)
I don't know why they even have a domain, but they insist on log=ons, and to make it easier for me I stick with the doamin.
How ever another problem is that I'm using the ISP's DHCP server that i do not have access to.
If I point the PC's to the servers DNS..then wouldn't the internet not work since it's not a DNS server?

-Hoped I helped. Don't forget this site is Member supported.

 

[WhoKilledKenny]

No, what he is saying is that AD Logon relies on DNS (SRV RECORDS) for finding the logon servers. If the clients are not pointing to the DNS servers for the domain it would not be able to find the DCs for authentication. It sound like you are not running a domain and the logon accounts are local to the file server (workgroup network).
- but -
If you are running a domain you should point your clients to the DNS server that is internal to your domain. As far as Internet access goes, on the local DNS server you could set up a forwarder to your ISPs DNS so that Internet queries would go to them. - or - Your DNS server can use root hints to query the DNS servers on the net.

 

[CGIMana]

But my Domain server isn't a DNS server. What IP do I use? Could I put the DNS of the server as the main, and the DNS of the ISP as the second?

And I know the computer see the domain. Otherwise I would have been able to add them to it.

When the domain is not available (when I set the file wall to block it, or I pull its net cable) the computers go to the desktop immediately.

-Hoped I helped. Don't forget this site is Member supported.

 

[Daveyd123]

If you are running Active Directory on a Domain Controller, DNS is required and should have been installed when you ran DCPROMO on the server.

DNS works fine on a DC. If you have no DNS server, which is rather odd, then install it on the DC.

After installation, make sure the DNS IP entries on the DC point to itself. Setup "forwarders" in DNS to forward to your ISPs DNS server.

Make sure all the workstations are pointing to your internal DNS server. Do not have any DNS entries on your workstations pointing to your ISP

 

[Daveyd123]

How to Configure Forwarders

Windows Server 2003 can take advantage of DNS forwarders. This feature forwards DNS requests to external servers. If a DNS server cannot find a resource record in its zones, it can send the request to another DNS server for additional attempts at resolution. A common scenario might be to configure forwarders to your ISP's DNS servers.

1. Click Start, point to Administrative Tools, and then click DNS.
2. Right-click ServerName, where ServerName is the name of the server, and then click the Forwarders tab.
3. Click a DNS domain in the DNS domain list. Or, click New, type the name of the DNS domain for which you want to forward queries in the DNS domain box, and then click OK.
4. In the Selected domain's forwarder IP address box, type the IP address of the first DNS server to which you want to forward, and then click Add.
5. Repeat step 4 to add the DNS servers to which you want to forward.
6. Click OK

 

[WhoKilledKenny]

ok let's backup for a second...
CGIMana,
Questions:
Are you running Active Directory?

How Many Servers (not workstations) are in your environment?

What do these Servers do (purpose)?

When you add a computer to your network - do you choose the Workgroup or Domain oprtion?