RRAS in Windows Server 2025 with issues

Question

Hello,

It seems RRAS is not working properly.

I need to build a VPN Site-to-Site connection to Azure, and using the Desktop Experience, raises the error below.

"A phonebook entry cannot be added: The binding handle is invalid"

The lab I'm trying to create is a server with 2 NICs that are connected each one on each LAN so the internal LAN can connect to Azure via IPSec.

Since I got this Error, I built a configuration script to be used in Server Core installation of Windows Server 2025 by using PowerShell.

When I try to connect the Dial-Up connection using the Connect-VpnS2SInterface cmdlet, it raises another error: Element not found.

I piped the objects using the following cmdlet, and the Dial-Up interface object is there.

Get-VpnS2SInterface | Connect-VpnS2SInterface

In summary

Can't create a Dial-Up connection using Desktop Experience, and but on Server Core, I can configure everything, but I do not have success on connect. It seems the Dial-up interface is broken.

On Windows Server 2022, it works as expected.

Anyone aware of this?

Answer 1

You're right.

However, you can directly add server "localhost" to the console, so the Demand-Dial wizard opens after Right clicking inside Network Interfaces and clicking on the context menu "New Demand-dial interface". Looks like this is an issue related to the hostname of the RRAS server after installing the feature. Thanks for your reply it helped a lot.

The error "Element not found" was happening because I set the VPN S2S interface with a DNS name that wasn't reachable.

Answer 2

UGH!~ Just spont about 6 hours troubleshooting this issue. Same errors for me.

Back to 2022.. I'll let you know if it goes smoothly in a bit.