Discussion Locked

Gateway Key in Registry

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a machine that originally would give an fatal error message when I attempted to use winipcfg. It would not ping 127.0.0.1 on that, I got a 10045 error. I installed a second TCP/IP protocol which forced it to reinstall the necessary files fromthe cabs. After I did that, I was able to do the loop back ping, I checked the winipcfg which came back telling me that the gateway was not held in the system even though it was added in the TCP/IP conf. It does show up there when I check it, but when I do winipcfg it is blank. I thought if I were to hack into the registry and place it there it would allow it to be registered in the system. Would this work? If so, where do I find that key in the registry. Any help would be appreciated as I don't really want to have to format the machine and start over. Thanks in advance

8 replies

by kgosnell

You likely have a spyware app hidden somewhere , get Ad-Aware or equivelent to purge your system , as they use the Gateway Protocol to enable them , there are some commercial apps that use it also , and again they are hidden. But first and formost ,deep scan your system for a possible Virus/Worm as this is a symtom, because resistance to change suggests it is being rewritten as fast as you write a new command , and could be any of the latter annoyances
Good luck

by kafru

This machine has never been connected to the internet and the teacher who uses it doesn't use floppy disks. Educational games are the only things that are loaded on it. I ran a virus check on it with updated definitions and it doesn't appear to be a virus. Thanks anyway.

by kgosnell

I found some material on winipconfig in my data base , it is for trouble shooting , do you want it? It is sort of lengthly and I don't have the time to sort it now.Luck , Kyle

by kafru

In case someone else has this problem, here is how to take care of the problem. Apparently some of the winsock files became corrupted during an install of program. That is why I got the 10091 error code "Fatal Error" when I did a winipcfg. To correct the problem go to a DOS prompt and go to the following folder. C:\windows\ws2bakup Once there run the ws2bakup.bat file and it will reinstall the original winsock files and delete the incorrect versions. Reboot your machine. It should be fixed, but if you still have problems pinging out to your router try a release all and then renew again in the winipcfg.

This discussion is closed to new replies.