Connnected but not routing

  • Thread starter Thread starter Narek
  • Start date Start date
N

Narek

Hello All. First, thank you for looking at this issue.

Question... is there a way to force the packets to go
through the pptp connection when the client is connected
via VPN?

Please read the scenario writen below.

I have a VPN server on a windows 2000 server located
behind a Soho3 firewall. The server is fully service
packed.

I have a windows 2000 client located at another company
which needs to access the server via VPN. I have
successfully done so with many other clients. The problem
is that this particular client is using the same IP schema
as the VPN servers environment. So as a result, the
servers environment is on a 192.168.1.x (255.255.255.0)
environment, and so is the client. When the client
connects to my VPN server, the client receives a
192.168.1.x address. when this happens, all the network
related services on the clients machine are disabled (ie.
networked printers, networked drives). On rare occasions
with very poor initial response time i am able to ping the
VPN server from the client. via the VPN connection. I
notice that when i ping, the packets go down the normal
LAN connection and only after a long time of searching the
Lan does it come back and try to look at the VPN
connector. an LMHosts file would do no good since the
clients initial response is to look down the wrong pipe.


Thank you for your assistance.

Respectfully,


Narek
 
Check the routing table and the mask, metrics and gateway for each
connection. You can play with the routing table for this client to force
packets on one connection or other. However, i suspect you should not need
to do this.
What networks are the client trying to reach ? Is there a loop created ?
What is the metric on each connection ?
 
The metric is 1 and the subnet mask is 255.255.255.0. The gateway is
the same for both connectors since coincidently they too opted for
192.168.1.1 as the default gateway.
The client is trying to reach a 192.168.1.xxx via VPN which is the
same ip schematic as its own native environment. There is no loop
connected cause i see the packets going down the wrong connector. I
tried playing with the metrics which proved to be unsuccessful.

I have since resolved the issue by completely changing the IP
schematic of the server. I dont necessarily know if this was the most
efficient way however it worked. I understand that the packets are
going to look down the first pipe it finds with the 192.168.1.xxx
address and since both the VPN connector as well as its own intenral
nic were addressed similarly, it never bothered looking down the VPN
connect. Now that the VPN connector receives a different ip address
due to the change i made at the office with the VPN server, i am able
to connect flawlessly.

I am still open to learning what other options i may have had.
Unfortunatly this was a high profile case and i did not have the
luxury of waiting to find the most correct resolution.

Thank you for your input and assistance. It is very very much
appreciated.

Respectfully,

Narek
 
Back
Top