169.254.x.x issue connecting laptop with BT Homehub

ps3ud0

ps3ud0

ps3ud0

Caporegime
Joined
27 Sep 2004
Posts
27,676
Location
Luton ;)
Hi Guys,

Kinda got a problem that Im slowly trying to fix but thought best to ask advice if anyone else has gone through it.

My sisters renting and has got access to the internet via BT and connects to the old type BT Homehub. As shes house-sharing theres a limited number of things I can do with the Homehub without disrupting their conenction (i.e. I cant setup the router to not be the DHCP server)

For some reason my sisters laptop (Dell Inspirion with inbuilt Intel WIFI but can only connect to the BT Homehub with a Linksys PC card I bought) is being given a 169.254.x.x IP address and therefore can not connect to the net, even though it was before.

The main changes that I think have caused this is attempting to move from WEP to WPA2, but as her flatmates werent happy with the apparent hassle my sister was forced to put it back to WEP. She had got her laptop working with WPA2 but as soon as it went to WEP shes now getting the whole private network IP address...

As I cant get down there, Ive already got her to try the following:

  • Rebooted Homehub after switching it off for a few minutes
  • Tried to release and renew the DHCP IP license but on renewing it advises that it has no contact to the DHCP server.
  • Removed the Linksys card from device manager and re-installed it via Add Hardware Wizard in an attempt to re-establish a default connection
  • Connected it via LAN and copied IP/DNS settings for the WIFI after disconnecting it from LAN, so its manually configured rather than using DHCP
Everytime Ive got it hooked to the Homehub the linksys software advises it connected to the 'network' but not outside of that so has limited connectivity and I get given another 169.254.x.x. IP address. Its got to be a DHCP issue, but I assume the other flatmates are having no trouble...

The only thing I think I havent done is to rebuild winsock, but I open to suggestions :D. I know the whole 169.254.x.x issue is a nightmare so appreciate any step by step advice so at least I can assist her over the phone. Shes already spoken to BT in the first instance and as usual were useless. As far as I understand the problem it very unlikely to be a PC issue but more a DHCP server issue...

Im loathed to even consider a windows rebuild as I only did that 6 weeks ago when I hit upon the BT Homehub Intel 2200 WIFI B/G issue :/

TIA

ps3ud0 :cool:
 
Last edited:
ps3ud0 said:
Hi Guys,


The main changes that I think have caused this is attempting to move from WEP to WPA2, but as her flatmates werent happy with the apparent hassle my sister was forced to put it back to WEP. She had got her laptop working with WPA2 but as soon as it went to WEP shes now getting the whole private network IP address...
Click to expand...

Sounds like the laptop is not connecting to the Wireless correctly to gain an address. What is the HomeHub Wireless Security currently set to? WEP or WPA?
From what you say it sounds as if the Home Hub is set to WPA2 but your Sisters laptop is WEP?

Rob
 
Hi Rob7865,

Unfortunately I think the security settings seemed to have produced this issue. Originally the Homehub was setup on WEP and my sister could connect to it via the Linksys WIFI PC card.

As shes aware how rubbish WEP is she thought she would call BT and get access to the router so she could change it to WPA2, which she did and got her laptop working with that easily (rediscover network and reconnect with new passphrase with WPA2), but one of her flatmates had some issue and it was decided to regress back to WEP.

Once they had done this (without any Homehub reboot it seems - BT never asked them to do it) my sisters laptop stopped working and started receiving the 169.254.x.x issue above...

I assume shes putting in the right passocde as shes the one that dealt with BT. Though I may ask her to go into the Homehub and re-type it in in case. Ill also go through manually connecting the laptop to the Homehub rather than using the Linksys wizard in case as you said its still trying to connect via WPA2 and not WEP..

ps3ud0 :cool:
 
Last edited:
Im pretty sure as part of connecting the Linksys driver asks for the security setting and the passphrase/hexcode. I left the Linksys driver to manage it as it seemed to be a bit more user-friendly than Windows (has a nice visual indicator of the connection chain).

Am double checking the manual to make sure the above is a default request...

EDIT: Yep either via a profile or searching for the network you get the option to choose the wireless security - as above Ill double check these points again with her when she can tonight...


ps3ud0 :cool:
 
Last edited:
Exactly which Homehub is it, I've had a few of them. Some you can have 2 types of encryption on, some you have to press a button to associate, some don't like 2 things done to them w/out rebooting them or they sulk.................
 
Erm how do I tell?!?

Soz never had one so dont know - just that its not the one on the adverts (its white with a blanking plate you have to take off every time you attempt to connect to it via a wire)...

BTW guys my sister came home this weekend and I got her laptop working with my net connection within 5mins (linksys router on VM cable). All I did was ensure there were no settings behind the automatic IP address (gateway was still pointing to something). Considering doing the winsock fix but if her laptop can connect to my network and internet, I cant see why I need to do anything with anything but the Homehub.

BT does really suck - Ive never had it but its been a nightmare to setup when she moved in and Im amaxed how poorly setup it is for security...

ps3ud0 :cool:
 
Last edited:
It sounds like the "registration" button isn't being pressed or you aren't "looking for wireless devices" when trying to logon to the hub after altering settings & the PC is assigning itself that I.P. as the hub won't assign it one.
 
just an FYI

its not being assigned a 169.x.x.x IP address. Thats what it reports when its set for DHCP when it doesnt find one

If its reporting 169.x. IP , chances are (as explained above) its not been authenticated onto the wireless network so cant get an IP.
 
quackers said:
Out of interest, if she connect's via a cable to the homehub does she get the correct ip address and net accesS?
Click to expand...
Pretty sure shes able to connect normally when shes wired and able to access the net...

Nick644622 said:
It sounds like the "registration" button isn't being pressed or you aren't "looking for wireless devices" when trying to logon to the hub after altering settings & the PC is assigning itself that I.P. as the hub won't assign it one.
Click to expand...
Not sure what you mean by the registration button, but shes definitely looking for wireless access and connecting to the Homehub through that rather than letting it automatically connect...

ps3ud0 :cool:
 
Last edited:
Most of the HomeHubs have a button that has to be pressed to allow a new device onto the network, they call it registration mode. Some can be put into the "registration mode" by the HomeHub s/ware using a browser. No button press = it won't connect unless it has already been registered before. A hub reset will require all wireless devices to be re- registered. When it is in "registration mode" you get a flashing pattern of LEDs for the duration, just a few minutes normally.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom