TCP doesn't work, windoze 98se.
Quasimodo
rebuilding all the drivers I have the following symtoms;
I cannot surf the web by name or IP, internal IP or external IP.
My '98 workstation has a private ip of 192.168.1.100 and is being
routed through my linksys router 192.168.1.1 with the most recent
firmware. My 98 workstation successfully gets a dhcp address from the
linksys & can ping any private or public pingable address. I tried
using netscape browser with the same results, ruling out explorer. The
problem persists if I use a static instead of dhcp.
My laptop (192.168.1.101) browses fine by name or IP, ruling out my
internal network.
It appears my TCP package/install/stack/whatever is corrupt on my win
98 workstation. I've removed my 10/100 adapter & reinstalled it. I've
also replaced it with a different model, all of which were known
goods. I have no personal firewall on my workstation that would cause
this.
snmp (ping) works fine. I can ping my dns servers & anything else. I
can't test by telneting, as all the packages that rely on TCP are
broken (telnet, ftp, etc). Not a real heavy microsoft guy, so if
someone could tell me how to fix this, I'd be very appreciative. I'm
not interested in re-os'ing my workstation, thanks. This should be
easily fixable without re-os'ing. IMHO. -Mike
David H. Lipman
If you execute WINIPCFG.EXE, do you get an error ?
Dave
"Quasimodo" <famous...@hotmail.com> wrote in message
news:66657c84.02100...@posting.google.com...
Rick Wintjen
Have you tried ping with a name, like www.yahoo.com, or only with the IP
numbers?
cjt
>
<snip>
If pinging by numeric address doesn't work, pinging by domain name doesn't
have a prayer of a chance.
Rick Wintjen
The way I read his post, ping worked, unless I missed something. He says
he can't surf, but can ping. I was trying to eliminate DNS problems.
Andrew Golebiowski
Some 2-3 weeks ago I raised the same questions. Same Windows 98SE. I
replaced a "normal" NIC with the wireless one from SMC and observed the same
behaviour:
I could:
ping from DOS window another computer in my home network - "ping
192.168.2.28"
ping any outside computer by IP address - "ping 24.167.23.111"
ping an outside computer by domain name - "ping www.yahoo.com"
What I could not do was to surf:
Netscape complained that it coult not open a socket
IE was playing dead for a while after which it loaded a local file with some
useless messages.
All imaginable combinations of troubleshooting involving old NIC, connecting
directly to the modem, reinstalling Windows etc did not work. I am sure that
TCP was installed correctly - well, as far as we talk about characteristics
you can control - after all I could ping. I am sure that the problem was
somewhere in Window but... contacting both customer support from SMC and
Microsoft was a waste of time.
After some 2 day I gave up and reinstalled the Windows clean ie. putting new
HD, formatting it etc. Guess what... It works.
Sorry that I cannot give you a more valuable advice. I understand that cold
loading Windows is a rather extreme solution.
The funny thing is that before I bought the router my home network worked
perfectly with a hub and the NAT software running on this particular box
that experienced the problem.
Andrew
"Quasimodo" <famous...@hotmail.com> wrote in message
news:66657c84.02100...@posting.google.com...
Wicksy
reinstalling TCP/IP:
go to Control Panel > Network
remove *ALL* the TCP > IP protocols from the list.
reboot.
go to Control Panel > Network
Add > Protocol > Microsoft > TCP/IP
do this once for your NIC, and once for your Dial-up adapter.
reboot.
u'll have to reconfigure your TCP/IP settings, but it's a lot quicker than
reinstalling windoze.
post back the results please.
"Quasimodo" <famous...@hotmail.com> wrote in message
news:66657c84.02100...@posting.google.com...