[Openvpn-users] Routing Problem? Win2000 road warrior --OpenVPN-- Win2000 server -- Subnet

["Ben" <tainhan@xxxxxxxxxxx>]

Hi all,

I am using OpenVPN 2.0b11.
Server side: My Window Pro 2000 is working as OpenVPN server. There are two
other Window 2000 PCs on the subnet
Client: Window 2000 road warrior using Dialup
So far Client and Server are working fine :-). However, Client cannot ping
the other 2 PCs on server side.
There is a push route: push "route 192.168.1.0 255.255.255.0" in server
config-file. And the Route table on client side reflects that "push route"
(Please refer the Network configuration below)
Server is able to ping Client at 10.1.1.n
Client is able to ping 192.168.1.25 and 10.1.1.1, but not 192.168.1.26 or
192.168.1.27
PC1/PC2  is able to ping Server at 192.168.1.25 and 10.1.1.1, but not the
Client at 10.1.1.n
Please review my network and the config-files
What could be the problem?
Do I need to add some else setting for my config-file?
Any suggestion would be appreciated.
Thank you,
Ben

+Network Configuration:
192.168.1.25                 192.168.1.26      192.168.1.27
OpenVPN Server          PC1                     PC2
10.1.1.1                         |                           |
|                                     |                           |
Hub----------------------------------------
|
Gateway 192.168.1.1. There is a route 10.1.1.0 255.255.255.0 192.168.1.25
Router
DSL port 5555 forwarded to 192.168.1.25. No other port is forwarded to
192.168.1.25
|
Internet
|
10.1.1.n
OpenVNP Client
66.42.xxx.xxx Dialup

+config-files
#Server file
port 5555
proto udp
dev tun
ca ServerCA.pub
key  Serverkey.pri
cert Servercert.pub
dh dh1024.pri"
server 10.1.1.0 255.255.255.0
push "route 192.168.1.0 255.255.255.0"
client-to-client

keepalive 10 60
tls-auth Statickey.txt 0
comp-lzo
status openvpn-status.log
verb 4

#Client file
client
dev tun
proto udp
remote foo_server.com 5555
resolv-retry infinite
nobind
ca ServerCA.pub
key Clientkey.pri
cert Clientcert.pub
tls-auth Statickey.txt 1
comp-lzo
verb 4

-------
Route table on server side
Active Routes:
Network Destination       Netmask              Gateway             Interface
Metric
0.0.0.0                          0.0.0.0                 192.168.1.1
192.168.1.25     1
10.1.1.0                        255.255.255.252    10.1.1.1
10.1.1.1             1
10.1.1.0                        255.255.255.0       10.1.1.2
10.1.1.1            1
10.1.1.1                        255.255.255.255    127.0.0.1
127.0.0.1          1
10.255.255.255             255.255.255.255     10.1.1.1             10.1.1.1
1
127.0.0.0                      255.0.0.0               127.0.0.1
127.0.0.1          1
192.168.1.0                  255.255.255.0         192.168.1.25
192.168.1.25     1
192.168.1.25                255.255.255.255     127.0.0.1
127.0.0.1           1
192.168.1.255              255.255.255.255      192.168.1.25
192.168.1.25      1
224.0.0.0                     224.0.0.0                 10.1.1.1
10.1.1.1            1
224.0.0.0                     224.0.0.0                 192.168.1.25
192.168.1.25      1
255.255.255.255          255.255.255.255       10.1.1.1             10.1.1.1
1
Default Gateway:     192.168.1.1
===========================================================================
I don't have a route table on client side for now. However I already checked
it. There are the routes to 192.168.1.0 via 10.1.1.1
That why Client is able to ping 192.168.1.25

Thank you for your review,

Ben






____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users