I hope that someone wiser than I will read through this post, and the symptoms and see the solution shining through. So far, it has eluded me, and my staff. Based on reading many of the VPN related posts and answer threads, I suspect that many of the other forum users who are experiencing troubles are seeing a subset (or the the full range) of issues reported in this post. Environment: Windows Server 2008r2 running on Hyper-v - with RRAS setup. Not using NAP (yet). Users setup in AD Group for VPN Access Windows 7 Professional SP1 on a number of HP ProBook (64Something) Laptops - The point here is multiple HW sets and drivers (all updated). IKEv2 VPN Reconnect installed and configured on our mobile workgroup's laptops. IKEv2 VPN is setup to use Machine Certificate Authentication, Mobility Setting can be on or off - doesn't change the symptoms. Symptoms: On 60% of our worker's laptops (see above) users experience the following syndrome: - Work all day <inside> the enterprise network - docked, wired and connected to all resources. - Go home and connect to VPN thus: Boot Laptop Login using cached credentials Connect to internet (can be wired or wireless - matters not) Connect to VPN (usually succesfully) - Outlook works and connects to server just fine... After a short (anywhere from 6 -8 minutes) time, Outlook will show "trying to connect" Internet (web access through tunnel) access fails, and mapped drives cannot be accessed. Disconnecting and reconnecting the VPN Adapter will restore services. Shut down, go watch a move or have dinner or something, come back and try to connect to VPN - Error 809 (Remote Server Not Responding) Wireshark trace shows connection attempt, and then you can watch NAT Keepalive packets being thrown at the laptop from the VPN Server for about an hour before it gives up. - Go back to the office, connect the laptop, logiin, work, all is well. Go home later and try VPN, and sometimes, it works, others not. Some of our users seem to be working just fine, all the time. Others have varying degrees of the syndrome described above - work great for a week or two, and then fall into the VPN no-work syndrome. We keep looking for a common denominator, and it eludes us. The intermittent nature is bothersome also. I have worked with 2 different router/gateways at my house on this issue (Linksys BEFSX41 and A Trendnet BRV204 with the same results) Other users are using the Apple Airport Express with one user never having trouble, and another user having intermittent trouble with the syndrome described above. Any ideas out there?

Hi, The error 809 indicates the network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g, firewalls, NAT, routers, etc) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem. This error usually comes when some firewall between client and server is blocking the ports used by VPN tunnel. L2TP or IKEv2 port (UDP port 500, UDP port 4500) is blocked by a firewall/router. [Applicable to tunnel type = L2TP or IKEv2] Enable the port (as mentioned above) on firewall/router. Disable the security software temporarily. If that is not possible, deploy SSTP based VPN tunnel on both VPN server and VPN client – that allows VPN connection across firewalls, web proxies and NAT. In addition, the issue is related to Server, I suggest contacting Server Forum if the issue persists. Win Server Forum http://social.technet.microsoft.com/Forums/en-US/category/windowsserver Best Regards, NikiPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks Niki: The 809 is an intermittent occurrence. Usually, a user can connect fine initially, but at some point, for example, a few hours later, they log back in and try to reconnect again, and they receive the 809... where a few hours earlier from the same connection, all was well. Ports 500 and 4500 are enabled on our firewall (Checkpoint UTM-1) to allow NAT-Passthrough. The home routers we are using are varied, and all have NAT Passthru and VPN passthru setttings enabled. We have disabled security software and windows firewall on the client computers when testing. The results are the same. We are leaning towards this being some kind of configuration issue on the client (Windows 7 ) computers as opposed to the server since we have some users who connect trouble-free all the time. Paul