My network and VPNing network have the same IP range. Please Help?

[ComputerDude5565]

So my network with the server that im connecting to has the ip range of 192.168.1.XXX and the network that I am VPNing in from has the same IP range 192.168.1.XXX. So the computer with the VPN doesnt go to the VPN it stays within the local network and I cant connect. Ive been trying to add a persistent route but not to familiar with it. Unfortunatly I cant chagne the range on either network. I need a qick fix. Here is a guy with the same problem.

http://www.howtonetworking.com/casestudy/vpn2.htm

 

[Packet7]

Hello,

Normally, you would NAT this at the Firewall. However, I'm guessing you're configure a client server VPN? What software are you using?

Rgds,

John

 

[ComputerDude5565]

hey um the VPN host was just an incomming connection and a win 200 sever and the client was just a vpn connection in netwrok connections....but the trick was i couldnt alter the routers in any way on either side....unfortunatly i had to take drastic measures and was forced to bring down 3 remote sites and a local one for the day so i could change the ip range....but everhting is good and working now thanks anyways

 

[Packet7]

Thanks for the update. Renumbering is the best way to go. Glad to hear you have it fixed.

Rgds,

John

 

[ComputerDude5565]

Well I thought I was in the clear but another problem has arose. I was forced to clear the firmware on my router (FVS318) Netgear Firewall Router and so I ran into some problems. This is a vpn router but i do not use the vpn i simple use windows incomming connection. But i needed to foward the incomming request to my server which i did as follows VPN TCP 1723 and L2TP UDP 1701. But now my remote users on the vpn experince inconsistency and dropped connections. Also it takes a few attempts before connecting. I believe this is because of my firewall seeing as how i have never changed anything on the server. What other ports shout i foward?

 

[Packet7]

Hi,

Are you using a rule on the Netgear? If so, what time of NAT? I'm guessing you have the remote hosts pointing to a public IP on the Netgear with port forwarding setup to the Microsoft box. Are they L2TP or IPsec clients?

Rgds,

John

 

[ComputerDude5565]

Im not sure what you mean by rule...I have a service added for VPN on port 1723 TCP and that port is fowareded to my server. There is not NAT. Remote host connects to my WAN...Static IP. And im prety sure there IPSec just the defual windows vpn.

 

[Packet7]

Does your Firewall have a CLI? I think the best approach is to debug an inbound IPsec packet to determine what your Firewall is doing with the packet.

Rgds,

John

 

[ComputerDude5565]

wow should have taken a look at the log long time ago. this should help

Mon, 12/04/2006 11:52:49 - TCP connection dropped - Source:xxx.xxx.xxx.xxx, 17898, WAN - Destination:xxx.xxx.xxx.xxx, 1723, LAN - 'Suspicious TCP Data'

the desitination is my sever ip address and the soruce is my remote eerminal address this also pops up

Mon, 12/04/2006 13:05:56 - TCP connection dropped - Source:xxx.xxx.xxx.xxx, 33428, WAN - Destination:xxx.xxx.xxx.xxx, 1723, LAN - 'TCP:Syn Flooding'

this is also my ip connecting

 

[ComputerDude5565]

ok i think this will work

can i get the port ranges for

IPSec and if it is UDP TCP or TCP/UDP
L2TP and if it is UDP TCP or TCP/UDP
PPTP and if it is UDP TCP or TCP/UDP

then i open all those ports and that will cover all my bases for hte vpn yea?