Windows 8 update

[psikey 1]

Need some pointers.

Previously using AirVPN on Windows 7 Pro machine as a headless server which I RDP into from both local network and over web using static IP and opendns.

Even with airvpn connected I could still RDP to see what the server was doing.

I then did Windows 8 Pro upgrade (not clean install) and now even though client connects the AirVPN webpage still shows Red (not connected) and uTorrent downloads still show my actual IP.

Also with AirVPN running I cannot RDP using the normal server static IP only by referencing its computer name on the local network, plus cannot connect remotely by dyndns.

Any suggestions? I did enable RAS for Windows 8 and have disabled AVG 2013 internet security temporarily but no luck yet. I also have Windows 8 Pro on my main machine (clean install) and if I run AirVPN on that with web or uTorrent then I am protected.

[Staff 9751]

Hello!

You need OpenVPN 2.3_rc1 and (optionally) the Air client for Windows 8:

https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=5827&Itemid=142#5834

We will soon publish the new package for Windows 8 in the Windows page, in the meantime please use the link above to download everything you need. Please note that you might like to uninstall OpenVPN 2.2.2 or older before installing 2.3_rc1.

Kind regards

[psikey 1]

Thanks, will give it a go.

[psikey 1]

OK

Can launch AirVPN without getting kicked out of RDP but AirVPN website still showing Red at the bottom. What next??

[Staff 9751]

OK

Can launch AirVPN without getting kicked out of RDP but AirVPN website still showing Red at the bottom. What next??

Hello!

Please send us the client logs.

Kind regards

[psikey 1]

Just doing a reboot of the server as the thread mentioned a reboot which I didn't do. Will report back.

[psikey 1]

No joy after reboot

Pardon my ignorance but where are the logs?

Only a readme file in C:\Program Files (x86)\OpenVPN (Still have OpenVPN client running).

[psikey 1]

04/12/2012 - 19:39 AirVPN client version: 1.7

04/12/2012 - 19:39 Reading options from C:\Users\Andrew\AppData\Roaming\AirVPN\Air\1.0.0.0\AirVPN.xml

04/12/2012 - 19:39 OpenVPN bundle version: OpenVPN 2.3_rc1

04/12/2012 - 19:39 OpenVPN current version: OpenVPN 2.3_rc1

04/12/2012 - 19:39 Ready.

04/12/2012 - 19:39 Login...

04/12/2012 - 19:39 Login success.

04/12/2012 - 19:39 Contacting service...

04/12/2012 - 19:39 Connecting...

04/12/2012 - 19:39 OpenVPN 2.3_rc1 x86_64-w64-mingw32 [sSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [iPv6] built on Nov 6 2012

04/12/2012 - 19:39 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables

04/12/2012 - 19:39 Socket Buffers: R=[65536->65536] S=[65536->65536]

04/12/2012 - 19:39 UDPv4 link local: [undef]

04/12/2012 - 19:39 UDPv4 link remote: [AF_INET]31.193.12.74:443

04/12/2012 - 19:39 TLS: Initial packet from [AF_INET]31.193.12.74:443, sid=a357172b 2f41fb43

04/12/2012 - 19:39 VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org

04/12/2012 - 19:39 VERIFY OK: nsCertType=SERVER

04/12/2012 - 19:39 VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org

04/12/2012 - 19:39 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

04/12/2012 - 19:39 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

04/12/2012 - 19:39 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

04/12/2012 - 19:39 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

04/12/2012 - 19:39 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA

04/12/2012 - 19:39 [server] Peer Connection Initiated with [AF_INET]31.193.12.74:443

04/12/2012 - 19:39 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)

04/12/2012 - 19:39 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.4.0.1,comp-lzo no,route 10.4.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.4.1.38 10.4.1.37'

04/12/2012 - 19:39 OPTIONS IMPORT: timers and/or timeouts modified

04/12/2012 - 19:39 OPTIONS IMPORT: LZO parms modified

04/12/2012 - 19:39 OPTIONS IMPORT: --ifconfig/up options modified

04/12/2012 - 19:39 OPTIONS IMPORT: route options modified

04/12/2012 - 19:39 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified

04/12/2012 - 19:39 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0

04/12/2012 - 19:39 open_tun, tt->ipv6=0

04/12/2012 - 19:39 TAP-WIN32 device [Local Area Connection 2] opened: \\.\Global\{379793C6-BEDD-4CF5-8A5B-191BD300790D}.tap

04/12/2012 - 19:39 TAP-Windows Driver Version 9.9

04/12/2012 - 19:39 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.1.38/255.255.255.252 on interface {379793C6-BEDD-4CF5-8A5B-191BD300790D} [DHCP-serv: 10.4.1.37, lease-time: 31536000]

04/12/2012 - 19:39 Successful ARP Flush on interface [16] {379793C6-BEDD-4CF5-8A5B-191BD300790D}

04/12/2012 - 19:39 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:39 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 Route: Waiting for TUN/TAP interface to come up...

04/12/2012 - 19:40 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

04/12/2012 - 19:40 C:\WINDOWS\system32\route.exe ADD 31.193.12.74 MASK 255.255.255.255 192.168.1.1

04/12/2012 - 19:40 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=10 and dwForwardType=4

04/12/2012 - 19:40 Route addition via IPAPI succeeded [adaptive]

04/12/2012 - 19:40 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.4.1.37

04/12/2012 - 19:40 Warning: route gateway is not reachable on any active network adapters: 10.4.1.37

04/12/2012 - 19:40 Route addition via IPAPI failed [adaptive]

04/12/2012 - 19:40 Route addition fallback to route.exe

04/12/2012 - 19:40 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

04/12/2012 - 19:40 OK!

04/12/2012 - 19:40 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.4.1.37

04/12/2012 - 19:40 Warning: route gateway is not reachable on any active network adapters: 10.4.1.37

04/12/2012 - 19:40 Route addition via IPAPI failed [adaptive]

04/12/2012 - 19:40 Route addition fallback to route.exe

04/12/2012 - 19:40 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

04/12/2012 - 19:40 OK!

04/12/2012 - 19:40 C:\WINDOWS\system32\route.exe ADD 10.4.0.1 MASK 255.255.255.255 10.4.1.37

04/12/2012 - 19:40 Warning: route gateway is not reachable on any active network adapters: 10.4.1.37

04/12/2012 - 19:40 Route addition via IPAPI failed [adaptive]

04/12/2012 - 19:40 Route addition fallback to route.exe

04/12/2012 - 19:40 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

04/12/2012 - 19:40 OK!

04/12/2012 - 19:40 SYSTEM ROUTING TABLE

04/12/2012 - 19:40 .1 p=0 i=12 t=4 pr=3 a=781 h=0 m=10/0/0/0/0

04/12/2012 - 19:40 37 p=0 i=12 t=4 pr=3 a=0 h=0 m=11/0/0/0/0

04/12/2012 - 19:40 10.4.1.37 p=0 i=12 t=4 pr=3 a=0 h=0 m=11/0/0/0/0

04/12/2012 - 19:40 255 192.168.1.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=10/0/0/0/0

04/12/2012 - 19:40 .0.1 p=0 i=1 t=3 pr=2 a=804 h=0 m=306/0/0/0/0

04/12/2012 - 19:40 127.0.0.1 p=0 i=1 t=3 pr=2 a=804 h=0 m=306/0/0/0/0

04/12/2012 - 19:40 55.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=804 h=0 m=306/0/0/0/0

04/12/2012 - 19:40 1.37 p=0 i=12 t=4 pr=3 a=0 h=0 m=11/0/0/0/0

04/12/2012 - 19:40 192.168.1.100 p=0 i=12 t=3 pr=2 a=781 h=0 m=266/0/0/0/0

04/12/2012 - 19:40 .255 192.168.1.100 p=0 i=12 t=3 pr=2 a=781 h=0 m=266/0/0/0/0

04/12/2012 - 19:40 .255 192.168.1.100 p=0 i=12 t=3 pr=2 a=781 h=0 m=266/0/0/0/0

04/12/2012 - 19:40 .0.1 p=0 i=1 t=3 pr=2 a=804 h=0 m=306/0/0/0/0

04/12/2012 - 19:40 68.1.100 p=0 i=12 t=3 pr=2 a=792 h=0 m=266/0/0/0/0

04/12/2012 - 19:40 55.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=804 h=0 m=306/0/0/0/0

04/12/2012 - 19:40 55.255 192.168.1.100 p=0 i=12 t=3 pr=2 a=792 h=0 m=266/0/0/0/0

04/12/2012 - 19:40 SYSTEM ADAPTER LIST

04/12/2012 - 19:40 TAP-Windows Adapter V9

04/12/2012 - 19:40 Index = 16

04/12/2012 - 19:40 CF5-8A5B-191BD300790D}

04/12/2012 - 19:40 IP = 0.0.0.0/0.0.0.0

04/12/2012 - 19:40 MAC = 00:ff:37:97:93:c6

04/12/2012 - 19:40 55.255.255

04/12/2012 - 19:40 DHCP SERV =

04/12/2012 - 19:40 ue Dec 04 19:40:24 2012

04/12/2012 - 19:40 ue Dec 04 19:40:24 2012

04/12/2012 - 19:40 DNS SERV =

04/12/2012 - 19:40 t Ethernet

04/12/2012 - 19:40 Index = 12

04/12/2012 - 19:40 73B-AC81-104A487EF5B1}

04/12/2012 - 19:40 255.255.0

04/12/2012 - 19:40 MAC = 44:1e:a1:3b:7c:b5

04/12/2012 - 19:40 55.255.255.255

04/12/2012 - 19:40 /255.255.255.255

04/12/2012 - 19:40 ue Dec 04 19:27:23 2012

04/12/2012 - 19:40 ue Dec 04 19:27:22 2012

04/12/2012 - 19:40 255.255.255.255

04/12/2012 - 19:40 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

04/12/2012 - 19:40 Starting Management Interface...

04/12/2012 - 19:40 Checking...

04/12/2012 - 19:40 Retrieve statistics...

04/12/2012 - 19:40 Connected.

[Staff 9751]

Hello!

It looks like Microsoft or the hardware vendor omitted to run by default some essential services, although we have reports that this is not the case in some Windows 8 versions. In this case, you might have a Windows 8 version which does not run (at the startup) the Netman service. Try to launch the service before launching the Air client or OpenVPN.

Please see here:

https://forums.openvpn.net/topic10013.html#p22546

Kind regards

[psikey 1]

I opened up the Network Applet as mentioned in the thread then restarted AirVPN and looks like it must have connected this time as I'm locked out of RDP again Either a hard shutdown or connect up a monitor again!

I knew I should have left Windows 7 on the server.

Any suggestions for the dropping of RDP once the OpenVPN connection is working?

[psikey 1]

Just for info, I'm using the official Window 8 Pro upgrade version. Just had to hard reset the server to get back into it.

[psikey 1]

Is the RDP problem something to do with this: https://forums.openvpn.net/topic9883.html

Redirected Gateway ?? any advise? Never had any of these issues in Windows 7 Pro.

[Staff 9751]

I opened up the Network Applet as mentioned in the thread then restarted AirVPN and looks like it must have connected this time as I'm locked out of RDP again Either a hard shutdown or connect up a monitor again!

I knew I should have left Windows 7 on the server.

Any suggestions for the dropping of RDP once the OpenVPN connection is working?

Hello!

Is the RDP listening to a port which has been remotely forwarded on our servers? This is necessary to allow incoming connections. You can then reach your remote desktop behind the VPN to :

You can also remap the remote port to a different local port for your convenience from your web control panel (menu "Member Area"->"Forwarded Ports").

Kind regards

[psikey 1]

I opened up the Network Applet as mentioned in the thread then restarted AirVPN and looks like it must have connected this time as I'm locked out of RDP again Either a hard shutdown or connect up a monitor again!

I knew I should have left Windows 7 on the server.

Any suggestions for the dropping of RDP once the OpenVPN connection is working?

Hello!

Is the RDP listening to a port which has been remotely forwarded on our servers? This is necessary to allow incoming connections. You can then reach your remote desktop behind the VPN to <Air Server exit-IP>:<forwarded port>

You can also remap the remote port to a different local port for your convenience from your web control panel (menu "Member Area"->"Forwarded Ports").

Kind regards

Only just had chance to look at this again but need some more help.

As mentioned before, I RDP to my small server either using my local IP/server name while within my LAN or using dyndns name to my static IP when away from home over the internet.

RDP is usually port 3389 by default but someone is already using that so I picked another port in the 6767 range and stated local port as 3389 on the AirVPN web config page.

Using format 192.168.1.1:6767 or SERVER:6767 in my local LAN or mydns.com:6767 or the AirVPN address 31.192.12.75:6767 doesn't get me anywhere.

I'm sure I'm missing something obvious here but what is it? I never had to do any of this with Windows 7 and could still RDP without any additional port-forwards??

[psikey 1]

No advise ??

[Staff 9751]

I opened up the Network Applet as mentioned in the thread then restarted AirVPN and looks like it must have connected this time as I'm locked out of RDP again Either a hard shutdown or connect up a monitor again!

I knew I should have left Windows 7 on the server.

Any suggestions for the dropping of RDP once the OpenVPN connection is working?

Hello!

Is the RDP listening to a port which has been remotely forwarded on our servers? This is necessary to allow incoming connections. You can then reach your remote desktop behind the VPN to :

You can also remap the remote port to a different local port for your convenience from your web control panel (menu "Member Area"->"Forwarded Ports").

Kind regards

Only just had chance to look at this again but need some more help.

As mentioned before, I RDP to my small server either using my local IP/server name while within my LAN or using dyndns name to my static IP when away from home over the internet.

RDP is usually port 3389 by default but someone is already using that so I picked another port in the 6767 range and stated local port as 3389 on the AirVPN web config page.

Using format 192.168.1.1:6767 or SERVER:6767 in my local LAN or mydns.com:6767

Hello!

That's correct: the RDP server is not listening to port 6767.

or the AirVPN address 31.192.12.75:6767 doesn't get me anywhere.

Please note that 31.192.12.75 is not an exit-IP address of any of our servers. Please determine the exit-IP address of the server your RDP server is connected to and access it (from outside the VPN) at :6767

Alternatively, you can change the listening port of your RDP server to 6767 and delete the remap to port 3389 of the remotely forwarded port 6767.

Kind regards