[b]Problem symptoms[/b] * your server's TAP NIC gets an APIPA IP address (196.254.x.x) * your client appears to connect just fine and even gets an IP assigned * your client cannot ping/reach the server through the IP that was set in the config (well duh since the TAP NIC has an APIPA IP address) 1) Open '[b]Windows Firewall with Advanced Security[/b]' 2) The root node should be named 'Windows Firewall with Advanced Security on Local Computer'. Right click it and hit Properties. 3) In the Properties window stay on the first tab: [b]Domain Profile[/b]. There is a group-box labeled 'State'. Look for 'Protected network connections' and a [b][Customize..][/b] button next to it. [b]If the button is disabled I will explain below how to enable it[/b]. Click the [Customize..] button. 4) A window will open with 'Network connections'. You will see your network adapters listed. Uncheck the one that is your TAP-Windows Adapter V9 (mine is called VPN-TAP). 5) Restart OpenVPN and check to see if IP is now being set correctly. [b]When the [Customize..] button is disabled...[/b] I had this issue on a VPS server where the OS installation was performed by the provider. I manage other VPS servers (also Windows Server 2008 R2) and I do not have this problem there. I am not sure why this happens but the provider tells me they just did a default installation. Solution: 1) Open your Local Security Policy (Editor) 2) Open the 'Windows Firewall with Advanced Security' node 3) Another node should be under it named: 'Windows Firewall with Advanced Security - Local Group Policy Object' Right click it and hit Properties 4) You will see the same tabs as before, stay on Domain Profile. In the State group-box change the Firewall state from 'On (recommended)' to 'Not configured'. 5) Hit apply/ok and retry the steps above. The [Customize..] button should now be enabled. This thing caused me quite a headache and I hope this will help someone else. Another important note: I had to follow the first steps above myself again recently (unchecking the TAP-Windows Adapter). Something reset the firewall settings, don't know what.

Some pictures for your convenience. For the first part/steps: [img]http://s12.postimg.org/vhdqv0ne5/windows_firewall.png[/img] [img]http://s12.postimg.org/ya6yf1nql/firewall_network_connections.png[/img] For the second part (enabling the [Customize..] button): [img]http://s12.postimg.org/h0v2u6nal/local_security_policy.png[/img] [img]http://s12.postimg.org/vvf2um7hp/local_group_policy_object_editor_firewall_domain.png[/img]

Server 2008 R2 - IP not getting assigned [solution!]

dixon

Problem symptoms

* your server's TAP NIC gets an APIPA IP address (196.254.x.x)
* your client appears to connect just fine and even gets an IP assigned
* your client cannot ping/reach the server through the IP that was set in the config (well duh since the TAP NIC has an APIPA IP address)

1) Open 'Windows Firewall with Advanced Security'

2) The root node should be named 'Windows Firewall with Advanced Security on Local Computer'. Right click it and hit Properties.

3) In the Properties window stay on the first tab: Domain Profile. There is a group-box labeled 'State'. Look for 'Protected network connections' and a [Customize..] button next to it. If the button is disabled I will explain below how to enable it. Click the [Customize..] button.

4) A window will open with 'Network connections'. You will see your network adapters listed. Uncheck the one that is your TAP-Windows Adapter V9 (mine is called VPN-TAP).

5) Restart OpenVPN and check to see if IP is now being set correctly.

When the [Customize..] button is disabled...

I had this issue on a VPS server where the OS installation was performed by the provider. I manage other VPS servers (also Windows Server 2008 R2) and I do not have this problem there. I am not sure why this happens but the provider tells me they just did a default installation.

Solution:

1) Open your Local Security Policy (Editor)
2) Open the 'Windows Firewall with Advanced Security' node
3) Another node should be under it named:
'Windows Firewall with Advanced Security - Local Group Policy Object'
Right click it and hit Properties
4) You will see the same tabs as before, stay on Domain Profile. In the State group-box change the Firewall state from 'On (recommended)' to 'Not configured'.
5) Hit apply/ok and retry the steps above. The [Customize..] button should now be enabled.

This thing caused me quite a headache and I hope this will help someone else.

Another important note: I had to follow the first steps above myself again recently (unchecking the TAP-Windows Adapter). Something reset the firewall settings, don't know what.

dixon

Some pictures for your convenience.

For the first part/steps:

For the second part (enabling the [Customize..] button):