| Home | Register | Members | Search | Links |
![]() |
| Thread Tools | Display Modes |
|
jlee161@comcast.net
Guest
Posts: n/a
|
I'm trying to accomplish the following
Create a Site to Site VPN between a BEFVP41 and Windows 2003 using IPSec. I have gotten it to connect and I can ping the Win2k3 internal NIC (192.168.1.1), however I can't ping any other devices on 192.168.1.0/24. And from 192.168.1.0/24 I can't ping anything on 10.0.0.0/24. What's strange is if I configure the tunnel to go straight to a windows machine (ex 192.168.1.103) on 192.168.1.0/24 I can't ping it, but can open up netbios shares. However, I can't reach that same machine if the tunnel is to subnet 192.168.1.0/24. you can view a net diagram here: ftp://71.225.96.243/netmapv1.jpg (I included 192.168.15.0/24 for informational purpose only, as that subnet is working on both tunnel ends of 10.0.0.0/24 and 192.168.15.0/24. I have no plans to connect 192.168.1.0/24 and 192.168.15.0/24 yet) |
|
|
|
|
|||
|
|||
|
|
|
| |
|
Robert L [MS-MVP]
Guest
Posts: n/a
|
Check any errors in the log and post back with the error. This troubleshooting IPSec link may help,
IPSec Audit Policy: To troubleshoot IPSec when it does not behave the way that you expect it to, first check the results of the Phase One and Phase Two exchanges ... www.chicagotech.net/ipsec.htm Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com <(E-Mail Removed)> wrote in message news:(E-Mail Removed) oups.com... I'm trying to accomplish the following Create a Site to Site VPN between a BEFVP41 and Windows 2003 using IPSec. I have gotten it to connect and I can ping the Win2k3 internal NIC (192.168.1.1), however I can't ping any other devices on 192.168.1.0/24. And from 192.168.1.0/24 I can't ping anything on 10.0.0.0/24. What's strange is if I configure the tunnel to go straight to a windows machine (ex 192.168.1.103) on 192.168.1.0/24 I can't ping it, but can open up netbios shares. However, I can't reach that same machine if the tunnel is to subnet 192.168.1.0/24. you can view a net diagram here: ftp://71.225.96.243/netmapv1.jpg (I included 192.168.15.0/24 for informational purpose only, as that subnet is working on both tunnel ends of 10.0.0.0/24 and 192.168.15.0/24. I have no plans to connect 192.168.1.0/24 and 192.168.15.0/24 yet) |
|
|
|
|
|||
|
|||
|
jlee161@comcast.net
Guest
Posts: n/a
|
No matter what I do. I can't seem to make this work. Is this just not
possible? Is there some additional config that must be done win2k3 other than the two rules, plus setting up, the two nic's (one with public, and one private) and turning on nat????????? |
|
|
|
|
|||
|
|||
|
jlee161@comcast.net
Guest
Posts: n/a
|
Here is one of the logs from the even view. And the local and remote
secure groups are correct, and have been checked and double checked. Even when it manages to connect I can only ping 192.168.1.1 from 10.0.0.xx, and can't reach anything from 192 to 10 IKE security association negotiation failed. Mode: Data Protection Mode (Quick Mode) Filter: Source IP Address 192.168.1.0 Source IP Address Mask 255.255.255.0 Destination IP Address 10.0.0.0 Destination IP Address Mask 255.255.255.0 Protocol 0 Source Port 0 Destination Port 0 IKE Local Addr 192.168.1.1 IKE Peer Addr 71.225.96.243 IKE Source Port 500 IKE Destination Port 500 Peer Private Addr Peer Identity: Preshared key ID. Peer IP Address: 71.225.96.243 Failure Point: Me Failure Reason: No policy configured Extra Status: Processed third (ID) payload Responder. Delta Time 1 0x0 0x0 For more information, see Help and Support Center at |
|
|
|
|
|||
|
|||
|
jlee161@comcast.net
Guest
Posts: n/a
|
IKE security association negotiation failed.
Mode: Data Protection Mode (Quick Mode) Filter: Source IP Address 192.168.1.0 Source IP Address Mask 255.255.255.0 Destination IP Address 10.0.0.0 Destination IP Address Mask 255.255.255.0 Protocol 0 Source Port 0 Destination Port 0 IKE Local Addr 192.168.1.1 IKE Peer Addr 71.225.96.243 IKE Source Port 500 IKE Destination Port 500 Peer Private Addr Peer Identity: Preshared key ID. Peer IP Address: 71.225.96.243 Failure Point: Me Failure Reason: No policy configured Extra Status: Processed third (ID) payload Responder. Delta Time 1 0x0 0x0 For more information, see Help and Support Center at |
|
|
|
|
|||
|
|||
|
Phillip Windell
Guest
Posts: n/a
|
It may not be possible. All VPN implementations are to a certain degree
"proprietary" with whatever device you are using. RRAS (Windows Server) uses two connections to create a Site-to-Site VPN. Each connection is one direction, so it takes two connections to get two-way communication. So it implies that you want an RRAS box at each end. I have doubts that a Linksys box (whatever a BEFVP41 is) does it the same way. Now ISA Server uses RRAS "under-the-hood" to perform its VPN tasks and there are supposed to be ways to make it work with other devices. You can check into these articles and see if they help any. That is the best I can tell you. Configuring IPSec Site-to-Site Connections Between ISA Server 2004 and Third-Party Gateways http://www.microsoft.com/technet/pro...siteipsec.mspx Establishing an IPSec site-to-site tunnel between an ISA 2004 Firewall and a D-Link DI-804HV IPSec VPN Router http://www.isaserver.org/articles/2004isadlink.html Configuring IPSec Tunnel Mode VPN Between ISA Server 2004 and Astaro Security Linux http://www.microsoft.com/technet/pro...elmodevpn.mspx Configuring IPSec Tunnel Mode VPN Between ISA Server 2004 and SmoothWall Express 2.0 http://www.microsoft.com/technet/pro...pnexpress.mspx Configuring IPSec Tunnel Mode VPN Between ISA Server 2004 and Netopia R9100 4.11.3 http://www.microsoft.com/technet/pro...n/netopia.mspx -- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com <(E-Mail Removed)> wrote in message news:(E-Mail Removed) oups.com... > No matter what I do. I can't seem to make this work. Is this just not > possible? Is there some additional config that must be done win2k3 > other than the two rules, plus setting up, the two nic's (one with > public, and one private) and turning on nat????????? > |
|
|
|
|
|||
|
|||
|
jlee161@comcast.net
Guest
Posts: n/a
|
Yeah, I'm beginning to come to that conclusion. My cohort, on the
other end of this tunnel, and I are going to give it one more shot. He believes the reason I couldn't reach his other clients is that they may have been getting the wrong default gateway. However next we'll try ISA 2004. |
|
|
|
|
|||
|
|||
|
Phillip Windell
Guest
Posts: n/a
|
Default Gateways are only for the Internet ("unknown routes"). The Lan on
the opposite side of each VPN is "known",...so you have to use "specific" Routes. It is done by placing Static Routes on the Device that acts as the Clients Default Gateway so that traffic for those particular remote destinations get properly passed over to the VPN Device. However if the Device providing the Internet and the device providing the VPN are the same device,...*and* if each respective LAN is a single subnet,...then you just make that one device the Default Gateway and forget it. You also have to make sure that both of the LANs are not using the same IP# Range. -- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com ----------------------------------------------------- Understanding the ISA 2004 Access Rule Processing http://www.isaserver.org/articles/IS...cessRules.html Troubleshooting Client Authentication on Access Rules in ISA Server 2004 http://download.microsoft.com/downlo...7/ts_rules.doc Microsoft Internet Security & Acceleration Server: Guidance http://www.microsoft.com/isaserver/t...dance/2004.asp http://www.microsoft.com/isaserver/t...dance/2000.asp Microsoft Internet Security & Acceleration Server: Partners http://www.microsoft.com/isaserver/partners/default.asp Deployment Guidelines for ISA Server 2004 Enterprise Edition http://www.microsoft.com/technet/pro...isaserver.mspx ----------------------------------------------------- <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com... > Yeah, I'm beginning to come to that conclusion. My cohort, on the > other end of this tunnel, and I are going to give it one more shot. He > believes the reason I couldn't reach his other clients is that they may > have been getting the wrong default gateway. However next we'll try > ISA 2004. > |
|
|
|
|
|||
|
|||
|
|
|
| |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| SITE-To-SITE VPN using Windows Server 2003 Standard | S H A R I Q U E | Windows Networking | 8 | 01-03-2009 04:25 PM |
| L2TP/IPSEC SITE TO SITE VPN Issues | JoeyG 2391 | Windows Networking | 4 | 10-17-2008 04:13 AM |
| W2k3 - Site to Site VPN using L2TP/IPSec and certificates | Ewald Bracko | Windows Networking | 0 | 06-12-2008 05:09 PM |
| 2003 Server RRAS Site-To-Site VPN Dropping | Russell Preece | Windows Networking | 8 | 09-29-2005 09:23 AM |
| IPSec Site to Site VPN | T Bodie | Windows Networking | 1 | 05-17-2005 08:44 PM |
Forum Software Powered by vBulletin®, Copyright Jelsoft Enterprises Ltd.
SEO by vBSEO 3.3.2 ©2009, Crawlability, Inc. |



Linear Mode

