Page 1 of 1

No Internet on XP client, but on Win7 client

Posted: Sun Jul 31, 2011 4:47 pm
by al3x
Hi!

I recently successfully set up my OpenVPN Server and connected to it with a Windows 7 client.
Everything was working flawlessly and I still had connectivity to the normal Internet since I don't push a gateway.
But my friend loses his Internet connectivity when he connects from his XP client.
The configuration is exactly the same.

Server:

Code: Select all

port 1194
proto udp
mode server
tls-server
dev tun
ifconfig 10.10.10.1 255.255.255.255
server 10.10.10.0 255.255.255.0
ca ca.pem
cert cert.pem
key key.pem
dh dh.pem
ifconfig-pool-persist ipp.txt
push "route 10.0.0.0 255.0.0.0"
push "dhcp-option DNS 192.168.1.xyz"
#push "redirect-gateway"
push "route 0.0.0.0 0.0.0.0"
auth SHA1
cipher aes-256-cbc
comp-lzo
user nobody
group nogroup
persist-key
persist-tun
verb 7
Client:

Code: Select all

tls-client
pull
dev tun
proto udp
remote #.#.#.# 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.pem
cert cert.pem
key key.pem
cipher AES-256-CBC
comp-lzo
auth SHA1
verb 3
mute 20
What should I do so it still keeps connected to the normal Internet when on a XP client?

Thanks in advance!

Re: No Internet on XP client, but on Win7 client

Posted: Sun Jul 31, 2011 5:12 pm
by Mimiko
Hello.

Oh you messed at server's config, that's why it does not work.

Code: Select all

ifconfig 10.10.10.1 255.255.255.255
You don't need this, because you declare this with:

Code: Select all

server 10.10.10.0 255.255.255.0
Server's local tunnel adapter always will get 10.10.10.1.

Code: Select all

push "route 10.0.0.0 255.0.0.0"
This is your server's LAN mask? If so, then you have to use different IP pool when declaring "server" something like 192.168.10.0 255.255.255.0.

Code: Select all

push "dhcp-option DNS 192.168.1.xyz"
Don't hide last decimal in this private IP - it's not a hacking hint. Which lan does bellong that dns?

Code: Select all

push "route 0.0.0.0 0.0.0.0"
This is your WinXP problem, because on Win7 route adding at client side seems to be treacky and not always working. Remove this line.