DNS client hangs on startup

  • Thread starter Thread starter rogerw
  • Start date Start date
R

rogerw

Win2K Pro:

During an attempted installation of a scanner, apparently
the system got somewhat corrupted.

I had to remove Winsock Settings and remove and reinstall
TCP/IP in order to repair the "An operation was attempted
on something that is not a socket" problem. That seemed
to work OK, at least.

Upon repair, the system began to hang at startup.

Inspection with task manager showed services.exe was
using 98 to 99 percent of the CPU time - and process of
elimination shows that DNS client was the culprit.

Setting DNS Client to MANUAL allows startup without
hanging. Trying to start DNS Client Manually generates:

"Error 1053: The service did not respont to the start or
control request in a timely fashion"

after the 3 minute timeout.

Is there a reload method similar to that of winsock-
TCP/IP?

If not, how do I otherwise resolve the problem?

TIA,

R.
 
In
rogerw said:
Win2K Pro:

During an attempted installation of a scanner, apparently
the system got somewhat corrupted.

I had to remove Winsock Settings and remove and reinstall
TCP/IP in order to repair the "An operation was attempted
on something that is not a socket" problem. That seemed
to work OK, at least.

Upon repair, the system began to hang at startup.

Inspection with task manager showed services.exe was
using 98 to 99 percent of the CPU time - and process of
elimination shows that DNS client was the culprit.

Setting DNS Client to MANUAL allows startup without
hanging. Trying to start DNS Client Manually generates:

"Error 1053: The service did not respont to the start or
control request in a timely fashion"

after the 3 minute timeout.

Is there a reload method similar to that of winsock-
TCP/IP?

If not, how do I otherwise resolve the problem?

TIA,

R.
Click to expand...

No, not sure, but I would also check the DHCP Client service since these two
services rely on each other.

Try to reinstall TCP/IP again.

Is there a Proxy or an ISA firewall client installed on this machine?



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
-----Original Message-----
No, not sure, but I would also check the DHCP Client service since these two
services rely on each other.

Try to reinstall TCP/IP again.

Is there a Proxy or an ISA firewall client installed on this machine?
Click to expand...

I was afraid of that. I'm usually pretty good at
ferreting out the truth from MS KB, but it certainly
didn't yield anything on reinstalling the client.

I disable it, but every time I change a TCP/IP setting,
the system re-enables it and it hangs for about 10
minutes at reboot.

Yes, there is a firewall (Winroute Pro), but I disabled
that (renamed the driver) first off when I began hunting
the problem.

I have (since my original message) tried the
remove/install winsock, tcp/ip, and related stuff - but
with the same results.

I guess it's time to copy what ain't backed up to CD and
rebuild the partition.

Good thing I don't have to go to work until 1/5.
 
In
I was afraid of that. I'm usually pretty good at
ferreting out the truth from MS KB, but it certainly
didn't yield anything on reinstalling the client.

I disable it, but every time I change a TCP/IP setting,
the system re-enables it and it hangs for about 10
minutes at reboot.

Yes, there is a firewall (Winroute Pro), but I disabled
that (renamed the driver) first off when I began hunting
the problem.

I have (since my original message) tried the
remove/install winsock, tcp/ip, and related stuff - but
with the same results.

I guess it's time to copy what ain't backed up to CD and
rebuild the partition.

Good thing I don't have to go to work until 1/5.
Click to expand...

Nice long vacation....same here!

Have you tried to uninstall the Winroute client? I've seen that using the
Proxy or ISA firwall client cause weird errors and usually uninstalling them
clears it up. They put in their own version of winsock.dll and am assuming
that Winroute's client does something similar.

Good luck!

Happy New Year!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Nice long vacation....same here!

Have you tried to uninstall the Winroute client? I've seen that using the
Proxy or ISA firwall client cause weird errors and usually uninstalling them
clears it up. They put in their own version of winsock.dll and am assuming
that Winroute's client does something similar.

Good luck!

Happy New Year!
Click to expand...

I will do that as the last thing before I wipe the disk -
just for curiosity's sake.

I've been using the winroute product for many years on
many machines, and trust it pretty much.

Again, when I just rename the winroute engine (wrdrv.sys)
so the system can't load it, it effectivly is removed.

I'm pretty sure that whatever hosed winsock and tcp/ip
merely clobbered something else in a chain reaction.

I can isolate DNS Client as the critical element - but
the error might be in something it depends on.

BTW, I note that DNS client is disabled on my XP Home
machine - but W2K Pro demands it be enabled. Any wisdom
as to why the difference?

Thanks again,

R
 
In
I will do that as the last thing before I wipe the disk -
just for curiosity's sake.

I've been using the winroute product for many years on
many machines, and trust it pretty much.

Again, when I just rename the winroute engine (wrdrv.sys)
so the system can't load it, it effectivly is removed.

I'm pretty sure that whatever hosed winsock and tcp/ip
merely clobbered something else in a chain reaction.

I can isolate DNS Client as the critical element - but
the error might be in something it depends on.

BTW, I note that DNS client is disabled on my XP Home
machine - but W2K Pro demands it be enabled. Any wisdom
as to why the difference?

Thanks again,

R
Click to expand...

Hmm, that is strange. If disabling the DNS Client service, the only impact
is that it won;t cache any lookups in it;s local cache and all lookups will
be treated as new ones. Is one a DHCP client or both DCHP clients?
Otherwise, not sure of why you are seeing that difference between the two.

I believe both OSs work in a similar fashion. They both require the DHCP
Client service (whether a DHCP client or NOT) in conjunction with the DNS
Client service to resolve names. There's an article that dictates this.

Let me ask, when you do an ipconfig /displaydns, what do you see? If you see
many many entries, then I'm going to venture to say that you have a virus.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
-----Original Message-----
Hmm, that is strange. If disabling the DNS Client service, the only impact
is that it won;t cache any lookups in it;s local cache and all lookups will
be treated as new ones. Is one a DHCP client or both DCHP clients?
Otherwise, not sure of why you are seeing that difference between the two.

I believe both OSs work in a similar fashion. They both require the DHCP
Client service (whether a DHCP client or NOT) in conjunction with the DNS
Client service to resolve names. There's an article that dictates this.

Let me ask, when you do an ipconfig /displaydns, what do you see? If you see
many many entries, then I'm going to venture to say that you have a virus.
Click to expand...
Well, I have to disable the caching, so
ipconfig/displaydns just tells me there's nothing to see.

It works pretty well without caching (in fact old
winroute pro does it's own DNS caching, too, so I never
notice a thing!) The maddening part is that any time I
change anything to do with networking, the DNS client is
turned back on (from disable)...and the reboot takes 10
minutes before services.exe finally stops slamming the
CPU at 100%.

Not likely it was a virus - the machine is pretty locked
down.

What happened to make it toss it's cookies was that I was
trying to feed it an old NT 4.0 driver for a scanner.
When 2K first came out, we had to mainly use NT drivers.
I've done it with *lots* of things. This scanner driver
(one I had used before - it was an old CD to go along
with the old scanner) just really sliced and diced things!

Serves me right for trying to avoid booting to the Win98
partition to use the scanner.

Thanks again,

R.
 
Comments inline below...

In
Well, I have to disable the caching, so
ipconfig/displaydns just tells me there's nothing to see.
Click to expand...

If you enable caching, wait for it to do it's lockup thing and time out, and
then do a /displaydns, does anything show up?
It works pretty well without caching (in fact old
winroute pro does it's own DNS caching, too, so I never
notice a thing!) The maddening part is that any time I
change anything to do with networking, the DNS client is
turned back on (from disable)...and the reboot takes 10
minutes before services.exe finally stops slamming the
CPU at 100%.

Not likely it was a virus - the machine is pretty locked
down.
Click to expand...

Well that's confidence! I would like to say the same about my machines...but
one never knows.
What happened to make it toss it's cookies was that I was
trying to feed it an old NT 4.0 driver for a scanner.
Click to expand...

Some NT4 drivers did work with W2k, but not all.
When 2K first came out, we had to mainly use NT drivers.
I've done it with *lots* of things. This scanner driver
(one I had used before - it was an old CD to go along
with the old scanner) just really sliced and diced things!
Click to expand...

Ouch...Can you identify the dll, do a regsvr32 /u dllname.dll to unregister
it, then delete the dll?
Serves me right for trying to avoid booting to the Win98
partition to use the scanner.
Click to expand...

Lessons learned ... etc.
Thanks again,

R.
Click to expand...

Wish you luck.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
-----Original Message-----
Comments inline below...

In (e-mail address removed)
Click to expand...
posted their thoughts, then I offered mine

If you enable caching, wait for it to do it's lockup thing and time out, and
then do a /displaydns, does anything show up?
Click to expand...
Generally, nothing, as the DNS client just times out
trying to start.
Well that's confidence! I would like to say the same about my machines...but
one never knows.
Click to expand...
Pride cometh before a fall, for sure, but I have a pretty
good handle on what's going on with these machines. The
Winroute Pro is a respectable firewall that I have set to
reject everything that I don't specifically allow - and
I'm pretty cautious about where I surf. Anyway, in this
case it was an old CD I was using.
Ouch...Can you identify the dll, do a regsvr32 /u dllname.dll to unregister
it, then delete the dll?
Click to expand...
No, there was nothing of the sort going on...it was an
extremely old scanner, and the programming was pretty
much 16-bit drivers dragged forward into the NT/9x world.

It'w a moot point, anyway. Using the win2k CD to try a
quick repair got me (at least) to the initial starting
point where I could enable DNS client. However, the
system was (by that time) too much of a hodge-podge of
modules spanning 4 year's time to allow it to do anything
good when trying to process windows updates stuff.

Just gonna have to bite the bullet and rebuild. A shame,
really, as I've been running it for about 2.5 years
without having to do a damn thing to it.

(Lord help me, my old '95 workhorse at the lab is still
virgin after about 5 years!)

Thanks,

R.
 
In
Generally, nothing, as the DNS client just times out
trying to start.
Pride cometh before a fall, for sure, but I have a pretty
good handle on what's going on with these machines. The
Winroute Pro is a respectable firewall that I have set to
reject everything that I don't specifically allow - and
I'm pretty cautious about where I surf. Anyway, in this
case it was an old CD I was using.

No, there was nothing of the sort going on...it was an
extremely old scanner, and the programming was pretty
much 16-bit drivers dragged forward into the NT/9x world.

It'w a moot point, anyway. Using the win2k CD to try a
quick repair got me (at least) to the initial starting
point where I could enable DNS client. However, the
system was (by that time) too much of a hodge-podge of
modules spanning 4 year's time to allow it to do anything
good when trying to process windows updates stuff.

Just gonna have to bite the bullet and rebuild. A shame,
really, as I've been running it for about 2.5 years
without having to do a damn thing to it.

(Lord help me, my old '95 workhorse at the lab is still
virgin after about 5 years!)

Thanks,

R.
Click to expand...

Bless you! Still got a working 95 box!

Well, good luck with everything! Happy New Year!!


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
-----Original Message-----
In (e-mail address removed)
Click to expand...
posted their thoughts, then I offered mine

Bless you! Still got a working 95 box!
Click to expand...
Yes, I need it - I do embedded programming for some
ancient embedded systems. My old dos compilers (using
old 3rd-party memory managers) won't coexist in the NT
memory model.

I like 95 better, 2k second because they're
more 'accessible' in terms of being able to get to the
innards.


But I digress.

I finally characterized the problem a *bit* more: it
seems that once the system stops freezing on startup,
everything is ok until I try a

ipconfig /flushdns

.....then it's another 10 minutes of services.exe slamming
the CPU.

Any thoughts? I'd like to have a clue in case I ever see
this again.

Thanks,

R.
 
In
Yes, I need it - I do embedded programming for some
ancient embedded systems. My old dos compilers (using
old 3rd-party memory managers) won't coexist in the NT
memory model.

I like 95 better, 2k second because they're
more 'accessible' in terms of being able to get to the
innards.


But I digress.

I finally characterized the problem a *bit* more: it
seems that once the system stops freezing on startup,
everything is ok until I try a

ipconfig /flushdns

....then it's another 10 minutes of services.exe slamming
the CPU.

Any thoughts? I'd like to have a clue in case I ever see
this again.

Thanks,

R.
Click to expand...

Wow, not sure. Try reloading TCP/IP again? Have you seen this article?
How to Remove and Reinstall TCP-IP for Windows 2000:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q285034

Hope that helps.

And if you need to use 95 for whatever reason, cool. I know many banks and
other financials still use DOS because of their older financial software
that either they haven't upgraded or there is no upgrade for and would take
too much out of productivity to move/migrate to a new one.

Cheers!




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
a> the DNS client just times out trying to start.

How large is your HOSTS file ?

a> Pride cometh before a fall, for sure, [...]

Incorrect. The correct reading of the proverb is that pride goes before
_destruction_ and that it is _a haughty spirit_ that comes before a fall.
 
Back
Top