Link to home
Start Free TrialLog in
Avatar of anon-anon
anon-anon

asked on

DNS and AD problems leading to Exchange problems leading to stalling

The SBS2003 computer is stalling at applying computer settings.  There is a whole lot of history prior to this error now appearing:
https://www.experts-exchange.com/questions/24080940/SBS-2003-Slowdown-and-Freeze.html
https://www.experts-exchange.com/questions/24082304/SBS-2003-issue-how-to-keep-small-office-alive-while-solving.html
https://www.experts-exchange.com/questions/24086040/SBS-stalls-at-Applying-computer-settings.html

Essentially, we have replaced the 'file sharing' component of the server with a NAS.  Everyone is basically using POP mail.  The router/modem now gives out IP addresses (DHCP) but each client has reservations.

I really want to bring the server back up for two main reasons:
I still want to run an Exchange server (if possible)
And the Clients will eventually run out of cached logons, meaning I will need a DC or everything will be a pain.

Please help me get this server back up.  I have attached the Event Logs that I think describe the issue.

I have been trying to boot the server into normal mode with the ethernet cable unplugged and it continually stalls at "Applying Computer Settings".  It boots into Safe Mode, Safe Mode with Networking, and Directory Services Restore Mode ok.  I have file backups of the entire server, but I am wary to overwrite the server data at this point.

If you can correct this issue you may get extra points for solving the other questions...
logs.zip
addiag-dsrm.txt
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

Make sure the servers are pointing to the windows DNS server as their preferred and ONLY DNS server - use a forwarder to resolve external name lookups see http://www.petri.co.il/configure_dns_forwarding.htm 

Incidently it is unlikely you will "run out"  of cached credentials - there is no limit to the number of times cached credentials can be used - the default is caching for up to 10 different users per machine, but no limits apply to how often they can be used.
Avatar of anon-anon
anon-anon

ASKER

KCTS - do you mean make the clients point to the windows dns server?

I will do that eventually I guess, but I just want to bring the server up - I want it to boot into normal mode first.  Then I can sort out the other bits.

Thanks for the info about cached credentials.  I did something dumb tho - on my client PC I rolled back to a workgroup, then tried to get back onto the domain (without DC).  It says 'welcome to domain etc' but I can't logon - I think it has lost the credentials somewhere.  The other clients are ok.
Both the servers and and AD clients MUST point to your windows server for DNS.
If you have removed a machine from the domain its cached credentials will be lost.
This server is the only one present on the network.

If I am attempting to boot normally without a network connection and I get the errors, how can I clear them?  Is there something I need to rebuild DNS or AD to get Exchange happy again?

10:49 "All problems preventing updates to the Active Directory Database have been cleared. New updates to the Active Directory database are succeeding. The Net Logon service has restarted."

11:10 "The DNS server was unable to open zone Dimond.local in the Active Directory from the application directory partition DomainDnsZones.Dimond.local. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code."

11:12 "Unexpected error The specified domain either does not exist or could not be contacted." (Exchange)
Hello anon-anon,

it's better to keep posting in the old thread, and not open several threads please.
Anyway, rerun the connect to the internet wizard, and supply the DNS servers of your ISP in there.
server needs to point to itself as only! dns server.
clients need to be on DHCP, and the SERVER needs to provide DHCP to the clients.
clients should point to the SERVER as their ONLY dns server.

Regards,

suppsaws
This may sound crazy, but I want to be able to be non-dependent on the server.  In our small business situation, if anything happens to the server, everything is gone.  No matter how many backups you do, there is downtime.

In our current setup, the NAS is there sharing files simply, the Router gives out DHCP (but static really due to assignments), and I want to the server to be there as a DC and Exchange server.

Is this going to work at all?  Or do I need to get a backup DC going so that if the server goes down, I'm not dependent on it?
ASKER CERTIFIED SOLUTION
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
just as KCTS told you, stick to the SBS rules.
please close one of the two posts so we can work this out in one thread.
I told you the exact same thing in the other post.