Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

UserNV 1030 & 1054

Status
Not open for further replies.

bsan2008

IS-IT--Management
Nov 3, 2008
12
I've only one DC (windows server 2003) with other XP Prof. Clients.

DC also has DNS Server Role. No other roles.

Server runs fine independently for hours. But whenever any client tries to logon, after few minutes everything hangs. Server hangs and clients cannot access anything.

When I checked log I got following errors-

USERNV error 1030 and 1054
DNS errors 4000, 4004 and 4015
NTDS error 1866

DC is configured with
IP=192.168.1.10
subnet=255.255.255.0
Gatway=192.168.1.1 (Linksys Router's IP to access Internet)
Primary DNS=192.168.1.10
Secondary DNS=192.168.1.1

All other clients are configured as
IP=192.168.1.xxx
Subnet=255.255.25.0
Gatway=Nill
Primary DNS = 192.168.1.10
Secondary DNS= Nill

When I removed DC, all other clients are working fine in network, when DC is connected and tried to logon again everything hangs.

Kindly Help.

Thanks in advance
 
This is incorrect.
Secondary DNS=192.168.1.1

Remove this entry, and go into your DNS server config, properties and add a forwarder to your ISPs DNS servers.
 
Dear Ashpp,
Thanks for suggestion.

With dcdiag I got the error that DC Server found @ 192.168.1.10 but could not be reached.

I removed DNS server roll and reinstalled it with forwarder as per your suggestion. At this point it was not showing any DNS error but still 192.168.1.10 could not be reached.(even can't ping) While doing all trials I disabled QuickHeal Antivirus Firewall and got this error solved.

Now since last 24 hours there is no 1054 error, no dns error like 4000, 4004 and 4015.

But still 1030 is occuring and with that error server hangs. This happens almost after 1 hour of work in network. If no client is connected server dosen't hangs!

If Server is restarted and clients are still connected, server could not start and stucks @applying computer settings screen. If lan cable is removed while restarting it boots fine and starts working after cable connected back. (ofcourse for next 1 hour only!!!)

Regards,
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top