General discussion

  • Creator
    Topic
  • #2132136

    TCP/IP no longer bound to NIC – bind?

    Locked

    by wessir ·

    I’ve done this to 2 PC by accident somehow…
    In device manager, In Network applet the arrows pointing from TCP/IP to the bound adapter are gone. Normally you would see:
    TCP/IP => Linksys Ethernet NIC
    but now only see
    TCP/IP
    I can ping the NICand it responds.
    It gets an IP from the DHCP server when booting.
    But it gets no response when pinging the DHCP server which it directly connected to. No WWW.
    What happened to break it and how do I fix it so the arrow comes back??? All my points to the guru who knows what this is.

All Comments

  • Author
    Replies
    • #3649471

      TCP/IP no longer bound to NIC – bind?

      by ann777 ·

      In reply to TCP/IP no longer bound to NIC – bind?

      Normally, TCP/IP –> Linksys or whatever adapter only appears when you have two or more tcp/ip protocols installed. For instance, if the computer had a modem and you removed it and thereby took away the tcp/ip protocol for the modems, then the only thing you will see is tcp/ip (it’s assumed to be for the network card).

      Sometimes you need not do anything specifi, the tcp/ip adapters just get corrupted due to improper shutdowns or whatever.

      I’d recommend that you remove the protocols andnetwork adapters from the computer and reinstall them. But realize that if the only tcp/ip protocol you are using is with the network card, then you should not see the “linksys” part of the protocol. The adapter is only identified if you have another adapter using TCP/ip.

      • #3649465

        TCP/IP no longer bound to NIC – bind?

        by wessir ·

        In reply to TCP/IP no longer bound to NIC – bind?

        That would explain the arrows but not the connection problem (which is the real problem). I have removed and reinstalled the NIC device and drivers but still have the connectivity problem.

    • #3431778

      TCP/IP no longer bound to NIC – bind?

      by timthetoolman ·

      In reply to TCP/IP no longer bound to NIC – bind?

      Hi,

      Anna’s answer was a good one as to why your properties page appears different now. You didn’t mention in your response to her whether you had in fact removed another nic or possibly a modem recently?

      There are a few possibilities for problems.
      If you haven’t removed another nic or modem, then you may have had another set of drivers in place and they’ve been removed somehow. Its possible that the drivers you’re using right now are not the right ones… Double check that and download the latest ones from the manufacturer’s website.

      Just because you have an IP address post boot, doesn’t necessarily mean that its actually been allocated to you. Windows caches the last address and continues to use it if it doesn’t get a reply fromthe DHCP request.

      Can you ping the machine’s nic from another machine?

      Do the lights come on on the nic? – one permanent and one flashing when you access the network?

      Its not entirely impossible that your nic is broken, too. Try another one.

      Cheers,
      Tim.

      • #3654093

        TCP/IP no longer bound to NIC – bind?

        by shanghai sam ·

        In reply to TCP/IP no longer bound to NIC – bind?

        Thanks for your answer. Knowing windows caches the last IP address helped me a bit – thanks! I can now say the DHCP server (a router) is working fine. The NIC gets a new IP from it but yet I can’t ping the router. Other PCs on the network can ping the router and each other but none can communicate with the broken PC. WinXP installed its own driver for the NIC and says it is working properly – but it may not be. 2 solid lights on the NIC and Router(for that PC).

    • #3431610

      TCP/IP no longer bound to NIC – bind?

      by dcosgrove ·

      In reply to TCP/IP no longer bound to NIC – bind?

      Where are you pinging the nic from? If you get all your packets back without significant loss you are getting bi-directional communication. It is possible that your tcp-ip stacks are corrupt and answer 1 may be your solution. Just remember to reboot after you remove tcp-ip ignoring the “you network is incomplete” message and when you reinstall, try to use files from the CD if possible. I also just noticed you say it is “directly connected to the DHCP server”, is this via X-over cable? Is DHCP running from a router? if it is a X-over cable make sure the wiring is correct. One side should be OW/O/WG/B/WB/G/WBr/Br and the other should be WG/G/WO/B/WB/O/WBr/Br. Good luck.

      • #3654094

        TCP/IP no longer bound to NIC – bind?

        by shanghai sam ·

        In reply to TCP/IP no longer bound to NIC – bind?

        Thanks for your answer. No X-over cable involved. DHCP from a router. The NIC is accepting new IP addresses from the DHCP router. Everything seems to be working but no communication from the bad PC outside of pinging itself.

    • #3429958

      TCP/IP no longer bound to NIC – bind?

      by adizatou ·

      In reply to TCP/IP no longer bound to NIC – bind?

      One other thing you may want to try is to run the “winipcfg” command in a dos prompt and make sure your adapter is selected. Once selected, click on release and then renew. If it pulls an IP you should be fine. In Win NT4 and 2000, the command wouldbe “ipconfig /release” and then “ipconfig/renew”. One other thing you can also do is blow out(delete/reinstall) your winsock2. You’ll have to go into your registry, HKEY LOCAL MACHINE and find it. Do a search. Also go into control panel, Add/RemovePrograms remove dial up networking, restart your computer and go back into it and readd it. This will rebuild winsock2. Hope these suggestions help. Let me know at richardmace@yahoo.com.

      • #3654095

        TCP/IP no longer bound to NIC – bind?

        by shanghai sam ·

        In reply to TCP/IP no longer bound to NIC – bind?

        Tried release and renew, pinging…The only clue I get from ipconfig /all is it says Unknown in the Node Type. All other PCs on my network say ‘Broadcast’. I’m using a signed XP driver for a Linksys LNE100TX v4 ‘an983.sys’ and I physically checkedthe card for the version. I have used this card in a WIN98 PC as well as the first NIC card I was using (which has the same problem as current proplem). What does the winsock2 suggestion do? I will try it tonight.

    • #3654355

      TCP/IP no longer bound to NIC – bind?

      by ann777 ·

      In reply to TCP/IP no longer bound to NIC – bind?

      Okay, we’ll ignor the arrows right now.

      You have nics in these two computers, both obtain an ip address from the dhcp server, but neither can ping that same server? What OS are you using?

      I’d suggest that you boot to safe mode and take a lookat device manager. Sometimes the drivers and multiple instances of adapters or “other devices” get into device manager and a re-install just adds to the inconsistencies. If you see multiple anything, or anything with a yellow question mark, exclamation point, or a red x, then remove them in safe mode. Shutdown and power back on & go to normal mode. See if the computer re-detects these cards and accepts the install and you should be fine from there.

      Also verify that these two computers are setup properly, no manual ip address conflicting with the dhcp server, subnet mask, gateway, and make sure that dns or wins is active for your internet connectivity on these two computers.

      • #3653654

        TCP/IP no longer bound to NIC – bind?

        by shanghai sam ·

        In reply to TCP/IP no longer bound to NIC – bind?

        All good comments, thanks… WinXP, only the XP doesn’t work. I have 3 other PCs that do work with the router/dhcp server. No IP conflicts, subnet all the same, gateway all the same, …

    • #3435753

      TCP/IP no longer bound to NIC – bind?

      by rightondudenospam! ·

      In reply to TCP/IP no longer bound to NIC – bind?

      Do you have any “other” devices listed with a question mark in device manager especially network adatpers? Remove these and reinstall the card.

      Depending on how well you know TCP/IP it might be worthwhile to record your IP settings beforehand.
      Sounds like the info bound to that card in the registry is munched. Remove the card in device manager, shut down then remove the card physically. Boot back up poke around the network settings to make sure you have none, then shut er down.

      Drop the card in another slot and reinstall the card when prompted. Your TCP/IP stack got toasted in windows. Also make sure you’re using the right drivers.

      Sounds drastic? Well…not really, it works 99.99% of the time.

      • #3653381

        TCP/IP no longer bound to NIC – bind?

        by wessir ·

        In reply to TCP/IP no longer bound to NIC – bind?

        This is a solid suggestion, one that I have already tried. I believe the registry settings are screwed up but that procedure did not repair them. Answer #4 may be on the right track but if I delete those keys – how do I rebuild them in XP?

    • #3435489

      TCP/IP no longer bound to NIC – bind?

      by timthetoolman ·

      In reply to TCP/IP no longer bound to NIC – bind?

      Hi,

      Two solid lights on the nic? That doesn’t sound good.

      Try another one.

      Cheers,
      Tim.

      • #3653382

        TCP/IP no longer bound to NIC – bind?

        by wessir ·

        In reply to TCP/IP no longer bound to NIC – bind?

        I’m on my 2nd NIC, but am considering buying another that is listed in the XP compatability list.

    • #3653741

      TCP/IP no longer bound to NIC – bind?

      by hypersoniq mcse ·

      In reply to TCP/IP no longer bound to NIC – bind?

      Don’t overlook the easy answers…

      1. Try a new cable, a usual suspect.
      2. Try a different port on the Router, they go bad too.
      3. Check the scope of IP addresses that the DHCP server is handing out, make sure it has enough and that the one being recieved by the problem NIC isn’t somehow blocked out or restricted.
      4. Try the NIC in a different PCI slot… a PXE-compliant nic will still recieve an IP addy even if a pci slot problem prevents full interaction between the NIC and the PC it’s installed into. If another PC works fine when fitted with the same NIC in the same location attached to the same physical connection on the router, then maybe the motherboard needs to be replaced.
      5. Check the routing tables for any irregular entries associated with the IPs being given out.
      6. Look for any clues in the Event Logs of the problem PCs.

      of course, if the registry was heavily edited, even re-installing the protocol won’t help. Try restoring system state data from an older backupof the PCs, or worst case, back up user data, wipe the drives, and go for a clean install of the OSes.

      • #3655107

        TCP/IP no longer bound to NIC – bind?

        by wessir ·

        In reply to TCP/IP no longer bound to NIC – bind?

        Thanks for your answer. I struggled with this for a week and finally went out to Best Buy and picked up an XP certified NIC and it works now! XP doesn’t play with a lot of hardware.

    • #3653740

      TCP/IP no longer bound to NIC – bind?

      by hypersoniq mcse ·

      In reply to TCP/IP no longer bound to NIC – bind?

      Don’t overlook the easy answers…

      1. Try a new cable, a usual suspect.
      2. Try a different port on the Router, they go bad too.
      3. Check the scope of IP addresses that the DHCP server is handing out, make sure it has enough and that the one being recieved by the problem NIC isn’t somehow blocked out or restricted.
      4. Try the NIC in a different PCI slot… a PXE-compliant nic will still recieve an IP addy even if a pci slot problem prevents full interaction between the NIC and the PC it’s installed into. If another PC works fine when fitted with the same NIC in the same location attached to the same physical connection on the router, then maybe the motherboard needs to be replaced.
      5. Check the routing tables for any irregular entries associated with the IPs being given out.
      6. Look for any clues in the Event Logs of the problem PCs.

      of course, if the registry was heavily edited, even re-installing the protocol won’t help. Try restoring system state data from an older backupof the PCs, or worst case, back up user data, wipe the drives, and go for a clean install of the OSes.

      • #3653678

        TCP/IP no longer bound to NIC – bind?

        by wessir ·

        In reply to TCP/IP no longer bound to NIC – bind?

        Everybody who answered my question obviously is familiar with network troubleshooting and anna came closest to answering my initial question. How do I give you the points? Do you know why XP drops the connection after a few hours of inactivity? Ipconfig /renew gets it back without rebooting but still….

    • #3642838

      TCP/IP no longer bound to NIC – bind?

      by daz’n’ash ·

      In reply to TCP/IP no longer bound to NIC – bind?

      Glad you got your troubles fixed. To give Anna the points, you can just post another question and entitle it for Anna, set the point value and then it is up to Anna to accept the points, close the question and award the points.

    • #3640184

      TCP/IP no longer bound to NIC – bind?

      by wessir ·

      In reply to TCP/IP no longer bound to NIC – bind?

      This question was closed by the author

Viewing 10 reply threads