Threat level definition
Search:
Home
Bugtraq
Vulnerabilities
Mailing Lists
Jobs
Tools
Vista
News
Infocus
Foundations
Microsoft
Unix
IDS
Incidents
Virus
Pen-Test
Firewalls
Focus On: Vista
Columnists
Mailing Lists
Newsletters
Bugtraq
Focus on IDS
Focus on Linux
Focus on Microsoft
Forensics
Pen-test
Security Basics
Vuln Dev
Vulnerabilities
Jobs
Job Opportunities
Resumes
Job Seekers
Employers
Tools
RSS
News
Vulns
Firewalls
Back to list
|
Post reply
Remote Branch reconfiguration
Jan 29 2008 10:21PM
Jon (jono29 gmail com)
Hello,
/First of all apologies if this is the wrong list./
I have, or rather had a few site to site vpn's set up. This is not my
setup, but rather its
inherited . I have two remote branches terminating on one pix at the
head office and another
vpn terminating on a different pix, also at the head office. On these
tunnels I pass RDP
traffic aimed at a Term server. From the termserver, there is a seperate
route out to the
internet for all hosts. The models of pix are 501's. I am led to believe
that you can only
have a maximum of two tunnels terminating on any one 501 firewall. I
presume this is why two
501's were used. Now to my issue: For reasons best left unsaid, the adsl
line on the pix
with only one site to site vpn configured has had the line cancelled.
This is causing me a
lot of grief from a customer and bearing in mind I dont know that much
about cisco configs I
am at a bit of a loss of how to get the third and presently cancelled
remote branch securely
connected to my head end. Would it be possible to configure an access
list on the pix that
allows RDP traffic from the remote site - if so, then how? I have an
Internet connection
available to me at the remote branch, I just need to know the best way
to integrate into the
only available pix that is remaining.
To summarise:
Remote Branch A & VPN Head END PIX 1
Remote Branch B
Remote Branch C VPN Head END PIX 2 (Now Cancelled)
Possible:
Remote Branch C RDP (3389) Head END PIX 1
All the Pix's are 501's. Trm Server is Windows 2000. Clients are XP.
I hope this makes sense - any help much appreciated.
Regards
J
[ reply ]
Privacy Statement
Copyright 2007, SecurityFocus
/First of all apologies if this is the wrong list./
I have, or rather had a few site to site vpn's set up. This is not my
setup, but rather its
inherited . I have two remote branches terminating on one pix at the
head office and another
vpn terminating on a different pix, also at the head office. On these
tunnels I pass RDP
traffic aimed at a Term server. From the termserver, there is a seperate
route out to the
internet for all hosts. The models of pix are 501's. I am led to believe
that you can only
have a maximum of two tunnels terminating on any one 501 firewall. I
presume this is why two
501's were used. Now to my issue: For reasons best left unsaid, the adsl
line on the pix
with only one site to site vpn configured has had the line cancelled.
This is causing me a
lot of grief from a customer and bearing in mind I dont know that much
about cisco configs I
am at a bit of a loss of how to get the third and presently cancelled
remote branch securely
connected to my head end. Would it be possible to configure an access
list on the pix that
allows RDP traffic from the remote site - if so, then how? I have an
Internet connection
available to me at the remote branch, I just need to know the best way
to integrate into the
only available pix that is remaining.
To summarise:
Remote Branch A & VPN Head END PIX 1
Remote Branch B
Remote Branch C VPN Head END PIX 2 (Now Cancelled)
Possible:
Remote Branch C RDP (3389) Head END PIX 1
All the Pix's are 501's. Trm Server is Windows 2000. Clients are XP.
I hope this makes sense - any help much appreciated.
Regards
J
[ reply ]