Windows Forum

Ask something
Discussion Locked

DUN DHCP Sets IP to Same as Gateway

0 helpful
8 replies

by gniazdo

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Windows 95, DUN ver 1.4 for 95. Computer dials and connects to ISP but sets the ipaddress to the same as the Gateway address. This prevents connecting to the internet or pinging any name/IP address except the gateway, which essentially is the same as pinging local host. Tried uninstalling/reinstalling DUN, IE 5.5, tcpip . etc. Not having any luck. I think a Reg hack might fix this but I havn't been able to find one yet

8 replies

by sprocket99

You do not need to set a gateway if you are letting the ISP set your IP address. Make sure that there is nothing set in your gateway setting in your TCP/IP for the Dial-up adapter.

Rename the following files from the windows system directory to .old:
vtcp.386
vip.386
You will need to uninstall the DUN.
and reinstall the DUN
Do not reboot until you reinstall TCP/IP.

by gniazdo

Tried but did not work. Never set anything in the TCP/IP Properties for the Dialup Adapter. Everthing is default

by mphoffar

Having the Gateway Address and the IP address the same is normal when you're using a dialup. I would certainly run the deinstall of the upgraded DUN package clear out your Network Stack and then start fresh by installing DUN and having that build your stack for you.

Mark

by gniazdo

It is not normal to have the gateway address the same as your computers IP address in a dial up connection. If you have these settings then all you have is a loop. IF your IP address is 192.168.1.1 and Your gateway is the same. When you go to look for a web site the request just loops around you computer never making it to the internet.

by gniazdo

Clear out network stack? Do you mean removing all items that are listed in the network properties box. ie. dialup adapter, tcp-ip, client for ms networks?

by mphoffar

From all comments to everyone, I think you're leaving a lot of pertanent information out of this question and are confusing different things. At this point, I would suggest spending the money at MS or reinstalling from scratch.

Mark

by gniazdo

I gave up and formated and reinstalled. Of course everything now works. This is the second time I have come across a corrupted tcpip stack problem that removing and reinstalling DUN and networking components could not fix. I am sure that it is something screwed up in the registry. One system that I did what I call a Dirty install on (deleted the user.dat and system.dat) and then reinstalled windows over the existing window corrected the TCPIP problem. If only I knew which keys to remove to fix the tcpip problems.

by gniazdo

I came across a similar problem that I was able to fix. The computer would give an error message everytime you opened IE6 and then restart it self and then give the same message. I tried pinging know addresses and got only time outs. Then I found something in the registry that clued me in. it was an entry for new.net . I went to add remove programs and found a listing for new.net and uninstalled it. Without ever restarting I was able to ping addresses and open web pages. I think new.net is one of those programs that gets installed along with Gator (SPYWARE). Its purpose I think is to create new domains that are NOT sanctioned by ICANN. Like .BMW (don't know if that is a real example but you get my point). So if you are having the same typeproblem as listed above look for new.net and uninstall it.

This discussion is closed to new replies.