56 replies to this topic

[IRJ]

I have been discussing this under this thread below however the title isn't relevant to the meat of the discussion and we may miss posting by others with similar issues.
http://forum.eeeuser...pic.php?id=9284

In short I can communicate with ANY OPEN WiFi almost instantaneously.

I use WEP encryption on my Linksys WRT54GX (latest firmware 1.02.15.05)

I go thru set up and starting and then get stuck into a PENDING loop which never finishes with a connection. I have reset back to original settings, I have wiped out prior efforts. Done all the good things

I am interested in collating information from others with similar problems and hopefully eventually sharing solutions.

After many conversations with Asus they are now discussing internally and have asked for 2 days grace period. Hopefully this means they are taking me very seriously.
Well they just called me back to ask a question so that's good.
Perhaps somebody can help me here. The question asked: Was I having a problem with any other Wifi WEP encryped router? Ooops the word "incompatibility" is creeping in here. I said no as I own only one router (though I did get kicked out of a neighbor's netgear router).
So are others having similar WEP issues using routers other than Linksys??????

I need to squash this easy out incompatibility answer. WEP is a standard and should not vary by router.

Edited by IRJ, 16 January 2008 - 09:51 PM.

[raeveth]

Hi, I have not been able to connect. EEE arrived this morning at 09.15, won't connect to my network on WEP, WPA, WPA2 or unsecured either. I tried putting the key in caps and non-caps, tried changing the channel to all, tried the 1,2,3,4 key thing - all to no avail.

I'm using a Buffalo WBR-G54, but I've changed the firmware to dd-wrt instead of whatever the Buffalo one used to be, seeing as there's so many people with this problem I can pretty surely say it's not my router's fault.

[singraham]

I can connect to non-encrypted, open wifi networks, generally without problems. On encrypted networks it sees the network and tries to connect but it gives the no DHCPoffers message after 4 or 5 tries to find one, switches to looking for a previous lease, does not find one, and hangs at pending forever after.

I have the encryption key for the network I am trying access. It has no spaces, dashes, punctuation, etc. Just numbers and letters. I have tried both connecting through Wireless Networks and through Create Connection, entering the key where prompted...but it still hangs at pending.

This is my office router and I have no access to it to reset it, etc. I don't even know what make or model it is...but from reading these threads, it does not seem to matter. This appears to be a flaw in the DCHP and encryption code, perhaps in the wifi drivers themselves.

IMHO

[Jon Bradbury]

Safecom SWBR-5400 router (which is a really old one), WEP enabled, the eee connects usually on bootup, but if not will always succeed when manually asked to connect.

I agree with you - WEP is a standard, as is 802.11b/g, so the eee should work with them.

[IRJ]

Ok had some conversations with tech support and I have got my eee working on my WEP enabled network!

Now we made only ONE change to the usual procedure of setting up the eee for wireless.
In the box WIRELES SETTINGS there are TWO boxes which are pre set to AUTO.

Change the MODE box to INFRASTRUCTURE from AUTO. REPEAT INFRASTRUCTURE.

Seems the eee does NOT like the standard Auto setting.

My goodness you would think tjhat such a small change would be all over the Internet.

Please someone else with the same issue make that change and let us know if it works for them:)

Edited by IRJ, 18 January 2008 - 05:22 PM.

[velobob]

I just got my new EEEPC an hour ago and have been struggling with the "Pending" connection. Thanks for your post - it worked for me!

[kaiserpc]

got my eeepc today, changing this setting worked for me too! :-) (netgear dg5834 and WEP)

[IRJ]

Glad to help guys:)

[vegassam]

Netgear WGT624 wireless had same problems. They went away once I stopped using DHCP & hard wired my IP address.

Using the suggestion above, I changed the mode to INFRASTRUCTURE and went back to DHCP. Everything worked great so I made the changes permanent.

Then today, I went to another room in my house & restarted the eeePC. It found another network. Even though I have my NETGEAR as the connect on boot configuration, it tried to connect to mt neighbor's unencrypted AP.

IMPORTANT.... in trying to force the eeePC to connect to my AP, it asked for my WEP key. I reentered it (but incorrectly)... I wound up with messeges that said ENABLED but I could not surf. Looking at my eeePC, there was NO way to tell that my log in had been rejected.

PS - the NETGEAR showed my MAC address as connected but w/o any ID.... obviously, any mis typing of the WEP key means you wind up in the pending loop....

Edited by vegassam, 21 January 2008 - 05:44 AM.

[IRJ]

I initiated the Skype program and was told there was an updated software to DL. This automatically rebooted my eeepc (didn't give me an out). Upon restart the Wifi connection failed in pending again. I cancelled the wireless networking settings and went thru the entire setup and everything works again.

I think that we need to start an "Essential Bug Fix" thread for Asus to take note off. This wireless connection should not be this sensitive.

Also the touchpad issue is som,ewhat annoying and needs fixing once and for all. Both look to be software tweaks. Casual usrs will not be bothered to keeptheir eepc while annoyances abound IMHO. As Asus is selling hundreds of thousands per month they need to make these fixes avalaible ASAP IMHO.

[debben]

I am also a new EEE PC user, having received my 4G a few days ago, and I ALSO cannot connect my EEE PC to my Linksys WRT54G secured wireless network. Mine is encrypted with WPA. I've tried changing the wireless setting to "infrastructure" as menioned in other posts here, but no matter what I've tried, the EEE hangs with the connection "pending"......
Don't know what else to try, except maybe just install Windows XP....

[agni]

I've got the WRT54GL, using it as an AP only with my wired router giving out DHCP.
Using default firmware and WPA2-PSK.
No problem here connecting but I use the replacement madwifi drivers and wpa_supplicant instead of the default eeepc ones (due to WPA2-PEAP at work).

[debben]

From reading these posts and trying to connect my new EEE PC UNSUCCESSFULLY to my WPA secured wireless network, it looks to me like I could waste yet another whole weekend just trying to make my EEE work.
Spending hours online looking for an answer and playing with all kinds of arcane settings and drivers is not what I call "easy". Maybe I should simiply change my wireless network back to "unsecured" - a nice step backwards.
I find it hard to believe that ASUS was not aware of such a flaw in their EEE PC, but failed to disclose that "little" tidbit to us buyers.

[almoore]

I use a BT Homehub which has a WEP key and all I had to do was enter the key once and it connected and maintained the connection until I shut down about 2 hours later

[gtm]

Quote

Now we made only ONE change to the usual procedure of setting up the eee for wireless.
In the box WIRELES SETTINGS there are TWO boxes which are pre set to AUTO.

Change the MODE box to INFRASTRUCTURE from AUTO. REPEAT INFRASTRUCTURE.

Seems the eee does NOT like the standard Auto setting.

My goodness you would think tjhat such a small change would be all over the Internet.

Please someone else with the same issue make that change and let us know if it works for them:)

I connected to a Netgear wireless router using WPA with no problems except that every time I logged in it asked for the password again! This change has sorted it - glad I found it as the rest of the net seemed to be recommending installing WiCD (which probably works - but this change is muuuch easier). Thanks

[debben]

I have the same issue (wireless connection stuck on "pending"), and I made that setting change to "infrastructure", but I still can't connect.

Very disappointed that my "easy" little computer can't do such a simple thing correctly. I've wasted too much of my life fiddling with arcane computer crap, and I vowed that I am not going to waste much more time on this...

[IRJ]

Would somebody start a petition to Asus asking them to make a proper fix for this? (and the touch pad sensitivity issue).

[Vernon]

It should detect a network is of the infrastructure type and use that setting, but if it doesn't changing it manually would be a good idea. (You can find out the network type by looking at the network "details" in the visible access points dialogue box)

I found the touch pad sensitivty issue could be largely solved by turning it down one or two notches under the settings tab.

Edited by Vernon, 20 January 2008 - 06:42 PM.

[mag12000x]

My WIFI is resolved...
This string as well as the one at ASUS regarding this issue were both interesting. However I refused to accept having to make any changes to my router since I have two laptops and a DS Lite running off a WEP encrypted wireless (WEP because of the DS's limitations). Therefore I started in with the Wireless atheros card, figuring this thing has got to work, it got to be one of its property settings. With MODE set to "AUTO"(DEFAULT), not "INFRASTRUCTURE". I went into Network Connections selected Properties or the Wireless and under "Sharing" and selected "Shared" and OK.
The WEP key and channel were already set so the "MINI" restarted the connection and picked up the router immediately. Now on the road i'll be able to connect to ADHOC and INFRASTUCTURE wireless. Always Use a Firewall.

Hope this helps someone, Cheers!!

ASUS 701 4G (2G CorsairRam) Xandros Advanced Mode Desktop Galaxy Black S/N:7C

Edited by mag12000x, 28 January 2008 - 04:03 AM.

[rosetown]

Quote

I initiated the Skype program and was told there was an updated software to DL. This automatically rebooted my eeepc (didn't give me an out). Upon restart the Wifi connection failed in pending again. I cancelled the wireless networking settings and went thru the entire setup and everything works again.

As a precaution,in Skype>options>advanced - I unchecked the box "Check for updates on startup". I didn't know where this update would come from although I presumed it would come from Skype. Since the version of Skype that I'm using is specifically written for the Eee I didn't want any automatic download, especially if they might come directly from Skype. Whereas the version of Skype that I'm running came from here:
http://update.eeepc....eepc-2_i386.deb

Regards Duane