I'm having a problem with a 95 machine that hangs on bootup. It doesn't hang everytime but most of the time. When I check the tasks I have msgsrv32 not responding. This does not stop it from booting it just hangs for well over 30 seconds at this point. Once it gets past this it seems like everything is ok. It's more of an inconvenience, so it seems. I need to make sure it's not part of a bigger problem I'm not seeing yet. I've tried MS Article Q136337 with no luck.<br>Any information will be appreciated.<br>
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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MSGSRV32 Not responding and hanging on startup (slow start)
- Thread starter PatrickR
- Start date
Just a thought. If you have an unused NIC installed, and have TCP/IP bound to it, undo the binding, as it may be set to obtain an IP adress automatically. <p>Clive<br><a href=mailto:clive@digitalsky.co.za>clive@digitalsky.co.za</a><br><a href= > </a><br>I assemble and sell these things.
- Thread starter
- #3
I also left out the detail that the slowdown happens after the windows client logon. The pc then sits idle, the startup sound starts and the apps that run on startup then load.<br>The pc in question has two NICs, one connected to the internal network and one to a cable modem. The external NIC gets it's IP adddress dynamically while the internal IP is static. Right now there isn't even power to the hub that the internal NIC is patched into. I know that I didn't have this problem before I added the second NIC but I'm not sure if this problem started right after adding that NIC.<br>Someone once told me they've seen problems with having two 3COM NICs in one pc but I haven't had that experience. Either way one NIC is a 3COM 905B-TX and one is a 3COM 905-TX.<br>Thanks for the input. I might try pulling the NIC from the internal network and trying another one or leaving it out to test it for a couple of days.
Are you loging onto a network? Does this computer have shared drives? If it has shared drives that are set to reconnect on login, then it is probably slowed down because the shares are trying to reconnect. How fast is the network that it is connected to?<br><br> <p> fenris<br><a href=mailto:fenris@hotmail.com>fenris@hotmail.com</a><br><a href= > </a><br>
I'm reasonably sure it's one of the NICs causing the delay, but I don't think it's due to failure or anything like that. For the life of me I can't remember what caused this on a machine I dealt with recently; I do recall that the NIC had a Realtek chipset, and I have found in a number of cases where machines with NICs that have Realtek chipsets are booted, and the network is down or they are not connected, this seemingly eternal delay is experienced. Perhaps you should just check the configuration and remove any unneeded protocols etc.<br><br>Sorry, best I can think of.<br> <p>Clive<br><a href=mailto:clive@digitalsky.co.za>clive@digitalsky.co.za</a><br><a href= > </a><br>I assemble and sell these things.
- Thread starter
- #6
Haven't had a chance to take care of this yet but I'm thinking there's a chance there's something wrong with the setup on the second nic (internal network) too. I had problems when installing the drivers but it has been working when it's patched in to the internal network (only peer to peer). Right now it's not patched in. I'll try it out in the next day or so.<br>Thanks for the responses.<br>
- Status
Similar threads
- Locked
- Question