• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Tablet PC having trouble connecting to network

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

LoneWolf121188

Member
Joined
Dec 31, 2004
Location
Osan AB, South Korea
I have an Asus Eee Slate EP-121 running Win 7 x64 and it has issues connecting to wireless networks. When I click on a network, it will usually just sit there and think for a while...then it says "Connecting to the network is taking longer than usual..." and will finally get it after about 5 minutes. The weird part is this is on my university's network. They have a very robust system; they've put millions of dollars into their IP infrastructure (I routinely get 16-20+ Mbps synchronous transfer rates), so there's no way the problem is on their side. I'm using the Intel 6230 Centrino-N chip with the latest drivers. Any idea what might be going on?
 
Fast transfer rates doesn't mean they don't have an overworked server handling DHCP and probably numerous other tasks, which could explain the delay. Especially if there's a few networking layers to the onion, it could cause requests to be handed off for a bit until something finally accepts, forwards, and performs the needed task (in this case giving you an IP address). Have you tested their wifi with another wireless device? If say your smartphone connects immediately then it could be something else (likely) laptop related and what I just posted is more a FYI.

I've seen plenty of 'high-end' installs that ran horribly. :p
 
^^ What would I change between home and school though? Settings are the same, the only thing that changes is the network SSID.

Fast transfer rates doesn't mean they don't have an overworked server handling DHCP and probably numerous other tasks, which could explain the delay. Especially if there's a few networking layers to the onion, it could cause requests to be handed off for a bit until something finally accepts, forwards, and performs the needed task (in this case giving you an IP address). Have you tested their wifi with another wireless device? If say your smartphone connects immediately then it could be something else (likely) laptop related and what I just posted is more a FYI.

I've seen plenty of 'high-end' installs that ran horribly. :p
I've never had issues with my smartphone or laptop, only the tablet. I've also never heard of anyone else complaining about how long it takes to connect. Pretty sure it's just my tablet...
 
SSID being a wireless profile (to netsetman) which is the whole point. 5 minutes is way too long and though I've never used it, activating a different profile, whether it be a lan or a wireless one, changes your network adapter on the fly. Similar to updating your mac or doing ipconfig (/release/renew). I like it simply because you tell the pc how to connect, not the other way round.


NSM I ran in wine and my only wifi dongle refuses atm to run in linux. It's a desktop & the dongle's are cheap. nb
 
Last edited:
Doesn't seem to do much... here's the output when I switch from my home profile to my school profile:
Code:
[0:00] Start: Red Rover (10:05:07)

[0:00] Start: Wireless Network Connection
[0:00] Adapter found
[0:00] WiFi: Start
[0:02] Connect: RedRover
[0:04] WiFi (RedRover): OK
[0:04] WiFi: Finish
[0:04] IP & Gateway: Start
[0:05] DHCP is already enabled on this interface.
[0:05] DHCP is already enabled on this interface.
[0:05] IP (DHCP-NS): OK
[0:06] Gateway: OK
[0:06] DNS: Start
[0:06] DNS: Error 84
Cable not connected or no connection possible

[0:06] Finish (10:05:14)
This is while sitting 50 ft from the closest AP.
 
Not much you can do on the server/router side. I'd change the mac too just to see what happens. But really, I'd talk to the IT dept and see what they say, if possible. You could request a static ip from them if dhcp does not work well.
 
Back