Problem w/Linksys LNE100TX TCP/IP binding in Win98

I am trying to set up a cable modem with a Linksys LNE100TX Fast Ethernet Adapter in my Windows 98 PC. Have installed NIC and drivers. This seems okay. Have installed TCP/IP, but the NIC doesn't appear to be bound to it.
In the network dialog box, I have the following items:
Client For Microsoft Networks
Linksys LNE100TX Fast Etherner Adapter
TCP/IP
When I look at the Properties, Bindings for TCP/IP, all I see is this:
Client For Microsoft Networks
Shouldn't I also see:
Linksys LNE100TX Fast Etherner Adapter
If this is not the problem is there some way to confirm that there is communication between the modem and the NIC?

1. RE: Problem w/Linksys LNE100TX TCP/IP binding in Win98
lbyard Jan-19-01 06:38 PM
In response to message 0

It looks correct. You only have one network adapter. The TCP/IP binding is not explicit unless you have more than one adapter. If there is more than one adapter, the adapter bindings are shown in the main Network Configuration, not in the Properties, Bindings. Temporarily add a dial-up adapter and you will see what I mean.
My cable MODEM has a browser interface. If yours does and you see it, the PC and cable MODEM are talking. You may have to Start, Run, winipcfg, select the network adapter and release and renew the IP address lease.
Another indictor: You should see solid LINK and flashing ACTivity LEDs on the network adapter and cable MODEM. The LINK LED might be on the back of the cable MODEM.
To test the Internet connection, open a DOS Window and type:
C:\>ping 216.92.56.121.
If you get a response you are talking to both the cable MODEM and the Internet (my web site).
Larry

2. RE: Problem w/Linksys LNE100TX TCP/IP binding in Win98
march1970 Jan-19-01 07:01 PM
In response to message 1

Thanks for the response. I guess I have some other problem because the solid LINK LEDs are lit up on both the MODEM and the network adapter but the ACTivity LEDs are not lit up (solid or flashing).
I am not in front of that computer right now, but I will try the winipcfg and the ping.
Thanks for your help.