 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows 2000 / Update / August 2006DHCP "hung" every boot since KB914388 (MS06-036)
Starting with the reboot right after installing KB914388 (MS06-036) and now with *every* subsequent boot, my NT5.0 SP4 system takes an extra 20 or 30 seconds to fully load - it appears like it is hanging on the "preparing network" screen before the desktop finally, eventually appears. This entry shows up, now, for every boot since the patch: Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7022 Description: The DHCP Client service hung on starting. -- My LAN runs into a DLink DI-524 with DHCP enabled. My three NT5.1 SP2 systems patched fine and are not having this problem. Do you use a VOIP system call ShoreTel by any chance? peter > Starting with the reboot right after installing KB914388 > (MS06-036) and now with *every* subsequent boot, [quoted text clipped - 15 lines] > My LAN runs into a DLink DI-524 with DHCP enabled. > My three NT5.1 SP2 systems patched fine and are not having this problem. Nope. > Do you use a VOIP system call ShoreTel by any chance? > [quoted text clipped - 7 lines] >> eventually appears. This entry shows up, now, for every boot >> since the patch: With a clean load, installing KB914388 did not cause any problem. After inatalling the voip client, dhcp cleint hung starting up. However, removing the voip client did not fix the problem, only uninstalling KB914388 will. Tried reinalling tcp/ip and winsock, did not help. Peter > Nope. > [quoted text clipped - 9 lines] > >> eventually appears. This entry shows up, now, for every boot > >> since the patch: Hello, same problem here. After installing KB914388 the startup slows down and enties in the system log show that the dhcp client does not start correct (the message is in german so this is not the exact error message). The only solution was uninstalling KB914388. We have no voip clients in use. Any solutions? Thanks Jens > With a clean load, installing KB914388 did not cause any problem. After > inatalling the voip client, dhcp cleint hung starting up. However, > removing the voip client did not fix the problem, only uninstalling > KB914388 will. Tried reinalling tcp/ip and winsock, did not help. > > Peter I'm just sorry that I didn't find this link a week ago though the real meat only came in earlier this week. I guess I can put my entire network stack, services, registry keys, etc back together and stop digging through ntbtlog and userenv. Removed the "patch" and my machine just flies again and EVERYTHING even remotely connected to the network is snappier and more stable. Permarping Network Connections is the big winner, going from 3+ min to 3+ sec. FWIW make sure that you note all of the dire warnings that you're given when you remove the patch. I was told that a handful of other things could go "phoom!" if I took it out. So far nothing else has crashed. This "patch" certainly covered any vulnerabilty that I might've had to getting any good work done ofver the past few days. I'm disabling Windows Update so it'll stop pestering me continually and I'll turn it back on periodically to check to see if this "patch" is still included. Thanks Bill. :-( :-0 Any news to this issue ?? Jens I think there is a similar thread in networking that has the answer. > Any news to this issue ?? > > Jens > I think there is a similar thread in networking that has the answer. > >> Any news to this issue ?? >> >> Jens Yes, this fix works for me, as well: <SteveFriday@discussions.microsoft.com> wrote: > We received a fix to test and on one machine it has been successful, > the fix was to edit [quoted text clipped - 9 lines] > Regards > Steve |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.