Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

Nothing listening on ports 500 or 4500 after setting up RRAS for IKEv2

$
0
0

Hi All,

Been through weeks of setting up and re-setting up RRAS service, finally with help on another post got the service up and running on a guest VM.  I am running Server 2019 and am splitting my services between multiple guest Hyper-V VMs to set up an instance of always on VPN.  I've followed multiple different tutorials for this purpose that have me set up a CA, NPS, and an RRAS instance to authenticate a VPN connection using IKEv2 (not sure if I've got all of that worded correctly... I'm tryin' hard!) and they all create the same end result.

As of now, when I attempt to connect from a client machine to the VPN I get an error that starts out with "The network connection between your computer and the VPN server could not be established because the remote server is not responding...".  This message continues to suggest there could be issues with a device between the internet and my RRAS server.  I think, however, the problem is with the RRAS service itself.  I've set this up according to templates (like the one provided) which I believe rely on IKEv2). I'm thinking based on what I've been reading that these services should listen on ports 500 and 4500.  I've set up port forwarding in my router to this machine for those ports.  I can confirm port forwarding works in general... I can forward port 53 to my machine running my DNS without issue. But, confirming the error message, ports 500 and 4500 remain "closed". The cause for "closed" status seems to be on the server itself.  When I run netstat -a in an elevated command prompt, there are no services listed as listening on those ports... and RRAS is running and set up in the default configuration.

Appreciate any guidance.  Thanks!


Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>