Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | IPSec not through VPN |
|---|---|
| Date: | Sun, 24 Oct 2004 21:52:57 +0200 |
Hi All, I have the following situation: - Windows Server 2003 behing ISA 2003 as the server that runs Terminal Services(TS) - XP client behind USR8054 NAT that is able to pass through NAT-T I have created IPSec filter on the server to receive request on 3389 to connect to the TS but only this port it requires IPSec from the client. There is a CA installed on it, both sides authenticates with certificates, not via kerberos, because they are not in the same domain (over internet) On the client I have set the IPSec only respond rule. On the ISA 2003 I have set the appropriate UDP rules: 1701, 500, 4500 Despite the connection is not working. I don't want to use VPN, only use IPSec for this purpose. What else should be configured, what else did I forget to set? Any response would be appreciated. Br, G
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Cisco CBAC, Shawn Wall |
|---|---|
| Next by Date: | RE: Cisco CBAC, Andrew Shore |
| Previous by Thread: | Firewall Implementation Strategy ?, Vijay Kumar |
| Next by Thread: | Symantec Firewalls/Appliances, Jose Costa |
| Indexes: | [Date] [Thread] [Top] [All Lists] |