Connecting Windows PC to an Office Network, TAP interface

kooskoets

I currently have an office environment where an OpenVPN server is running and several off site clients connect successfully.

As an administrator, I have a laptop (Windows 7) and sometimes would like to access the network as well. I installed the OpenVPN GUI for Windows.

I can connect properly. However, I cannot access the office network.

I am running a TAP interface. IP range: 192.168.1.x

Interesting fact: I noticed that if I am on the same IP range in a hotel (192.168.1.x), then I can access the office devices. Just now I was on 192.168.43.x, and I could not connect.

So probably I need to change something in the routing of my Windows Client.

Does anybody know what to change?

Traffic

Please see the Forum rules (top of page)

kooskoets

The client config is as follows:
------------------------------------
client
dev tap
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap
proto udp
remote blanked.asuscomm.com 1194
float
cipher BF-CBC
comp-lzo yes
keepalive 15 60
ns-cert-type server
<ca>
-----BEGIN CERTIFICATE-----
blanked
-----END PRIVATE KEY-----
</key>
resolv-retry infinite
nobind
---------------------------------

On the ASUS RT N66U I am not able to access the server config file, but here is a copy of the settings of the VPN server on the GUI of the router:
---------------------------------
Interface Type TAP
Protocol UDP
Server Port: 1194
Default : 1194
Firewall Auto

Authorization Mode TLS

Username/Password Authentication No

Extra HMAC authorization Disable
(tls-auth)

Allocate from DHCP No

Client Address Pool 192.168.1.200 - 192.168.1.209

Advanced Settings

Poll Interval 0
( 0 to disable )
minutes

Direct clients to redirect Internet traffic No

Respond to DNS Yes

Advertise DNS to clients Yes

Encryption cipher BF-CBC
Compression Enable
TLS Renegotiation Time -1
( -1 for default )
seconds

Manage Client-Specific Options Yes

Allow Client <-> Client Yes

Allow only specified clients No

Allowed Clients Blank

Custom Configuration
keepalive 1 180
-----------------------------------

Traffic

kooskoets wroteInteresting fact: I noticed that if I am on the same IP range in a hotel (192.168.1.x), then I can access the office devices. Just now I was on 192.168.43.x, and I could not connect.

It is called a network conflict.

NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.

:arrow: Never use 192.168.0.0/24 or 192.168.1.0/24 (or other common subnets) for your OpenVPN Server LAN :!:

You are advised to change your server LAN to a more unique RFC1918 compliant subnet. f.e 192.168.143.0/24

kooskoets wroteOn the ASUS RT N66U I am not able to access the server config file

Learn how to do that by reading ASUS RT documentation.

As you only read half the rules, for help with openvpn, start here: