Question Locked

Windows Log on Problems

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

All workstations on our LAN find it difficult to log onto the Domain. It takes up to 30 minutes for logon process to complete with some workstations. Our LAN is runing Win Server 2003 with 2 DC configured as DNS and 1 of the DCs is DHCP server distributing IPs to all workstations.

A study of the events log on the PDC shows errors relating to synchronization with other DC and some relating to DNS. One of those events is copied hereunder.

Any hint in overcoming this problem?

--- Copied from Event Viewer ----

Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 113
Date: 9/24/2008
Time: 3:40:24 PM
User: N/A
Computer: HQ-RES-DC-1
Description:
The DNS server could not signal the service "NAT". The error was 1168. There may be interoperability problems between the DNS service and this service.

2 replies

by Former member

Try these methods below:

If you are trying to use ICS (Internet Connection Service) and running DNS on the same box. That is also the reason why nothing is registering anymore.

Disable ICS, and configure NAT under RRAS to stop the errors.

THe 113 error is usually indicating that ICS is enabled, probably inadvertently, even though you are using NAT. Check your NIC properties to insure it is not turned on.
......................................

Clean Your DNS Cache to Fix Browsing Problems

If you've found yourself hitting DNS errors or 404 pages in your browser but you know your net connection is working fine, it might be time to flush and restart Windows' DNS cache. The How-To Geek shows how to do this in three command line entries, although you might only need the first to see results. After launching a command prompt as an administrator and closing down Firefox (which has its own DNS cache), enter the following:

ipconfig /flushdns
net stop dnscache
net start dnscache

An easier and quicker way of doing this in XP is to:
1) go to Start
2) go to Run
3) Type: services.msc
4) click Enter.
5) Then locate "DNS Client"
6) Right click on it.
7) From there, click Restart
....................................................................................

Put into a .bat file.
@echo off
echo .*** RUNNING IPCONFIG /FLUSHDNS ***
pause
ipconfig /flushdns
echo .*** STOP THE DNS CACHE ***
pause
net stop dnscache
echo .*** START THE DNS CACHE ***
pause
net start dnscache
Or:

@echo off
echo .*** RUNNING IPCONFIG /FLUSHDNS ***
ipconfig /flushdns
echo .*** STOP THE DNS CACHE ***
start /wait net stop dnscache
echo .*** START THE DNS CACHE ***
pause
net start dnscache
That way no pauses, and start /wait forces the batch file to wait until the net stop dnscache finshes before trying to start it

............................................................................................

Commandline-ophobes can also right-click on the connection, either in the Network Connections control panel applet or in the taskbar (if you have it set to always display there), and choose "Repair".
In addition to flushing the DNS cache, this renews the DHCP lease, flushes the NETBIOS cache, and reregisters NetBIOS and IP address with WINS.
...................................................................................................................

Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.

This discussion is closed to new replies.