-
February 23rd, 2010, 06:13 PM
#1
I will try to keep it short
OK,
Have an office that I am working on that has 5 staticIP's provided by their ISP. I currently have one IP that points to a server that has two nic's, one on the WAN side and one on the LAN side, this server is also the DHCP and the DNS server for the LAN. Then I have a hardware VPN on another one of WAN IP's. The problem I am having is:
The device shows that the VPN tunnel is established, and I can ping to the LAN IP of the VPN, but am unable to get to anything on the LAN side. I know this is just a small tweek in the routing that I am missing, but what is it?
Post if you need more info.
No matter where you go........there you are.
-
February 24th, 2010, 12:07 PM
#2
A diagram of the actual main components might help here.
IP1.....IP2.....IP3.....IP4.....IP5
WAN.....LAN.....WAN.....LAN.....LAN
VPN
WAN-----Server-----ISP
Lan-----
or whatever.
edit: 3 articles re Vista and this issue - may prove useful;
http://www.smallbusinesscomputing.co...le.php/3791176
http://www.smallbusinesscomputing.co...le.php/3785976
http://itmanagement.earthweb.com/net...Over-a-VPN.htm
Last edited by CCT; February 24th, 2010 at 12:37 PM.
-
February 24th, 2010, 01:55 PM
#3
Chat Operator
Originally Posted by Irish Shark
OK,
Have an office that I am working on that has 5 staticIP's provided by their ISP. I currently have one IP that points to a server that has two nic's, one on the WAN side and one on the LAN side, this server is also the DHCP and the DNS server for the LAN. Then I have a hardware VPN on another one of WAN IP's. The problem I am having is:
The device shows that the VPN tunnel is established, and I can ping to the LAN IP of the VPN, but am unable to get to anything on the LAN side. I know this is just a small tweek in the routing that I am missing, but what is it?
Post if you need more info.
I *think* the issue here is that you are not getting correct IP info. The VPN endpoint is what is giving out the IP addresses. Make sure it's configured to provide IP's from the DHCP server. If it's giving out an internaly configured range of IP's, it may not be the same as the internal range that you are using.
<Ferrit> Take 1 live chicken, cut the head off, dance around doing the hokey pokey and chanting: GO AWAY BAD VIRUS, GO AWAY BAD VIRUS
-----------------------
Windows 7 Pro x64
Asus P5QL Deluxe
Intel Q6600
nVidia 8800 GTS 320
6 gigs of Ram
2x60 gig OCZ Vertex SSD (raid 0)
WD Black 750 gig
Antec Tri power 750 Watt PSU
Lots of fans
-
February 25th, 2010, 12:08 AM
#4
Originally Posted by Matridom
I *think* the issue here is that you are not getting correct IP info. The VPN endpoint is what is giving out the IP addresses. Make sure it's configured to provide IP's from the DHCP server. If it's giving out an internaly configured range of IP's, it may not be the same as the internal range that you are using.
The VPN is NOT giving out IP's. The server is, the VPN LAN side is configured with a static IP in the range of the IP's giveb out by the server for the local network.
No matter where you go........there you are.
-
February 25th, 2010, 12:32 AM
#5
Originally Posted by CCT
The articles are for software VPN's, which I don't have a problem with. The VPN is between two VPN hardware devices, between two office locations. I can access network resources from MAIN office to REMOTE through the VPN tunnel with no problem, but I am unable to do the same from the REMOTE to the MAIN.
here is some idea of how it lays out. Actual IP's have been changed.
Server
NIC-1
WAN 89.123.12.112
SUB 255.255.255.0
DEF 89.123.12.1
DNS 99.123.98.5
99.123.89.6
NIC-2 (This gives out DHCP and is the DNS for the LAN)
IP 192.168.111.2 (Static)
SUB 255.255.255.0
DEF 192.168.111.2
VPN (with DHCP off)
NIC-1
WAN 89.123.12.113
SUB 255.255.255.0
DEF 89.123.12.1
DNS 99.123.98.5
99.123.89.6
NIC-2 (LAN)
IP 192.168.111.9 (Static)
SUB 255.255.255.0
REMOTE
NIC-1
WAN (Dynamic)
SUB (Dynamic)
DEF (Dynamic)
NIC-2 (LAN) (DHCP server for LAN)
IP 10.10.10.1
SUB 255.255.255.0
DEF 10.10.10.1
Like I said, the VPN tunnel ip up and running, the issue is the routing on the MAIN side. Let me know if you need more
No matter where you go........there you are.
-
February 25th, 2010, 08:23 AM
#6
I got a number of good info hits using this Coogle search string;
hardware VPN tunnel unable to access LAN side
I hope that helps.
-
March 8th, 2010, 10:20 PM
#7
Anyone else have 2 cents?
Anyone else have any experience doing this?
No matter where you go........there you are.
-
March 23rd, 2010, 12:06 AM
#8
Resolved
Firmware on the Remote side VPN was corrupt. FIXED
No matter where you go........there you are.
Similar Threads
-
By sthorsell in forum BIOS/Motherboard Drivers
Replies: 0
Last Post: March 31st, 2005, 12:42 PM
-
By jsigmon in forum Microsoft Office
Replies: 2
Last Post: May 29th, 2002, 11:02 PM
-
By Morticia Addams in forum Tech Lounge & Tales
Replies: 29
Last Post: March 8th, 2002, 07:42 PM
-
Replies: 11
Last Post: April 29th, 2001, 08:13 PM
-
By pauladshead in forum Windows 95/98/98SE/ME
Replies: 1
Last Post: June 8th, 1999, 07:31 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks