CCIE wireless

[ScottMac]

Perhaps they pay more because smart people are so hard to find in your neighborhood?

I'm out of this discussion to go talk to a brick wall that has better comprehension.

 

[jorken]

So.... how bout that CCIE wireless?

 

[DisgruntledVirus]

Originally posted by: ScottMac
Perhaps they pay more because smart people are so hard to find in your neighborhood?

I'm out of this discussion to go talk to a brick wall that has better comprehension.

I'm sure the brick wall would be easier to talk to

 

[alkemyst]

Originally posted by: DisgruntledVirus

Originally posted by: ScottMac
Perhaps they pay more because smart people are so hard to find in your neighborhood?

I'm out of this discussion to go talk to a brick wall that has better comprehension.

I'm sure the brick wall would be easier to talk to

I agree you guys are like a box of rocks.

 

[alkemyst]

Originally posted by: jorken
So.... how bout that CCIE wireless?

It's easy...just get your CCNP and you should be ready for the wireless exam

 

[JackBurton]

I was able to implement GTC authentication using the built in Wireless Zero service within Windows XP so users could authenticate to our Cisco APs using their RSA tokens, even when Cisco and Microsoft both said it couldn't be done. Do I get a cookie?

 

[xSauronx]

Originally posted by: JackBurton
I was able to implement GTC authentication using the built in Wireless Zero service within Windows XP so users could authenticate to our Cisco APs using their RSA tokens, even when Cisco and Microsoft both said it couldn't be done. Do I get a cookie?

 

[JackBurton]

Originally posted by: xSauronx

Originally posted by: JackBurton
I was able to implement GTC authentication using the built in Wireless Zero service within Windows XP so users could authenticate to our Cisco APs using their RSA tokens, even when Cisco and Microsoft both said it couldn't be done. Do I get a cookie?

Thanks man. I appreciate it.

 

[spidey07]

Originally posted by: JackBurton
I was able to implement GTC authentication using the built in Wireless Zero service within Windows XP so users could authenticate to our Cisco APs using their RSA tokens, even when Cisco and Microsoft both said it couldn't be done. Do I get a cookie?

Good job. But I don't see why that would be a problem, but it would depend on what hotfixes/service packs you have on the client.

 

[alkemyst]

Originally posted by: spidey07

Originally posted by: JackBurton
I was able to implement GTC authentication using the built in Wireless Zero service within Windows XP so users could authenticate to our Cisco APs using their RSA tokens, even when Cisco and Microsoft both said it couldn't be done. Do I get a cookie?

Good job. But I don't see why that would be a problem, but it would depend on what hotfixes/service packs you have on the client.

it wasn't though, that was his point I believe even though both said he shouldn't be able to do that.

It's like the textbook limits of ethernet and other media. The book is usually VERY conservative what real world shows.

In my IBM PS/2 days, I pulled off quite a bit with their hardware that they said couldn't be done.

 

[JackBurton]

Originally posted by: spidey07

Originally posted by: JackBurton
I was able to implement GTC authentication using the built in Wireless Zero service within Windows XP so users could authenticate to our Cisco APs using their RSA tokens, even when Cisco and Microsoft both said it couldn't be done. Do I get a cookie?

Good job. But I don't see why that would be a problem, but it would depend on what hotfixes/service packs you have on the client.

Windows XP doesn't support PEAP with GTC authentication natively. MS said Vista would have it, but to my knowledge it does not. You have to use a third party wireless client for that functionality. We didn't want that option for two reasons, cost and lack of control. With the solution I provided, you can use the Windows' built in wireless client, and most importantly, the wireless configurations can be pushed out through a group policy.

 

[drebo]

Originally posted by: JackBurton

Originally posted by: spidey07

Originally posted by: JackBurton
I was able to implement GTC authentication using the built in Wireless Zero service within Windows XP so users could authenticate to our Cisco APs using their RSA tokens, even when Cisco and Microsoft both said it couldn't be done. Do I get a cookie?

Good job. But I don't see why that would be a problem, but it would depend on what hotfixes/service packs you have on the client.

Windows XP doesn't support PEAP with GTC authentication natively. MS said Vista would have it, but to my knowledge it does not. You have to use a third party wireless client for that functionality. We didn't want that option for two reasons, cost and lack of control. With the solution I provided, you can use the Windows' built in wireless client, and most importantly, the wireless configurations can be pushed out through a group policy.

Feel like sharing?

 

[spidey07]

Originally posted by: JackBurton

Originally posted by: spidey07

Originally posted by: JackBurton
I was able to implement GTC authentication using the built in Wireless Zero service within Windows XP so users could authenticate to our Cisco APs using their RSA tokens, even when Cisco and Microsoft both said it couldn't be done. Do I get a cookie?

Good job. But I don't see why that would be a problem, but it would depend on what hotfixes/service packs you have on the client.

Windows XP doesn't support PEAP with GTC authentication natively. MS said Vista would have it, but to my knowledge it does not. You have to use a third party wireless client for that functionality. We didn't want that option for two reasons, cost and lack of control. With the solution I provided, you can use the Windows' built in wireless client, and most importantly, the wireless configurations can be pushed out through a group policy.

Heh, now you're talking an OS/driver /client linkage, not a network thing.

 

[JackBurton]

Originally posted by: spidey07

Originally posted by: JackBurton

Originally posted by: spidey07

Originally posted by: JackBurton
I was able to implement GTC authentication using the built in Wireless Zero service within Windows XP so users could authenticate to our Cisco APs using their RSA tokens, even when Cisco and Microsoft both said it couldn't be done. Do I get a cookie?

Good job. But I don't see why that would be a problem, but it would depend on what hotfixes/service packs you have on the client.

Windows XP doesn't support PEAP with GTC authentication natively. MS said Vista would have it, but to my knowledge it does not. You have to use a third party wireless client for that functionality. We didn't want that option for two reasons, cost and lack of control. With the solution I provided, you can use the Windows' built in wireless client, and most importantly, the wireless configurations can be pushed out through a group policy.

Heh, now you're talking an OS/driver /client linkage, not a network thing.

True.

 

[JackBurton]

Originally posted by: drebo
Feel like sharing?

You'll need the PEAP Supplicant provided by some of Cisco's wireless clients. Install that on the client and server and you'll be able to push out Windows wireless configurations through a group policy from the server.

 

[Cooky]

What advantage do you gain over the regular PEAP w/ PEAP GTC?
Besides the supplicant, do you need something else to support it?

For example, from Cisco's ACS server, do you need to apply a new patch or upgrade?
We currently run PEAP w/ ACS 4.2.

 

[JackBurton]

Originally posted by: Cooky
What advantage do you gain over the regular PEAP w/ PEAP GTC?
Besides the supplicant, do you need something else to support it?

For example, from Cisco's ACS server, do you need to apply a new patch or upgrade?
We currently run PEAP w/ ACS 4.2.

We needed the ability to authenticate to our APs with RSA tokens. PEAP with GTC lets us do that. It's pretty cool. When the wireless client finds the AP, it will prompt you for your RSA token. You enter your information and you're then granted access to the network.

Sorry, I don't think I answer your question fully. You don't need to do anything different on your ACS server. Try using Cisco's wireless client first, or what we used, Funk Odyssey Client. If you can authenticate using your RSA token with those clients, you can integrate the PEAP supplicant with Windows and get that same functionality with the Windows built in wireless client. Like I said, the great thing about it is, you can then push out those wireless configurations from the server. On top of that, with RSA security, your wireless network is pretty damn secure. About as secure as a wireless network can be.

 

[RadiclDreamer]

Originally posted by: JackBurton

Originally posted by: Cooky
What advantage do you gain over the regular PEAP w/ PEAP GTC?
Besides the supplicant, do you need something else to support it?

For example, from Cisco's ACS server, do you need to apply a new patch or upgrade?
We currently run PEAP w/ ACS 4.2.

We needed the ability to authenticate to our APs with RSA tokens. PEAP with GTC lets us do that. It's pretty cool. When the wireless client finds the AP, it will prompt you for your RSA token. You enter your information and you're then granted access to the network.

Sorry, I don't think I answer your question fully. You don't need to do anything different on your ACS server. Try using Cisco's wireless client first, or what we used, Funk Odyssey Client. If you can authenticate using your RSA token with those clients, you can integrate the PEAP supplicant with Windows and get that same functionality with the Windows built in wireless client. Like I said, the great thing about it is, you can then push out those wireless configurations from the server. On top of that, with RSA security, your wireless network is pretty damn secure. About as secure as a wireless network can be.

Not to thread hijack or anything, but last I heard Juniper bought the Odyssey software/Funk

 

[JackBurton]

Originally posted by: RadiclDreamer
Not to thread hijack or anything, but last I heard Juniper bought the Odyssey software/Funk

I'm not sure who owns the Funk software now. I haven't used it in a long time.

 

[freegeeks]

Originally posted by: JackBurton

Originally posted by: RadiclDreamer
Not to thread hijack or anything, but last I heard Juniper bought the Odyssey software/Funk

I'm not sure who owns the Funk software now. I haven't used it in a long time.

Juniper