Guest Jose Alves Posted May 1, 2008 Posted May 1, 2008 Hello. I´ve two windows 2003 std DC. This two DC are DNS servers of the lan. One of the servers has Exchange 2003. At 5 days ago i´ve done an upgrade to 4 GB (maximum supported by windows 2003 std) to the server with Exchange 2003, and since that the server hangs, and do not generate any error in event viewer. The system freeze. All the client computers are Windows XP Professional, and are configured by DHCP and know the 2 DNS. When the server with Exchange 2003 goes down, i´ve problems with users authentication (logon). I think the other server should kepp users authentications and computers working ok in the lan, but when users try to logon, the request fails ! I´ve checked the AD and DNS replication and no problems were found. Why the other server does not respond to the client logon request? The problem of "system freeze" can be related with the quantitiy of 4 Gb of memory (i,ve already changed the DIMMS)? I´ve done hardware diagnostic with HP smartstart CD, but no problems wer found.. Please, someone, help. Thanks in advance.
Guest Ace Fekay [MVP] Posted May 2, 2008 Posted May 2, 2008 Re: 2 windows 2003 DC hang problem In news:8B3428D5-C653-4BE7-B8FF-198C414EF0B9@microsoft.com, Jose Alves <JoseAlves@discussions.microsoft.com> typed: > Hello. > I´ve two windows 2003 std DC. This two DC are DNS servers of the lan. > One of the servers has Exchange 2003. > > At 5 days ago i´ve done an upgrade to 4 GB (maximum supported by > windows 2003 std) to the server with Exchange 2003, and since that > the server hangs, and do not generate any error in event viewer. The > system freeze. > All the client computers are Windows XP Professional, and are > configured by DHCP and know the 2 DNS. > > When the server with Exchange 2003 goes down, i´ve problems with > users authentication (logon). > > I think the other server should kepp users authentications and > computers working ok in the lan, but when users try to logon, the > request fails ! I´ve checked the AD and DNS replication and no > problems were found. > > Why the other server does not respond to the client logon request? > The problem of "system freeze" can be related with the quantitiy of 4 > Gb of memory (i,ve already changed the DIMMS)? > I´ve done hardware diagnostic with HP smartstart CD, but no problems > wer found.. > > Please, someone, help. > Thanks in advance. How much RAM was previously installed? For 4GB, you will want to use the /3GB and /USERVA=3030 switch in the boot.ini file. But then again, it may not be recommended if Exchange is on a DC or it eats up resources. Also, run the Exchange Best Practice Analyzer (ExBPA). It will report any errors on the Exchange side of things, AD-Exchange related issues, as well as memory registry recommendations, among others: Download details: Exchange Best Practices AnalyzerFile Name: ExBPA.msi. Version: 1. Date Published: 6/6/2007. Language: English. Download Size: 6.8 MB. Estimated Download Time: 17 min 56K ... http://www.microsoft.com/downloads/details.aspx?FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3 Also, just an FYI, Exchange is not recommended on a DC. Plus, Exchange performs better with write-cache enabled on the drive. Unfortunately a DC by default, disables write-cache on the drive the AD database is on. This is a feature to prevent AD database corruption, and especially because the FRS (an AD service), does not recover during a hard stop (power outages, unplugged, etc). Also, there is no way to enable it on that drive on a DC. Just some food for thought: Slow Network Performance After You Promote a Windows 2000-Based Server to a Domain Controller (also applies to Win 2003): http://support.microsoft.com/kb/321543 Considerations when hosting Active Directory domain controller in virtual hosting environments http://support.microsoft.com/kb/888794 Exchange on a DC: http://hellomate.typepad.com/exchange/2004/02/exchange_on_a_d.html Exchange Disk Sizing (search for write-cache in the article): http://blogs.technet.com/evand/archive/2004/10/14/242127.aspx Anyway, getting back to the issue at hand, if you are still having problems after running the ExBPA, and implementing it's recommendations, then I would look at the RAM. Even though tests say it's fine, it may still be bad RAM. I've seen this before. Let us know how you make out. -- Regards, Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP Microsoft MVP - Directory Services Microsoft Certified Trainer For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers. Infinite Diversities in Infinite Combinations
Recommended Posts