After joining in domain PC slow starting

50 pts.
Tags:
DataCenter
Networking
Performance management
Project management
Dear all, Greetings of the day. I have windows 2000 server and 300 clients. Some are in domain. When I am trying to join in domain remaining PC after restarting its boot time is increased. Also working is slow. Please suggest for resoloution. Thanks in advance.
ASKED: November 29, 2006  4:47 AM
UPDATED: November 30, 2006  1:48 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

try to capture the DNS traffic on a network.
Is it just stand alone server? Exchange? DHCP? Configuration of the server? What about other PCs?

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Mortree
    Same questions. But this may be an overburdened Domain Controller (DC). If you don't have two DCs add one. Two DCs is a must just in case one fails. Also try not to have DCs doing too many other jobs other than Active Directory. For 300 computers DNS and WINS is probably not a problem. DHCP if you really have to and accept any security issues. But generally avoid making your main two DCs do file and print serving, SQL, email or other serious applications that might results in "prolonged distraction" from doing Active Directory. If you have an additional (3+) DCs then having say Exchange on that machine is OK. Just realize that DC probably won't be responding to many client AD requests but it can really help the Exchange server itself. If your DC hardware is older you may want to think about an upgrade. Faster CPU speed is very helpful on a DC (total 2GHz+). Avoiding inadequate memory is very important (384MB+) but enormous amounts 1GB+ is not that helpful unless it doing nonDC tasks. Faster disks can help DCs too (7200rpm+, etc) but it is probably wasteful to use expensive top performance drives. I would put some sort of hardware RAID on the disk system even if it is two disk SATA mirror. If you are super pressed for money, your second DC doesn't actually have to be on full blown server hardware from IBM or DELL. You can settle for a reliable workstation with solid CPU speed and fair memory.
    0 pointsBadges:
    report
  • Mortree
    If you are saying the workstations start up slow...well what burden of logon scripts and Group Policies are you imposing that they didn't run until they joined the domain? Check if you have an excessive number of GPOs to layer on and resolve. Can you reduce to 1 OU imposed GPO? Is there an unnecessary local computer policy still being applied? Older workstations might simply load down under these new duties. But maybe an overburdened DC is holding them back and is not letting the workstations read all the logon script and GPO files from the SYSVOL fast enough. The disk SYSVOL is on might be fragmented and near full. Here you might want to check performance counters for disk queues and paging activity over the typical times when workstations experience slow logon. Maybe the disk is just slow compared to the number of users. Maybe the DC lacks memory to properly cache these common files and run DC processes without swapping. A straight DC normally wants 384MB-768MB. Maybe you have just run out of DC CPU. Because DC responses are time sensitive you actually don't want to see spikes with flat heads at 100% very often on CPU performance. (Normally you wouldn't worry unless you saw something more sustained.) Also you should have a 100Mbps full duplex nework connection to assure snappy network responses.
    0 pointsBadges:
    report
  • Mortree
    Hmmm...also do you have at least two fast DNS servers? That could be on the same server as the DC functions. One thing about AD is that member workstations and servers are absolutely dependent on DNS to locate DCs, other servers AND services. So slow, bad or dropped DNS responses will slow clients. For 300 workstation network and combined AD& DNS & WINS on one server, I want at least 512MB RAM and a 2Ghz CPU if single CPU machine or dual 1GHz CPUs.
    0 pointsBadges:
    report
  • Tommski
    Remember, when running AD you must have a DNS service running on at least one server. When joining the domain make the workstation first DNS number that server. This will increase boot time. I have all my DC's running DNS and it solved a lot of my boot time problems.
    0 pointsBadges:
    report
  • Skepticals
    Everyone has already given a great deal of information - maybe too much. In simple terms: Make sure you have DNS installed on a server. Have this server point to itself for its DNS server. Make sure all your clients are pointing to this DNS server as well. If you are using DHCP, you could push it to your clients this way.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following