w2k3 + vpn problem

  • Thread starter Thread starter Björn
  • Start date Start date
B

Björn

Hi List

I have a w2k3 standard edition running as a vpn Server. The server has
direct access to internet(public ip)

Now I´m trying to connect to the vpn server from an private
network(192.168.6.x). The network is protected by a linux firewall opening a
vpn connection and doing the necessary routing for remote access connections
to the w2k3 server.

I have added a route on the w2k3 server so it knows the private network I´m
working with ( route -p 192.168.6.0 mask 255.255.255.0 192.168.55.[ip of
linux firewall] metric 1 if 192.168.55.[ip of w2k3])

If I connect from a client(w2k or xp) all works fine, but after a while with
no traffic over vpn the linux box disconnects the vpn connection. Now if a
client whants to connect to the w2k3 server the linux box opens the vpn
connection but the traffic doesn´t come back. It leaves the linux box but
the w2k3 server seems to ignore the added route in his routing table. If I
delete the route and add it again all works fine until the vpn connectin
closes. Any Ideas? I searched google for this problem but don´t find
anything.

regards

Björn
 
Set up a demand-dial interface on the server, and configure the static
route to use this interface (using the new static route wizard).

Now change the dialup client to connect to this dd interface (by using
the interface name as the username for the connection). The client will
connect to the demand-dial interface, and the route will be added to the
server's routing table. (this is the technique used for router-to-router
connections).
 
Now all works fine, thanks for your help

Björn

Bill Grant said:
Set up a demand-dial interface on the server, and configure the static
route to use this interface (using the new static route wizard).

Now change the dialup client to connect to this dd interface (by using
the interface name as the username for the connection). The client will
connect to the demand-dial interface, and the route will be added to the
server's routing table. (this is the technique used for router-to-router
connections).

Björn said:
Hi List

I have a w2k3 standard edition running as a vpn Server. The server has
direct access to internet(public ip)

Now I´m trying to connect to the vpn server from an private
network(192.168.6.x). The network is protected by a linux firewall
Click to expand...
opening
a
vpn connection and doing the necessary routing for remote access connections
to the w2k3 server.

I have added a route on the w2k3 server so it knows the private network I´m
working with ( route -p 192.168.6.0 mask 255.255.255.0 192.168.55.[ip of
linux firewall] metric 1 if 192.168.55.[ip of w2k3])

If I connect from a client(w2k or xp) all works fine, but after a while with
no traffic over vpn the linux box disconnects the vpn connection. Now if a
client whants to connect to the w2k3 server the linux box opens the vpn
connection but the traffic doesn´t come back. It leaves the linux box but
the w2k3 server seems to ignore the added route in his routing table. If I
delete the route and add it again all works fine until the vpn connectin
closes. Any Ideas? I searched google for this problem but don´t find
anything.

regards

Björn
Click to expand...
Click to expand...
 
Back
Top