//flex table opened by JP

Click to See Complete Forum and Search --> : Winsock problem? (pings in DOS but not in Windows)


john.s
11-04-1999, 12:03 AM
I have a Win98 P100Hz that is networked with my AMD333. Both have their own IP numbers and are hooked up to a cable modem through a hub. Both used to surf the web great but now, after changing to new NICs in both computers, the P100 no longer can (while the AMD still works fine).
The P100 can ping a IP from DOS - but not from Windows (ruling out an internet connection problem).

Not only does IE5 not work, IPC and OE don't either (ruling out a browser problem).

The two computers still network fine, it's just that the P100 isn't able to reach a server from within Windows (ruling out a problem with the network configuration).

Switching the NICs in the wto computers didn't help (ruling out a problem with a NIC).

The AMD still worked after setting it up with the P100's IP number (ruling out problems with the IP number or cable modem).

The problem seems to be with the Win98 operating system on the P100 - maybe its Winsock? (I extracting new Winsock.dll and wsock32.dll files from the setup CD - didn't help.)

I'm stumped. Only solution seems to be to reinstall Win98 but I'm hoping someone has a better answer!

Axel
11-04-1999, 03:14 PM
I'd say that you might have a bad driver for the NIC. That's one possibility - then there are your network bindings and protocols. You can ping your brains out, but no higher protocols will work if that has been wrecked.
I'm not too familiar with cable modems.
Can you go back to IE 4.01 and ditch 5.0? - Had to do that several times myself to get some systems working.
Also win95 had a nasty habit of putting back it 42kb winsock and putting any other winsock into the winsock.old file in the same directory - that might be why your IE5 stopped working. Perhaps win 98 does the same thing.
So - looks like you have two different problems. possible bad/replaced winsock, and a protocol binding problem.

john.s
11-05-1999, 11:59 AM
Thanks - I found that the problem was with the computer hardware itself. Didn't like the card (which was fine). Switched to another computer and everything's great.