Windows Forum

Ask something
Discussion Locked

Network Protocol Problems In Win 95

0 helpful
14 replies

by coomzy

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

Whilst teching a customer, trying to get him connected, I had to perform a comms refresh and replace the network stack. I removed the lot and reinstalled 'client for ms networks', 'dial up adapter' and 'tcp/ip' - although ipx/spx and netbui kept trying to get their oar in. After successfully reinstalling and rebooting I kept getting this error message when trying to authenticate username and password :-

'' error 731 dial up networking could not negotiate a compatible set of network protocolsyou specified in the server type settings, check your network config and try again''.

I emptied the stack and reinstalled again, only to get the same error. Is there anyone out there who could offer a solution, any offers would be greatfully received. - Alex

14 replies

by dmiles

Seems as though the PROTOCOL.INI-is used in windows directory to determine the parameters for the protocol and network adapter drivers.
[network.setup] entry
version= current software version
netcard=the network adapter driver
transport=name of the network transport driver protocol
lana#=identifies the bindings between network adapter and network protocol

by tuck46

first rename your *.386 files and then uninstall and reinstall dial up networking. That usually takes care of the problem

by mphoffar

Unless there's a reason to keep netbeui and IPX, get rid of them.

A lot of times, what I've had work has been to rename the wshtcp.cxd file after removing all of your network components, rebooting and then rebuilding your stack.

Mark

by burtsa

How I handle this problem is first go to network properties and remove everthing. Then go to control panel and to Add/Remove programs then to the windows setup tab and remove the communications option. Reboot. the back to Add/Remove and put the communications back. In the network settings, unless you need them, I would remove everthing but dial-up adapter, TCP/IP, and Client for Microsoft Network.
Reboot.
In you connection shortcut I would also unselect NetBUEI and IPX. Most providers won't route those protocols anyway.

hope this helps.

Shawn

by zbrain75

First of all, Microsoft advises using NetBEUI as a primary protocol for RAS communications. Also is you are dialing into an NT server before 3.5, RAS was only supported using NetBEUI. Therefore my advise is to install NetBEUI on the client computer to solve your problem. If you're running a typical NT network, your computer using the RAS connection may be able to access network resources through the RAS server (it provides support for other transport protocols) reguardless of their transportprotocol. I know this works for NT workstation, but I'm not sure how it works for 95. Make sure you dial in using PPP.

This discussion is closed to new replies.