Discussion Locked

VPN with Symantec 200 R.....

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi Guys,
I have a situation here.. I just installed a Symantec VPN 200 R for a client becoz they wanted remote access from different locations.. Their local IP scheme is 192.168.1.X.. They are using Windows 2000. The problem is that when I try logging in from home behind a Linksys Cable Router that also has its local IP scheme as 192.168.1.x I can only see the VPN box.. I can not even ping my server. I can web browse into the VPN box but can't go any further. I changed my home IP scheme to 172.22.x.x and I can get in without a problem. I can use a dial up and I can get in with no problems. The problem is that I have few clients who will log into the VPN box from places where they already are using 192.168.1.x scheme and they cannot changeit to some other IP scheme...
Also how do I have a client LOGON to my 2000 domain when they connect to the VPN??
Anyone have any comments ??????
Would greatly appreciate any help !!

6 replies

by Former member

Not enough info. But first, private addressing on a VPN server=bad idea. There's nto enough info because you don't say where your VPN server is. Is it at home? On this same 192.168 private addressed network? The IP of the VPN box is unclear. Need source/destination info...

by Former member

I think i got it now. This is a little wierd now because realistically you have, when you vpn, two gateways on the same subnet (your home router that translates you and the router at work, that translates them) for the 192.168.x.x network. Seems to me that there is a problem with your client PC internal routing table (type netstat -r at a command prompt) and it knows that your gateway is 192.168.?.? and it has resolved it's MAC address. Now when you VPN into the office, you try to get to 192.168.server, your PC and then the gateway assumes this is on the local segment and will not route out through the VPN. Normally, when one VPNs into another network, they have valid addresses, have a VPN client, and get another IP addres assigned by the far end. Here you have created a VPN tunnel, yet beyond the end points is the same subnet. I think the only thing you can do is change addresses or at least subnet, either end.

by ndhiman

Here is some more info.. I have a Real static IP address from my ISP.. 24.x.x.x. That is the IP of the Outside interface of my VPN router. The internal IP of VPN router is 192.168.1.1. This is in the office. I have a cable connection at home that gets a DHCP address from ISP and then I have a Linksys Cable router that allows me to do NAT and assigns my local PC a 192.168.1.x address. Let me know if u need any more info.

by ndhiman

So it seems like I have to change the IP scheme of my small network (SERVER SIDE)from 192.168.1.x to 192.168.200.x. I have 1 Win 2k DC and 10 win 2k clients. The server acts as a DNS, WINS, DHCP server. I will still keep the same domain name and thename of the server will still be same. Is it safe to do this.. If yes, is there a special way to do this? What should be done first and what should be done last???
Any comments ASAP will be helpful.. I only have 2 days left to do this.
Thanks

This discussion is closed to new replies.