Wireless Access

Reply
Contributor II

Wired RAP XP can connect but Windows 7 cannot

Using a RAP2. Using the same 802.1x policy on both WLAN and Wired.

I have an XP laptop that will connect to both.

Win7 laptop connects with the SSID but not wired.

Both machines are in the same AD group.

Is there some setting on the LAN adapter for Win7 that needs to be set?

 

Wired WIN7 show auth-tracebuf mac

Apr 26 15:25:07 station-up * 68:b5:99:f9:d0:94 01:80:c2:00:00:03 - - open system
Apr 26 15:25:07 station-up * 68:b5:99:f9:d0:94 01:80:c2:00:00:03 - - wired station
Apr 26 15:25:07 eap-id-req <- 68:b5:99:f9:d0:94 01:80:c2:00:00:03 1 5
Apr 26 15:25:37 eap-id-req <- 68:b5:99:f9:d0:94 01:80:c2:00:00:03 1 5
Apr 26 15:26:07 eap-id-req <- 68:b5:99:f9:d0:94 01:80:c2:00:00:03 1 5
Apr 26 15:26:37 eap-id-req <- 68:b5:99:f9:d0:94 01:80:c2:00:00:03 2 5
Apr 26 15:27:07 eap-id-req <- 68:b5:99:f9:d0:94 01:80:c2:00:00:03 2 5
Apr 26 15:27:36 eap-id-req <- 68:b5:99:f9:d0:94 01:80:c2:00:00:03 2 5
Apr 26 15:28:07 eap-id-req <- 68:b5:99:f9:d0:94 01:80:c2:00:00:03 3 5
Apr 26 15:28:37 eap-id-req <- 68:b5:99:f9:d0:94 01:80:c2:00:00:03 3 5
Apr 26 15:29:07 eap-id-req <- 68:b5:99:f9:d0:94 01:80:c2:00:00:03 3 5

 

 

Aruba Employee

Re: Wired RAP XP can connect but Windows 7 cannot

Have you verified that the windows 7 system has the Wired Auto Config turned on so that the system CAN do 1x on the wired side?


Harold
Contributor II

Re: Wired RAP XP can connect but Windows 7 cannot

No, how do I do that?

 

Thanks

Guru Elite

Re: Wired RAP XP can connect but Windows 7 cannot

Wired Autoconfig is a service that needs to be running on the Windows PC.

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Contributor II

Re: Wired RAP XP can connect but Windows 7 cannot

Thanks for the quick response Harold.

New Contributor

Re: Wired RAP XP can connect but Windows 7 cannot

Hi everyone.

 

I hope I'm on the right spot. I'm having a similar issue with a client on windows 7 and a RAP3 that gives the user access to a corporate network. The funny part is the computer connects fine via VPN (bypassing the aruba) but when its wired back to the aruba, it gets stuck on "unidentified network" and gets APIPA IP range. The wiredAutoconfig service is running and the appropiated certificates are in place for authenticaiton.

 

Last but not least, the computer worked fine on aruba for 2 months or so. We are not sure how a support session (service desk tech remote in) for email problems the user had one or two days before could have affected the network connectivity. 

 

Any ideas would be appreciated.

 

JC.

Guru Elite

Re: Wired RAP XP can connect but Windows 7 cannot

Did that specific computer ever work wired?  Did you turn on debugging for that user?  Do you see anything in the Radius server?

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

New Contributor

Re: Wired RAP XP can connect but Windows 7 cannot

Thanks for you reply.

 

Yes. As I said, that computer (desktop) was working before; wired. Still does perfectly if we wire the computer directly to the broadband modem and make a VPN connection via Aventail. By he way, all our RAPs have the wireless administratively disabled and just E1 port can be used. Access to debugging or the Radius Server is above my support level, but I will suggest level III to check into it.

 

JC.

New Contributor

Re: Wired RAP XP can connect but Windows 7 cannot

Hi cjoseph,

 

I was able to figure this one out and I thought it would be good to share.  After sending the user a new aruba proved to be useless, we started digging a little deeper on the previous ticket the user had because email problems. We found out that another tech changed the default Advanced NIC settings for Jumbo packet handling from "Disabled" to  "4088 bytes"

 

I quickly set a test computer in our office with those same NIC settings and I was able to recreate the error: “Unidentified network” and APIPA address. Once we changed the settings back to "Disabled" which it's the default, connectivity through Aruba was restored. Not sure how the previous tech thought  that Outlook email handling could benefit from changing this setting but we immediately advised all support teams to refrain from changing "Jumbo Packet" handling, at least for our Windows 7 users wired on RAP3.

 

I hope someone else finds this useful.

 

JC. 

 

 

 

 

Guru Elite

Re: Wired RAP XP can connect but Windows 7 cannot

Simply awesome!

 

Thanks for the solution!

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: