IP 169.254 DHCP server unavailable Windows XP
Thread Starter
Join Date: Nov 2008
Location: Chicago
Posts: 1
Likes: 0
Received 0 Likes
on
0 Posts
IP 169.254 DHCP server unavailable Windows XP
First off, excuse my ignorance of computer technology. The limited amount of things that I do know about this current situation is from what I've heard from my ISP and from reading a bunch of forums. Currently I live in an apartment complex that offers wireless internet for the whole complex. I was receiving high latency issues because of interferance from other 64 Ghz bandwith things like cordless phones. As a fix for the high latency my ISP has provided me with a TUT modem and ethernet connection for my computer. Right now I'm connected to the wireless signal still, because when I set everything up I was receiving "Limited to No Connectivity" messages. From reading forums etc. I have found several "fixes" none of which has worked- Including power cycling my modem. Currently my IP is a windows generated 169.254.x.x because it is saying my DHCP server is unavailable (whatever that is lol) I've tried opening the command dialog box and using the commands ipconfig /reset and /renew to no avail. There was also some kind of nepsh command that I had used to try and uninstall and reinstall TCP/IP something or other...anyone know of any other possible fixes for this situation?
Spoon PPRuNerist & Mad Inistrator
Surely it is up to your ISP to fix?
If they have provided you with a modem and a wired connection, they should have configured it for you, no?
Perhaps the problem is that the WiFi Access Point (WAP) was functioning as the DHCP server, and your new modem isn't.
Maybe you could get around this by assigning a fixed IP address, subnet mask, default gateway and DNS servers, but you should not do this without receiving an approved IP address from the network administrator.
SD
If they have provided you with a modem and a wired connection, they should have configured it for you, no?
Perhaps the problem is that the WiFi Access Point (WAP) was functioning as the DHCP server, and your new modem isn't.
Maybe you could get around this by assigning a fixed IP address, subnet mask, default gateway and DNS servers, but you should not do this without receiving an approved IP address from the network administrator.
SD
Official PPRuNe Chaplain
Join Date: Apr 2001
Location: Witnesham, Suffolk
Age: 80
Posts: 3,498
Likes: 0
Received 0 Likes
on
0 Posts
As SD said.
169.254 means your PC can't see a DHCP server, or has been told not to talk to one.
I don't know what a TUT modem is - is that a router connected (without wireless) to the hub, or is it a separate ADSL modem with your own private connection?
If you have a wired ADSL into your home, then you may need to configure your PC to work with it. It's usually very straightforward, if not automatic. But then...
169.254 means your PC can't see a DHCP server, or has been told not to talk to one.
I don't know what a TUT modem is - is that a router connected (without wireless) to the hub, or is it a separate ADSL modem with your own private connection?
If you have a wired ADSL into your home, then you may need to configure your PC to work with it. It's usually very straightforward, if not automatic. But then...
The 169.254.xx.xx addresses are what Windows falls back to when it's been told to get its IP address from another machine (the one acting as a DHCP server), but couldn't. The basic link is up (or else it wouldn't even try), but I have seen that happen when wireless security parameters were set incorrectly. I suggest you double-check those against any settings you made or were given.
Like the others who replied, I don't know what a "TUT Modem" is. Is there a model name/number on it? I think TUT means it's made by Texas Instruments, but that doesn't tell us what its role is in your setup, whether it is supposed to act as a DHCP server.
Like the others who replied, I don't know what a "TUT Modem" is. Is there a model name/number on it? I think TUT means it's made by Texas Instruments, but that doesn't tell us what its role is in your setup, whether it is supposed to act as a DHCP server.
