Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 930
  • Last Modified:

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
0
usslindstrom
Asked:
usslindstrom
  • 5
  • 3
1 Solution
 
MikeKaneCommented:
ARe you using a browser to test?    Check for proxy settings in the browser.  

A better test is to use nmap to scan the host across Vpn, or just try to telnet to port 443 over the vpn.    

0
 
usslindstromAuthor Commented:
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.
0
 
MikeKaneCommented:
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.  
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
usslindstromAuthor Commented:
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).
0
 
MikeKaneCommented:
Any local ROUTE tables on the PC that would send traffic elsewhere?  Local VPN adapters that capture traffic?   I'm grasping for straws here since it's an unusual description.    

The traffic must flow somewhere....    Do you have a switch with a monitor port capability to run a trace at the Router level just to make sure packets are being sent there?  How about at least on the host itself?
0
 
usslindstromAuthor Commented:
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.
0
 
usslindstromAuthor Commented:
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.
0
 
usslindstromAuthor Commented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now