View Full Version : NIC not binding with TCP/IP
12-25-2002, 12:07 PM
Anyone have any suggestions on the following problem:
I've just done a clean install of Win98 on an IBM ThinkPad 380ED and am using a 3COM PCMCIA NIC. The NIC is properly installed with the latest drivers and TCP/IP is configured. The card is binded to TCP/IP under Network Properties, however when I run winipcfg the NIC is not listed (only PPP Adapter shows). I would think that is not listed because it's not binding correctly but it's Properties tells me it is. Everything looks to be installed and configured correctly. It's connected directly to a cable modem which works fine on another Win98 PC. The NIC shows a steady green light, but no activity. Any ideas on why the NIC is not listed under IP Configuration? Thanks for any suggestions.
12-25-2002, 12:15 PM
From the "Start" button, select "Settings," then "Control Panel."
Open the "Network" icon.
If your NIC is "plug and play," Windows 95/98 should automatically detect its presence and configure it properly. If your NIC does not appear under the "Configuration" tab, you will need to add it:
Choose the "Add. . ." button, then choose the "adapter" network component.
Select the manufacturer from the list on the left, and the card model from the list on the right.
If your NIC is not listed, choose "Have disk. . ." and use the floppy disc or CD-ROM that came with your NIC to add the software necessary to run your adapter.
Choose the "OK" button when finished.
12-26-2002, 12:16 AM
Hi YODA74, thanks for your reply.
The NIC is listed under Configuration and under Properties->Bindings, TCP/IP is checked. That should bind the aodapter to the protocol but it still doesn't show in the list when I run winipcfg.
12-26-2002, 11:01 AM
Try removing, then reinstalling TCPIP
12-26-2002, 11:17 AM
I hate it when that happens.... One other thing, I always use a modem and dial-up connection to confirm the TCPIP stack, at least for the PPP adaptor. That way you KNOW it's only the NIC adapter's stack that's screwed up.....
For whatever reason I've seen this more often with OEM 98 loads than retail loads..
12-26-2002, 11:41 AM
I've tried uninstalling and reinstalling TCP/IP several times but to no avail.
The ThinkPad doesn't have a modem so I can't test the stack for the PPP Adapter. I can try to get a hold of one though and give that a shot. As for the NIC's stack. If that is bad as you say happens with the retail versions, is it a problem with the card or with winodws? Is there anyway to fix it?
Thank you both for replying.
12-26-2002, 11:44 AM
you said it happens with OEM versions more often than retail. the install was from an OEM cd.
12-27-2002, 01:56 AM
I had a problem with TCP/IP when installing a cable modem one time. I had to reformat the whole drive to get it working again. Best option is to reformat the drive. IF you have try to uninstall and reinstall the tcp/ip protocol, i think you need to reformat it. I know it drastic but it could be the only way. Go to Here (http://support.microsoft.com/default.aspx?scid=fh;EN-US;kbhowto&sd=GN&ln=EN-US&FR=0) to try and search for a better solution. Try typing in Tcp/ip problems. CYa
12-27-2002, 12:25 PM
Well the next step is to jump back to no-network. Remove the NIC and network services files from the OS. Then re-install.
I'm not brainy enough to know why, but the cause of problem (at least I think) is on machines that have been loaded using a "msbatch.inf" file.
This file supplies the answers to setup requests during installation.
Sometimes an inconsistency or mistake occurrs in a registry key. (after someother hardware detection event) Any attempt to reconfigure the info in the key simply reloads the existing data. (equeals-your screwed)
However if "study up" on it, you can find where you delete the "cureent control set services tcipip" info and get fresh network service install.
As usual Bill Gates disavows any of the above info having anything to do with the realtiy of the "windows xperience"......good luck!
12-28-2002, 01:46 AM
i'm going to try to find some more info on that "msbatch.inf" file. but for the meantime i guess i'll try updating the BIOS (which i doubt will help) and most likely do a reinstall. the problem is that i have about twenty other machines setup the same way as this one sitting on a shelf. i would imagine that they were all setup using the same windows cd if not cloned. i guess i have some work cut out for me.
i'm still open for suggestions, but thanks to those who have replied.
12-28-2002, 11:39 AM
The batch tool is is the Win98 resource kit. I've used it.
Powered by vBulletin® Version 4.2.2 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.