Tricky Setup Problem with ASA 5505 / WLC / AP's

[tspmonk]

This one will take a little explaining but here goes..
I have a WLC 4400 that manages our AP's. We have a few wlan/ssid's that the ap's use.
We have locations around the county that are connected back to us on our fiber. (So Direct Access) When we plug AP's into any of the remote or local sites we have no problems.
Second setup: We have locations that are not on our fiber so we use ASA 5505's to create a tunnel using easy vpn.
They connect just fine and users into the 5505 have no problems at all. But when we plug in a AP it connects up to the WLC and everything looks ok.
The client will get an ip and can ping everything on the remote network and out on the internet.
The problems that occurs is no traffic gets back? Like web, etc.. So when I try to bring up a web page internally or externally it just times out. All sites can be pinged just no way back?
Now the clients connecting to the AP's are getting addresses from the WLAN they are connecting to. The Users directly plugged in are getting them from the ASA 5505.
this is a rough explanation.. I can explain more if needed to help with the problem!
TIA!

 

[unclerico]

can you post teh config??

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[stubnski]

The client will get an ip and can ping everything on the remote network and out on the internet.
The problems that occurs is no traffic gets back? Like web, etc.. So when I try to bring up a web page internally or externally it just times out. All sites can be pinged just no way back

It sounds like you cannot resolve DNS. Can you resolve DNS on the internal network?


Stubnski

 

[VinceWhirlwind]

This forum is starting to get completely gummed-up with posts about ASAs & Pixs instead of "Cisco - Routers".

 

[tspmonk]

I will get the config up in the morning..
The DNS is okay. It resolves and pings internally and externally behind the asa 5505 on the vpn connection. Connected directly to the asa by ethernet and getting an ip on that subnet and also when getting an ip through a WLAN on the AP connected to the POE port.
It is only when I am connected to the WLAN/AP subnet that traffic doesn't seem to make it back. Pinging and resolving work fine. Even connecting to a network share. When grabbing a file it is slow but when I try to bring up a web page internally or externally it resolves tries to connect and then sits and spins it's wheels.

 

[unclerico]

vince is right, when you come back with the config post it in here

forum1598

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[tspmonk]

moved thread to:

http://www.tek-tips.com/viewthread.cfm?qid=1564250

thanks unclerico for the advice..