2x Cisco RVS4000 / IPSec Tunnel = Can't https through vpn
Experts,
I have a bit of a strange problem here.
I have two Cisco RVS4000's setup with a VPN between them at two different sites. For testing, I have everything security-related 100% disabled on both little routers. No firewall, no IPS, nothing.
Everything works between the two sides, and I can access everything as if it were sitting right next to me (RDP, FTP, HTTP, ICMP, etc.)... Except 443.
Trying to access anything over https gets network timed out errors. What would be the cause of this?
The VPN settings for both sides are as follows (identical of course):
IKE with Preshared Key
Ph1 : 3DES / SHA1 / Grp 1024bit / Lifetime 28800
Ph2 : 3DES / SHA1 / Perfect Foward Secrecy Enabled / ***PSK*** / Grp 1024bit / Lifetime 3600
I have a bit of a strange problem here.
I have two Cisco RVS4000's setup with a VPN between them at two different sites. For testing, I have everything security-related 100% disabled on both little routers. No firewall, no IPS, nothing.
Everything works between the two sides, and I can access everything as if it were sitting right next to me (RDP, FTP, HTTP, ICMP, etc.)... Except 443.
Trying to access anything over https gets network timed out errors. What would be the cause of this?
The VPN settings for both sides are as follows (identical of course):
IKE with Preshared Key
Ph1 : 3DES / SHA1 / Grp 1024bit / Lifetime 28800
Ph2 : 3DES / SHA1 / Perfect Foward Secrecy Enabled / ***PSK*** / Grp 1024bit / Lifetime 3600
ASKER
Yes for the browser. Both FireFox and IE.
Telnetting to a host through the tunnel on 443 gives "connection failed."
Of course, doing anything local (local PC to local server) to each site works fine, there definately is some sort of access list blocking 443 through the tunnel.
As mentioned before, I've disabled everything on the little Cisco routers, so they're just providing NAT for internal clients and IPSec Tunnel support at the moment.
I have a DC at each site, and they're able to replicate freely, as well as DNS, FRS, etc. Everything is working great, except https. Very weird issue.
Telnetting to a host through the tunnel on 443 gives "connection failed."
Of course, doing anything local (local PC to local server) to each site works fine, there definately is some sort of access list blocking 443 through the tunnel.
As mentioned before, I've disabled everything on the little Cisco routers, so they're just providing NAT for internal clients and IPSec Tunnel support at the moment.
I have a DC at each site, and they're able to replicate freely, as well as DNS, FRS, etc. Everything is working great, except https. Very weird issue.
So as you traverse the cisco devices, the cisco's should record any dropped packets in the logs. I forget where the logs are on those, but it's viewable and should record any dropped packets and give a reason for the drop.
ASKER
Thanks for the suggestion.
Unfortunately, the only place I can see on those little RVS4000's to check logs, comes up 100% empty for all logs (including system).
Unfortunately, the only place I can see on those little RVS4000's to check logs, comes up 100% empty for all logs (including system).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No worries. Thank you very much for assisting me with this strange problem.
The one thing I haven't done up to this point is grab packet captures, and can definately go that way... Including Fiddler to see where the https request is going. The router is connected to a c2950, and I'm not entirely sure if those things support SPAN off the top of my head, but it'd definately be another place to take a look at.
PCs behind the devices are all receiving addresses from DHCP, and I'm not injecting any host routes throughout the domain, so it shouldn't be the case. - That being said, standard http and -well- any other traffic traverses the tunnel just fine and makes it to its destination, so we're most likely not dealing with any sort of L3 issue here.
The one thing I haven't done up to this point is grab packet captures, and can definately go that way... Including Fiddler to see where the https request is going. The router is connected to a c2950, and I'm not entirely sure if those things support SPAN off the top of my head, but it'd definately be another place to take a look at.
PCs behind the devices are all receiving addresses from DHCP, and I'm not injecting any host routes throughout the domain, so it shouldn't be the case. - That being said, standard http and -well- any other traffic traverses the tunnel just fine and makes it to its destination, so we're most likely not dealing with any sort of L3 issue here.
ASKER
Sorry for the delay here. Been very busy with other active issues that needed working out.
Still having the issue here, but it's consuming other protocols as well.
Almost everything over the VPN is working, but SMTP and HTTPS are being killed.
Still having the issue here, but it's consuming other protocols as well.
Almost everything over the VPN is working, but SMTP and HTTPS are being killed.
ASKER
Problem was with firmware. Updated to latest release and SSL traffic was finally able to go through.
Unfortunately, SMTP is still getting destroyed on the little thing, but at this point we can definately agree that it's the small little POS router.
Unfortunately, SMTP is still getting destroyed on the little thing, but at this point we can definately agree that it's the small little POS router.
A better test is to use nmap to scan the host across Vpn, or just try to telnet to port 443 over the vpn.