Win98SE won't talk TCP/IP on network card

I'm trying to setup my fiancee's W98 2nd Ed. PC to talk on my home
network (1 XP pro box, 1 Linux server, 1 WinSE box, hub, router, and
cable modem to comcast). Her machine has a modem and has worked with
it, so I know TCP/IP works. I've tried a Lynksys Etherpro II card and
a Realtek (CompUSA branded) card, and neither works. In both cases,
the PC recognizes the card, the drivers load, the card settings are
all Ok, TCP/IP settings are ok, but the card won't talk on the
network. I've tried switching cables, hub ports, and (as mentioned)
network cards. The machine won't negotiate DHCP (when that's enabled)
and won't even talk to the other boxes when I hard-coded it's IP/mask
to talk on the 192.168.1.* internal range. The "it's alive" LED on
the card is on -- and on hub, but the FDX LED at the hub isn't on for
this machine (doesn't matter how machine is connected to the hub).
I seem to recall something about Win98 boxes needing some special
majic to commune with the rest of the world, but I haven't had to mess
with that for a couple years now, and I've misplaced those brain cells
...... On the other hand I can still recall the lyrics of virtually
every top-40 song from the 70s.

if the modem was used for internet , the tcp/ip bindings for file/printer
sharing may be disabled...

double check your bindings for the nic..


"pt" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> I'm trying to setup my fiancee's W98 2nd Ed. PC to talk on my home
> network (1 XP pro box, 1 Linux server, 1 WinSE box, hub, router, and
> cable modem to comcast). Her machine has a modem and has worked with
> it, so I know TCP/IP works. I've tried a Lynksys Etherpro II card and
> a Realtek (CompUSA branded) card, and neither works. In both cases,
> the PC recognizes the card, the drivers load, the card settings are
> all Ok, TCP/IP settings are ok, but the card won't talk on the
> network. I've tried switching cables, hub ports, and (as mentioned)
> network cards. The machine won't negotiate DHCP (when that's enabled)
> and won't even talk to the other boxes when I hard-coded it's IP/mask
> to talk on the 192.168.1.* internal range. The "it's alive" LED on
> the card is on -- and on hub, but the FDX LED at the hub isn't on for
> this machine (doesn't matter how machine is connected to the hub).
> I seem to recall something about Win98 boxes needing some special
> majic to commune with the rest of the world, but I haven't had to mess
> with that for a couple years now, and I've misplaced those brain cells
> ..... On the other hand I can still recall the lyrics of virtually
> every top-40 song from the 70s.

First, go through this article:

169790 How to Troubleshoot Basic TCP/IP Problems
http://support.microsoft.com/?id=169790

Next, let us know where it errors out at. We can go from there to resolve
this.

--
Thank you,

Brennan Crowe
Microsoft corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

"Brennan Crowe [MSFT]" <(E-Mail Removed)> wrote in message news:<#(E-Mail Removed)>...
> First, go through this article:
>
> 169790 How to Troubleshoot Basic TCP/IP Problems
> http://support.microsoft.com/?id=169790

With sections from the specified KB article:


Try to connect to another computer on your network...
Can't ping *ANY* other 192.168.1.* computers on same network

ping the loopback address (127.0.0.1)
ping localhost works (HOSTS.SAM)
ping 127.0.0.1 works

Ping Your Computer's IP Address
winipcfg says local IP is 192.168.1.13/255.255.255.0
Default gateway 192.168.1.1
(all of which I set manually)
ping 192.168.1.13 works

display all mappings currently in the ARP cache
No ARP Entries Found

Verify the Default Gateway
Can't ping gateway (192.168.1.1) from the machine in question. All
other machines on network can ping gateway successfully.

Ping the IP Address of the Other Computer
As stated, can't ping (or be pinged by) any other 192.168.1
machines.
From any other machine on network, can ping the remaining machines.

Verify Persistent Route Table Entries
C:\WINDOWS>route print
Active Routes:
Network Address Netmask Gtway Address Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.13 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.13 192.168.1.13 1
192.168.1.13 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.13 192.168.1.13 1
224.0.0.0 224.0.0.0 192.168.1.13 192.168.1.13 1
255.255.255.255 255.255.255.255 192.168.1.13 0.0.0.0 1

Use the TRACERT Command
tracert to 192.168.1.13 works
tracert to 192.168.1.1 fails (Request timed out)


Check the HOSTS File
127.0.0.1 localhost

Check the LMHOSTS File
The typical "nuttin but comments" LMHOSTS.SAM file (3717 bytes)



>
> Next, let us know where it errors out at. We can go from there to resolve
> this.

(E-Mail Removed) (pt) wrote:

>"Brennan Crowe [MSFT]" <(E-Mail Removed)> wrote in message news:<#(E-Mail Removed)>...
>> First, go through this article:
>>
>> 169790 How to Troubleshoot Basic TCP/IP Problems
>> http://support.microsoft.com/?id=169790
>
> With sections from the specified KB article:
>
>
>Try to connect to another computer on your network...
> Can't ping *ANY* other 192.168.1.* computers on same network
>
>ping the loopback address (127.0.0.1)
> ping localhost works (HOSTS.SAM)
> ping 127.0.0.1 works
>
>Ping Your Computer's IP Address
> winipcfg says local IP is 192.168.1.13/255.255.255.0
> Default gateway 192.168.1.1
> (all of which I set manually)
> ping 192.168.1.13 works
>
>display all mappings currently in the ARP cache
> No ARP Entries Found
>
>Verify the Default Gateway
> Can't ping gateway (192.168.1.1) from the machine in question. All
>other machines on network can ping gateway successfully.
>
>Ping the IP Address of the Other Computer
> As stated, can't ping (or be pinged by) any other 192.168.1
>machines.
> From any other machine on network, can ping the remaining machines.
>
>Verify Persistent Route Table Entries
> C:\WINDOWS>route print
> Active Routes:
> Network Address Netmask Gtway Address Interface Metric
> 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.13 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.1.0 255.255.255.0 192.168.1.13 192.168.1.13 1
> 192.168.1.13 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.1.255 255.255.255.255 192.168.1.13 192.168.1.13 1
> 224.0.0.0 224.0.0.0 192.168.1.13 192.168.1.13 1
> 255.255.255.255 255.255.255.255 192.168.1.13 0.0.0.0 1
>
>Use the TRACERT Command
> tracert to 192.168.1.13 works
> tracert to 192.168.1.1 fails (Request timed out)
>
>
>Check the HOSTS File
>127.0.0.1 localhost
>
>Check the LMHOSTS File
>The typical "nuttin but comments" LMHOSTS.SAM file (3717 bytes)
Not related, but,
I read somewhere, that all those comments get parsed, every time.
Slows down already slow machines. Just a thought.


>
>
>
>>
>> Next, let us know where it errors out at. We can go from there to resolve
>> this.

Plug in the cat5 cable.

Just kidding, but, are you sure there is hardware connectivity?
Seems really suspicious!

Jim

If you can't even ping the default gateway when it's set correctly you
likely have a hardware or NIC driver problem.

--
Richard G. Harper ((E-Mail Removed)) MVP Win9x
* Please post all messages and replies in the newsgroup so that
* all may benefit. Private mail is usually not replied to.
* Help US Help YOU ... http://www.dts-l.org/goodpost.htm


"pt" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> "Brennan Crowe [MSFT]" <(E-Mail Removed)> wrote in message
news:<#(E-Mail Removed)>...
> > First, go through this article:
> >
> > 169790 How to Troubleshoot Basic TCP/IP Problems
> > http://support.microsoft.com/?id=169790
>
> With sections from the specified KB article:
>
>
> Try to connect to another computer on your network...
> Can't ping *ANY* other 192.168.1.* computers on same network
>
> ping the loopback address (127.0.0.1)
> ping localhost works (HOSTS.SAM)
> ping 127.0.0.1 works
>
> Ping Your Computer's IP Address
> winipcfg says local IP is 192.168.1.13/255.255.255.0
> Default gateway 192.168.1.1
> (all of which I set manually)
> ping 192.168.1.13 works
>
> display all mappings currently in the ARP cache
> No ARP Entries Found
>
> Verify the Default Gateway
> Can't ping gateway (192.168.1.1) from the machine in question. All
> other machines on network can ping gateway successfully.
>
> Ping the IP Address of the Other Computer
> As stated, can't ping (or be pinged by) any other 192.168.1
> machines.
> From any other machine on network, can ping the remaining machines.
>
> Verify Persistent Route Table Entries
> C:\WINDOWS>route print
> Active Routes:
> Network Address Netmask Gtway Address Interface Metric
> 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.13 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.1.0 255.255.255.0 192.168.1.13 192.168.1.13 1
> 192.168.1.13 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.1.255 255.255.255.255 192.168.1.13 192.168.1.13 1
> 224.0.0.0 224.0.0.0 192.168.1.13 192.168.1.13 1
> 255.255.255.255 255.255.255.255 192.168.1.13 0.0.0.0 1
>
> Use the TRACERT Command
> tracert to 192.168.1.13 works
> tracert to 192.168.1.1 fails (Request timed out)
>
>
> Check the HOSTS File
> 127.0.0.1 localhost
>
> Check the LMHOSTS File
> The typical "nuttin but comments" LMHOSTS.SAM file (3717 bytes)
>
>
>
> >
> > Next, let us know where it errors out at. We can go from there to
resolve
> > this.

Jim <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>. ..
> (E-Mail Removed) (pt) wrote:
>
> >"Brennan Crowe [MSFT]" <(E-Mail Removed)> wrote in message news:<#(E-Mail Removed)>...

[snip]

>
> Plug in the cat5 cable.
>
> Just kidding, but, are you sure there is hardware connectivity?
> Seems really suspicious!

As stated in OP, I've switched NICs, cables, and hub ports. The other
Win98 PC works when using the troublesome PC's cable and hub port.

>
> Jim

"Richard G. Harper" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> If you can't even ping the default gateway when it's set correctly you
> likely have a hardware or NIC driver problem.

I've tried 2 different NICs (each with it's associated drivers). I've
tried different cables.

>

[snip]

(E-Mail Removed) (pt) wrote:

>Jim <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>. ..
>> (E-Mail Removed) (pt) wrote:
>>
>> >"Brennan Crowe [MSFT]" <(E-Mail Removed)> wrote in message news:<#(E-Mail Removed)>...
>
>[snip]
>
>>
>> Plug in the cat5 cable.
>>
>> Just kidding, but, are you sure there is hardware connectivity?
>> Seems really suspicious!
>
>As stated in OP, I've switched NICs, cables, and hub ports. The other
>Win98 PC works when using the troublesome PC's cable and hub port.
>
>>
>> Jim

Sorry, jumped in late. Went back and grabbed your original post and
went through it.

Also read the post from Haggis:

"if the modem was used for internet , the tcp/ip bindings for
file/printer
sharing may be disabled...

double check your bindings for the nic.."

Did you dig into the adapter settings to check the bindings?

Also. After all the changes you've made to your machine, you
might try something do every now and then. I have absolutely no idea
if this does *anything*. I'd like to hear from someone who
knows if it's valid.

Boot into safe mode. Check the Device Manager. You may see
devices that are no longer physically installed. Try removing
them.

Does Windows load these phantom drivers? Do they take up
resources? Like I said, I don't know, but would like to.

BTW,

"with that for a couple years now, and I've misplaced those brain
cells
...... On the other hand I can still recall the lyrics of virtually
every top-40 song from the 70s."

I can sure relate to the missing brain cells. And perhaps the reason
you remember those songs so well, is like me you listen to a radio
station that plays 'em all day, every day.

Jim

(E-Mail Removed) (pt) wrote:

>"Brennan Crowe [MSFT]" <(E-Mail Removed)> wrote in message news:<#(E-Mail Removed)>...
>> First, go through this article:
>>
>> 169790 How to Troubleshoot Basic TCP/IP Problems
>> http://support.microsoft.com/?id=169790
>
> With sections from the specified KB article:
Also look at:
Microsoft Knowledge Base Article - 238135
How to Troubleshoot Internet Connection Sharing Problems

Jim