C2k Help
Non-C2k Issues => Legacy Networks => Topic started by: Kev on October 11, 2007, 10:28:04 AM
-
One of our legacy servers that handles DNS seems to have an intermittant problem.
Every so often (and there's no pattern to this that I can see) the DNS service crashes.
This always happens around 8:30pm - 9:30pm.
There are two events logged as this happens:
Firstly:
The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine the DNS server event log entries that preceded these run-time events. The data is the number of events that have been suppressed in the last 60 minute interval.
Then:
The DNS server was unable to open Active Directory. 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.
DNS seems to be running perfectly well up until the first event log.
Have any of you guys encountered this before? Any clues as to why this happens?
-
Kev are you having any problems with your stations logging in, also are you running symantec AV.
If you are it might be the same problem i had were symantec attacked my DNS thinking it was a virus or something, i think it was something to do with what ever updates symantec and Win 2003 released the seemed to conflict each other.
So you could try and run an update for you AV and Win 2003 to see if this sorts it.
Just make sure you get your GPO's, users and any scripts you have backed up as mine required a complete rebuild.
-
If the problem has just started recently, i would just restart the server and monitor the DNS for the next few days.
-
Kev are you having any problems with your stations logging in, also are you running symantec AV
Yeah Forthill, when DNS falls over none of the users can log on. I am also running Symantec on my servers and stations.
Sounds to me like we have the same problem as you had.
How did u solve it in the end?
-
For me it happened in two days, were my dns was so damaged we needed to reinstall. luckily i had everything backed up the week before.
Kev first of all check to make sure that your legacy has not become connected to the c2k system as this could also cause your DNS going down(The two servers fighting over who the boss), to do this check your ip range of your stations with your server because the c2k range is very similar to our.
Failing that you will have to uninstall your DNS and reinstall it again to get it going, then update your server and symantec
I just hope you have caught it in time before the corruption is mirrored to your AD and you have to do everything from scratch :o, because this is what happened to me
Just make sure you backup all you important stuff e.g. users, scripts if you have any and gpo's.
FINGERS CROSSED
-
Just an update to this thread I posted a couple of months ago:
This problem was still ongoing and I had to regularly reboot the problem server.
I was going to take Forthill advice and do a rebuild/reinstall job on the server over the Christmas break.
However, last Thursday I had to rebuild a large number of my legacy machines because they weren't recognising
USB drives (thanks to Blackcat Spider software... don't get me started!! >:( ).
Since these machines have been rebuilt, the DNS problem on the server has ceased.
Its been 7 days now and the event viewer hasn't shown a single error. At this stage I don't think
its a coincidence.
So if anyone else is having this problem, it might be worth thinking about systematically rebuilding stations
before embarking on major server surgery.
-
check your DNS forwarders Northgate had changed them a few months back and didn't tell anyone. I think they are now:
10.4.134.21
10.4.134.22
10.4.134.23
Go to DNS right click your server and select properties. Click the forwarders tab and at the bottom you should see domain forwarder IP address list.
-
How sure are you of the IP addresses. Not that I doubt you but with my primary dead and setting up my secondary as primary I have to add these services and I am using your ip list.
-
i didn't read the problem correctly. I was having problems a while back with DNS. Problem that i was getting was that my DNS on my server was working correctly but when i went to get on the internet through the proxy server the i was unable to gain access to the internet. The DNS IP address on either HP or Northgate server had been changed to the address above.
Sorry for misleading you.
Next time i may read the question, when i not being nagged by teachers and their students sims reports.
-
Eh? You weren't misleading me, I just wanted clarification because you said "I think they are now: ". I wanted to be ure the IP addresses were correct as I have no way of checking them in order to define the DNS forward service.
Isn't it great when you ask a teacher about something you have to wait for an answer but wen they ask you, you are meant to know there and then.
-
they are what i have on my server just checked their now.
100% sure.
I had this problem for three weeks.
-
i would only change your DNS forwarders if you are having problems with access to the Internet on your legacy system.
-
I noticed the legacy is a lot slower than the C2k system and hoped that this would help clear that. The truth of the matter seems to be that the legacy system runs at 1Mb/s whereas the C2k system runs at 2Mb/s.
I have the PRTG Traffic Grapher installed for checking the bandwidth usage - this was done by HP as part of the trial for the Avantis internet cache system. I had the apple macs updating and they were taking forever when I checked the grapher that was the speeds it was reporting.
Do you find a similar slowness in your legacy system when using the internet?
-
Stephen, now you're scaring me about my OWN problem!
Is nothing sacred! ;D