AP mode not visible from Windows XP

   #1  

invisiblewave

Verified VCDS User
Verified
Joined
Feb 25, 2014
Messages
56
Reaction score
8
Location
USA
VCDS Serial number
C?ID=208767
In access point mode my HEX-NET isn't visible from my XP netbook. It works fine in infrastructure mode, and in AP mode it's visible from both my Android phone and my Linux desktop. With Windows, it just doesn't appear in the list of visible networks. I don't think it's a problem with the laptop, it sees numerous other networks including the two in my house and half a dozen belonging to neighbours. Just to be absolutely sure I ran a Windows Update to no avail.

Any solutions or troubleshooting pointers would be welcome.

The only other issue I have yet to overcome is a speed problem. Running in wireless infrastructure mode and monitoring both coolant sensors, the connection appeared to be extremely slow. I've only tried once (my HEX-NET only arrived yesterday), so it might be a problem with either the laptop or the network.
 
   #2  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
38,973
Reaction score
27,540
Location
USA
VCDS Serial number
HC100001
Is this the Acer Aspire One that you listed on your order? How old is it? Can you give us the exact model number please? What is it using for a WiFi chipset, and are the drivers for that WiFi chipset up-to-date?

-Uwe-
 
   #3  

invisiblewave

Verified VCDS User
Verified
Joined
Feb 25, 2014
Messages
56
Reaction score
8
Location
USA
VCDS Serial number
C?ID=208767
Yes, the Acer Aspire One. It's a D250-1389, manufacture date says 0907. The chipset is Atheros AR5007EG and the driver version was 7.6.1.244, dated 2/25/2009. I've just updated it to 7.7.0.348 to no avail (it also has a 2009 date, but is apparently the latest). The same laptop when booted into Ubuntu can see the HEX-NET.
 
   #5  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
38,973
Reaction score
27,540
Location
USA
VCDS Serial number
HC100001
Yep, if it works when booted into Ubuntu, it's clearly not a hardware issue with the laptop/WiFi itself.

-Uwe-
 
   #6  

invisiblewave

Verified VCDS User
Verified
Joined
Feb 25, 2014
Messages
56
Reaction score
8
Location
USA
VCDS Serial number
C?ID=208767
Ok, I updated to that driver and it still doesn't see the HEX-NET. The driver version is now 10.0.0.260 7/18/2013.
 
   #7  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
38,973
Reaction score
27,540
Location
USA
VCDS Serial number
HC100001
Scratching head...

-Uwe-
 
   #8  

Santos

Administrator
Staff member
Administrator
Joined
Jan 29, 2014
Messages
333
Reaction score
2,923
Location
Lansdale, PA, USA
I was able to dig up an old netbook equipped with an Atheros AR5007EG card. I'll experiment and get back to you shortly.
 
   #9  

Santos

Administrator
Staff member
Administrator
Joined
Jan 29, 2014
Messages
333
Reaction score
2,923
Location
Lansdale, PA, USA
I found a work around for direct wireless connect to the Atheros AR5007EG.

Create a profile in the HEX-NET for an AD-HOC network. The Atheros card can see the HEX-NET and allow you to connect. Its not as clean as AP-Mode, but should work for now. It sounds like a Windows driver issue.

0qDmXX8.png
 
   #10  

invisiblewave

Verified VCDS User
Verified
Joined
Feb 25, 2014
Messages
56
Reaction score
8
Location
USA
VCDS Serial number
C?ID=208767
So you couldn't get your laptop to connect in AP mode either?
 
   #11  

Santos

Administrator
Staff member
Administrator
Joined
Jan 29, 2014
Messages
333
Reaction score
2,923
Location
Lansdale, PA, USA
Correct. It appears the windows driver for the AR5007EG do not support "Access Point" mode networks.
 
   #12  

thismember

Verified VCDS User
Verified
Joined
Feb 26, 2014
Messages
7
Reaction score
0
Location
USA
VCDS Serial number
C?ID=208399
I am also unable to connect my XP laptop in AP mode. Network card is an Atheros AR928X. I tried the AD-HOC network profile and just updated to the latest driver (10.0.0.255 Release Date: 2013-07-02) yet HEX-NET is still not visible...
 
   #13  

Santos

Administrator
Staff member
Administrator
Joined
Jan 29, 2014
Messages
333
Reaction score
2,923
Location
Lansdale, PA, USA
Yep looks to be in the same family as the AR5007EG and uses the same driver package.

What kind of laptop is it?
 
   #14  

thismember

Verified VCDS User
Verified
Joined
Feb 26, 2014
Messages
7
Reaction score
0
Location
USA
VCDS Serial number
C?ID=208399
Yep looks to be in the same family as the AR5007EG and uses the same driver package.

What kind of laptop is it?

It's an Asus EEE PC 1000HE - I'm the one who also can't connect to the "09-Central Elec" controller via wired USB.
 
   #15  

invisiblewave

Verified VCDS User
Verified
Joined
Feb 25, 2014
Messages
56
Reaction score
8
Location
USA
VCDS Serial number
C?ID=208767
Mine won't see it in ad-hoc mode either. I tried Auto & DHCP.
 
   #16  

Santos

Administrator
Staff member
Administrator
Joined
Jan 29, 2014
Messages
333
Reaction score
2,923
Location
Lansdale, PA, USA
Did you set the profile using the Java utility?

Once set, unplug and replug the HEX-NET. It will show up as an AD-HOC network. If you take too long, it will switch over to the next wifi profile.
 
Top