Asus Eee 1000H Eeebuntu 3.0.1 won't authenticate/connect wifi network
I have loaded my wife's Asus Eee 1000H with Eeebuntu 3.0.1 alongside WinXPsp3 after I had to replace the HDD, now a 320G SATA drive. The WinXP setup went well and outside the webcam and a few drivers works flawlessly. The Eeebuntu install went on without a hitch and it updated the distribution as well as the Add/Remove files list off a wired connection in my home network.
Trying to get wireless working is resulting in similar issues with my last attempt to get wireless working on the Live USB version I used for troubleshooting. My home and office WinXP machines have no issues with the network, working for 3 years now, and in XP the Asus connects fine, but not under Eeebuntu.
Network is ADSL 1.5Mb connected via Linksys Wireless Broadband B 2.4GHz router (BEFW11S4 ver4). SSID is not broadcast as I am currently in a condo. The encryption is set and a 64bit (10 digit key) is the only WEP1 key defined (preamble is the same), broadcasting on channel 3, everything else is default on the router. On the DHCP table I can see the wired and wireless connections on the Asus when in Linux and IPs are in my custom range, only thing odd is the host name is different, the wired one is the defined name from install and wireless is the generic PC name (Eee-1000H).
I try to connect to a hidden network, entered in the SSID name and WEP key in the 40/128 WEP section as there isn't a 64bit section and it just asks for the key 3 times and quits. I have WEP enabled for the PSP2000 device and my 4 year old Toshiba laptop. 64bit is a bit faster then 128 as the encryption encap is a lower overhead which works well in the condo due to the thick concrete walls. Is it possible to get Eeebuntu to connect via wireless or am I trying to force it to do something it can't support?
Are you using GNOME network manager or Wicd? Wicd v1.7.0 has documented problems connecting to some WiFi routers, but WPA2 passwords are usually the problem. I've seen it on my own machines running Ubuntu or Slackware. GNOME network manager doesn't have this problem, and I don't know if Wicd has been fixed.
|All times are GMT -5. The time now is 12:57 AM.|