MicroSoft Network Client

Topic

New Reply

My Win 98SE boots to the Network Client waiting for a password. The desktop minus icons is visible along with the wallpaper. I have no password and am only required to hit the enter key. The boot process stops there. When I hit “CTRL” “ALT” “DEL” is says magsrv32.exe not responding. I have used the SFC to replace that file and I still get the freeze up. I have to reboot sometimes 3 or 4 times before I can use the machine. Short of flattening the hard drive and starting over, does anyone have a remedy?

I can not remove the Microsoft Network Client because I have a little 2-computer network going.

Thanks.

Reply | Quote

Replies

Try to re-install Microsoft Network Client.
To do this, right-click “Network Neighborhood” icon on the desktop and choose “Properties” from pop-up menu. Highlight Microsoft Network Client and press Remove button. Reboot computer and repeat the steps, then press Add button and choose Client, Microsoft Network Client. Be sure NetBEUI protocol is installed on both your computers. (If not, press Add, choose Protocol, NetBEUI protocol.) Reboot, if prompted.
To logon to the network automatically, use TweakUI utility. If you don’t see it on Control Panel, download and install it (http://support.microsoft.com/default.aspx?…b;EN-US;q190643).

I hope it will help you.
Happy holidays!

Reply | Quote

I have a similar problem — mine freezes on shutdown — even after re-installing the MS networking protocols. The problem seems to come from the host PC not responding to the client when it logs on. That, in turn, *seems* to come from some power-management “feature”. I have had some success with the following. Disable all power management schemes (change everything to always on). Change network login to “Windows Login”. (This won’t disable any networking features, it just tells the PC to not bother re-connecting at boot-up.) Use Tweak-UI as mentioned in other post. Always reboot the host computer as well as the client computer after a msgsrv32 crash. Additionally, I have found that booting the client PC with the networking card not installed, and inserting the card after boot, is the most reliable way to get the network back to proper functioning. I do this on a laptop w. a PCMCIA NIC, so it’s easy.

Note that I;m using “client” and “host” just to distinguish between the “problem” PC and the rest of the network. My network is a simple P2P on Win98.

Perhaps someone can jump in and explain what is really happening …

K.

Reply | Quote

I’ve had problems previously with Win98 computers freezing up when shutting down. I can’t get into Microsoft’s knowledge base right now to give you a link, but I know there’s a fix out there for the shutdown freeze up. I think there’s actually two seperate fixes for different problems. One has to do with mapped drives, and the other is just a shutdown fix or something like that. I know we had laptops and desktops that experienced the problem here, but after applying the fixes to them, they quit freezing up during shutdown. One side effect of the fix however, is you get screen saver or blank program tab/button down in your taskbar afer the screensaver has been running and you move your mouse or hit a key to make the screensaver go away. No big deal, you just have to click the blank program tab/button in your taskbar and it disappears.

Reply | Quote