Sorry to hear your problem is not solved. I have had a Google and found a similar problem to yours with no DHCP offer detected from a BT Homehub router, its a bit old though.

http://ubuntuforums.org/showthread.php?t=911350

Unfortunately there was no solution. I have never experienced an issue like this, but I have only ever used Netgear and Thomson Wireless routers with O2 broadband.

Have you tried a CAT5 cable into the netbook from the Router?

I will have a search around and post back if I find anything.

My first experience with Linux was Corel Linux about years ago, this was in the days when I had to configure a V90 dial up modem with it. It wasn't easy, but I never gave up on Linux!

I noticed you have ethernet port, does BT Broadband allow you to log into router?
I have a DLink router and I find it easier, to actually login to the router and accept the default key which is very long maybe 30 characters.
What I do is, do wireless setup, when it shows key I copy & paste it, to desktop folder, then press ok. Then I edit my wireless wireless network connection and paste key to it. If it changed network I have the key and I go to other machines & make the change since they're easier to alter.

Hi again, I've slept on it and taken a deep breath and I'm back to give it one last try before I give in and put it back on ebay!

I'm going to give it a go on the ethernet cable. In the meantime does anyone know what all the settings should be in the properties just so I can check I have everything set to the right places etc. As I left it last night i had put it to static ip and filled in the subnet mask and dns server boxes with the numbers off the homehub manager.

This has changed the status to 'enabled' instead of pending. Fingers crossed you're going to say thats a step in the right direction!

If you set your IP Address back to DHCP, that will remove any IP and Subnet mask values. The default gateway you should check is removed and any DNS settings.

Good luck with it. If it does work with an ethernet cable then it is certainly an issue with DHCP and your BT router.

Saying that thought it should have worked with a static IP Address.

I dont think Asus put Linux on their eeepcs anymore. I using an Asus eeepc 1005HA to type this, but it has a dual boot Windows / Slackware.

It works with the ethernet cable and the same settings, IP address, DNS etc! Just doesn't want to do the same thing wirelessly. I know I'm no computer whizz but surely using the same settings proves the settings I have put in are ok and it must be something to do with the wireless part of the darn thing! What is the difference between it saying pending and enabled?

I'VE ONLY BLOOMIN MANAGED TO FIX IT!!

I'll post here what I have done so anyone else stuck can see rather than trawling round google for a week. Feel a bit silly now because it sounds quite simple really.

I figured that the only difference between the cable and wireless was the password thing. All I have done is to change the encryption type. The homehub was on WPA and the netbook was on WEP so I have matched them both up and it now connects wirelessly!

If anyone can see any potential problems I might have created please let me know....

Good news, glad you got it! Enjoy your first steps into the world of Linux....

I think Linux Questions is great but... When I got my EEEPC 701 I joined the EEEPCUSER forums. Check here for one of the "pending" threads.

http://forum.eeeuser.com/viewtopic.php?id=8919

These guys may be able to help you out as their stuff is more specific to Asus EEEPCs.

But... Hurry back and don't be a stranger!

Play Bonny!

This has been a generic problem with EEEPCs and their weird Linux distro. I have two identical EEEpc 2G Surf units, and both get this problem intermittently. Right now, one is connected, and I've been trying to get the other one to connect for an hour. The one that won't connect worked fine until I rebooted the wireless router while it was connected.

And now, after about 10 tries, it's up.

It's only a problem with encrypted connections, incidentally.

Various EEEpc forums suggest deleting the connection information and re-entering it. Sometimes that works. Others suggest going in as root and releasing the DHCP leases. Some people claim that works. I've never seen a good solution. The manufacturer abandoned Linux and went entirely to Windows years ago, leaving the Linux machines unsupported.

They can't load a standard Linux distro; they're too small. They only have 2GB of flash as disk.

I use these little machines to run some demo hardware over a USB port, and I wish they'd stay up.