Discussion Locked

TCP/IP

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a p200 machine with Win 95. It was a networked machine but i have reccently changed it to standalone but i'm having trouble with it.

When i changed the profile to standalone it wouldn't boot but instand hung after the windows password. On ctrl-alt-delete it showed that msgsrv32 wasn't responding.

Finally i removed tcp/ip and the machine booted and now works ok, however, when i put an internal modem into it and tried to setup a dial-up internet connection thru the wizard the system wants to install some software, this turns out to be TCP/IP, and on reboot the machine hangs - again at the same point with the same problem.

The network card is still physically in the machine but it is disabled in device manager.

Any ideas toget round this? - i intend to physically remove the network card to see if this affects thing

Thanks in anticipation

10 replies

by jwpluto

The hanging you describe could very well be a resource conflict. You could even be working with multiple problems at once without realizing it.

Definately remove your nic (and the modem for now). That's one less problem to deal with. After that,remove everything in your network control panel. Then restart the PC and you should get a successful restart with no networking drivers or hardware. (I suggest focusing on getting a reliable boot before proceeding with installing the modem. That wayyou'r working on one problem at a time.)

When your PC boots up clean, install your modem and dial-up networking (if you're going to use the internet, for example).

Now, internet usually requires TCP/IP, and your ISP should provide the necessary settings for that. But those TCP/IP settings are done in the dial-up settings, not the nic card IP settings.

That should take care if your dilemma. If not, you likely have a resource conflict with other added components in your PC. Take out one card at a time until you get a successful boot. That should tell you where the problem lies.

by Member 30653292

Just to note - i checked technet re msgsrv32 & it claims a power mgt issue can be at fault, however, there are no screen savers & the power mgt icon is not in the control panel

by mphoffar

You probobly don't have to remove the NIC. I would clean out my network stack first, then rename the wshtcp.vxd file to force a copy from the cabs when it's install from the modem. When prompted, answer no to keeping the newer files.

The other thing I'd make sure of is that within Client for ms networks, I have quick logon set and user level share access set to make sure I'm not going to pull any info from a server.

Good luck to you

Mark

by zbopz

Make sure windows mesaging and anything associated with it is uninstalled. Delete all connections in Dialup networking, THEN uninstall DialUp networking. Unbind Tcp from everything despite the warnings. (Install netbeui protocol if needed)Remove thenic and any dialup adapters out of the network configuration.

*Have the W95 set-up disk ready*.

Use "find" to locate the following files and delete them: MSTCP.DLL, mstcp.dll, winsock.dll, wsock.vxd, wshtcp.vxd, wshtcp.vxd, pppmac.vxd, splitter.vxd, VTCP.386, vtcp.386, vdhcp.386, vip.386, vnbt.386. Run Regedit and go to HKEY_Local_Machine\System\Current Control Set\Services\VxD\and delete the key MSTCP. Everything will be replaced new on restart.

Restart, (Let the system copy the OLDER version of any files) reinstall Dialup networking, Reconfigure the network as needed. This will give you a fresh copy of TCP/IP and rebuild the DUN files as well.

Good Luck,
Ken

by bv2

Remove all of your networking services and protocols, then remove dial-up networking. Run regclean to fully remove references to these services and protocols. Reinstall Dial-up networking and your TCP/IP. Before you reboot, check to make sure that windows logon is your preferred method to connect.

This discussion is closed to new replies.