Hub not assigning IP adress
CB
Ƹ̵̡Ӝ̵̨̄ƷDer Millionendorf- Icrontian
We're trying to hook another PC into the network, and it keeps telling us that the hub is not sending it an IP. When we look at the hub config, it is only detecting our computers. It's not the cable. And the same computer was working on a different hub earlier today. In fact, this hub was sending IP addys to two other computers earlier today too. Does this issue sound familiar to anyone?
0
Comments
I have mine configured to only allow .100 - .102 which covers the 3 PCs I have connected.
It's a long shot, but....
also try another port on the router, if you can/haven't yet.
What happens when you hook the computer directly to your cable/dsl connection?
The strange thing is that on Thursday before we set up for the mini-LAN, the PC had an IP just fine (with the same router) on the same exact network in the same exact configuration. All weekend during the LAN, the PC had an IP assigned by the router, and they both recognized it and we were on the web with the PC and playing LAN games with it. As soon as we moved it back to the entertainment center and reconnected it, it stopped acknowledging that it had a connection.
Here's the history of the problem:
We reconnected the PC on the network last night at about 10:00. Booting the PC, it didn't appear to have any issues. I tried to browse the Network Neighborhood. It showed the other PCs for a split second, then the PC with the red "X" icon showed up in the system tray (cable unplugged message). We screwed around with it for a bit, and eventually got it to show that the cable was plugged in, but received the "Limited or no connectivity, could not obtain an IP" message. I searched the web for solutions. Most of the solutions dealt with either recent upgrades to XP SP2 (this PC has had and been working with SP2 all its life) or resetting the winsock/IP stack. I applied the hotfix for the 'recent upgrade to SP2' issues anyway, and did the stack resets. I also set the connection type from 'auto select' to '10Mbps Full Duplex' manually, as was suggested in one of the articles I found. No fix worked. By the end of the night, I was getting my router to acknowledge handing out an IP, but the PC would not acknowledge that it had been given an IP. I'm going to try Prof's suggestion tonight (though I'm not eager to stick another NIC in the PC, since it's in a mini-cube case that's a beeeyatch to work inside) but I'm open to other suggestions as well.
I tried resetting TCP/IP with the netsh int ip reset command, I tried a repair install, I tried updating to SP2 from SP1, I tried a different NIC... All no go.
I'm about to reinstall from scratch.
One other curious behavior. Try this and see what you get:
If I manually assign an IP, such as 192.168.0.155 and then try to ping our gateway (which is 192.168.0.1) I get the most bizarre result. It says "Pinging {BEEP}bÿ0¬ with 32 bytes of data..." As in, literally it beeps and then followed by junk characters. The weird part is, it does actually perform the ping. However, even with a static IP, DNS isn't working.
So weird.
I'll try what you say and see if I get the same weirdness.
Before you reinstall from scratch, try the netsh winsock reset command. It will then require a reboot afterward (nesh int ip reset didn't require a reboot for me). The winsock reset didn't work for me but it might save you a reinstall...
Maybe there's some new baddie out there that we don't know about yet....
If it was my computer (this one is GH's so it's not my call) I would be willing to wait a few days and scan it again before I start getting into some time consuming troubleshooting.
No reinstall for me!
Look in your networking setup. The GATEWAY and DHCP Host IP might be SET, in this case to a previous router's IP, so when hooked to new router with a different IP, Windows cannot find the GATEWAY\DHCP server. Essentially, Widnows, in order to flex gateways, need to be set like this:
For DHCP, do not specify a host (DHCP server IP) unless you HAVE to. IF you have to, and I have on occassion had to, make sure the mask and IP are verbatim to the LAN IP of the router. THEN, once it accepts that IP and gets DHCP, probably after a reboot with 98, Me, and 98 SE, CHANGE the settings to full automatic, both as to IP fetch by computer and as to the DHCP server auto-detect.
When 98 SE, ME, 98, sometimes 2000 fault, the TCP\IP stack can NOT get updated right (leaving you with default IP and mask, whihc might not BOTH match the router, and BOTH HAVE TO MATCH), and MAKE DANG sure that you are playing with the TCP\IP stack advanced setttings associated with your NIC, and not a modem associated TCP\IP stack. TCP\IP stack should point to NIC driver, ideally, or be the ONLY TCP\IP stack in networking config.
Folks keep forgetting the mask in client TCP\IP stack, or to reboot if networking is hung and box is not an XP box, adn even with XP, SP2's firewall can block DHCP SOMETIMES but by no means all times. Some older routers and the VPN updates also conflict, and some NIC drivers are not VPN capable even, with older Windows or older routers, and newer routers might need new drivers at NIC level with 2000 and back and unupdated drivers from 2-4 years ago.
I will almost bet, of the folks posted here, that most will find one or more of four things:
Computer somehow got set to fixed one time, never changed from that.
NIC drivers cannot VPN, but router CAN and does.
TCP\IP stack is corrupt due to settings conflicts.
Drivers are older than OS, or much older than router.
Other things that can come into play and create intermittents like this with no pure hardware fault other than lack of feature design-in due to age of component:
Me, 98, and 98 SE are NOT uPNP OSs in the modern sense. Plug-nPlay and uPNP ARE different. Routers mfr'd in time frame that 98, SE, adn ME came out might not be uPNP capable, or have uPNP turned OFF by default. So, there you might have problems with 2000 and\or XP not taking IPs right (2000 with all service packs to current is mostly capable for uPNP for networking, the stack fixes in XP Pro were ported BACK into the more recent TCP\IP updates for 2000, whiel earlier 2000 had problems with uPNP).
Having two or more NIC drivers, or partially installed driver and TCP\IP stack soft parts present, can also create a sometimes-on, sometimes NOT working, scenario. in 98 SE and 98 and Me, I have seen duplicates show in safe mode only, for drivers, and sometimes easiest thing is to start afresh with all networking, after finding right drivers and reading the README or install directions for the card. Safe mode, in 98, SE, and ME and sometimes 2000, can let you only delete drivers and device packs. Then, you have to force the4 computer to take drivers from the media you have the driver install set on, or run a program that installs drivers, then let the OS decide it needs its networking underlayment reloaded from install set (sometimes AFTER a restart).
That is a general scenario\possible cause parts set in idea form, for this thread....
Plugging the PC directly up to the DSL router gets the same "low connectivity" message.
None of my previously described fixes worked (including winsock reset).
When I manually set the IP, it says "connected" but I'm not actually connected.
If I had any confidence that a complete reinstall would do anything, I'd do that, because it would probably be quicker than putting in another NIC, based on the structure of this case.
As for the four scenarios John set forth, here are my results:
1.Computer somehow got set to fixed one time, never changed from that.
My PC was still set to automatically obtain.
2. NIC drivers cannot VPN, but router CAN and does.
I don't think the router is set for VPN - the other PCs aren't acting as such.
TCP\IP stack is corrupt due to settings conflicts.
I reset the TCP/IP stack, and it didn't work.
Drivers are older than OS, or much older than router.
Newest Via 4-in-1s.
Now my notebook is doing the same thing. It worked fine a few days ago with the exact same configuration it (and the Router) has today.
//edit: Update on the notebook: If I turn off WEP, the notebook will connect just fine. If I turn it back on, the notebook gets the "Limited or no Connectivity" error.
Any ideas?