Hello,
I am trying connect to Microtik hap ac3 by Orange Slovakia. They used limited webadmin access
I have Remote VPN enabled and configured, PSK generated, user defined.
But when trying connect from Windows 10 obtain this message:
The remote connection was not made because the name of the remote access server did not resolve
What you masked in Connect To field looks like numeric address, so if that’s the case, the message is weird, because there’s nothing to resolve.
Hi Sob,
thanks you for reply, but I am little confused. Problem is masked IP? This is public static IP address of my client and I masked it because security. Or problem is IP address instead of name? This IP and port value was automatically entered by system.
What is wrong on my question? Plz explain me more
That means if you are using the IP then there is no name resolving possess will be involved. ( windows Client error )
Maybe “event viewer” can tell us the tail of the error. 
?
OK,
I am understand, but how can I solve this? IP address and port was entered automatically by ORANGE config system and is not possible change it, is grayied an unmodificable. How can I connect to VPN by IP?
Note: The same error was happend on 3 different machines and 2 OS (Win10 and Win7) on two different LAN/WAN… thus this is not OS related issue, but Microtik config issue, I think…
Can you ping that public IP address ?
Also, when connected to hap ac3 network from a PC, if you do tracert to e.g. 8.8.8.8, does that same IP address show up ?
Can you please also provide a network diagram of the network which contains hap ac3 ?
And you are 200% sure the port required to reach your hap is being forwarded by the modem from Orange ? How do you know ?
if Mikrotik config issue, please post full config:
export hide-sensitive file-anynameyouwish
Check the file for secret/public info, change it and then post contents of that file between Code quotes.
See it looks like IP even with a masked pattern.
This is vissible public static IP address of my client and port was entered automatically by Microtic Orange autoconfig I think
Yes, So what did you set in the L2TP out in the Windows client?
remove “:1701” from the client try if it can resolve it.
what is that you masked again in connect to. is it a name like google.com or is the public IP the same as your B2B portal?
strange, then connecting longer and result is another
This is better than the first error.
can you check any log in the Mikrotik or in the Windows Client? at least it did find the server.
I’m not sure, but this second error may be how Microsoft broke L2TP/IPsec with january updates. They already released a fix, but I don’t know if it’s installed automatically.
CoId={MAC}: The user HP-** dialed a connection named test which has failed. The error code returned on failure is 789.
CoId={MAC}: The user HP-** has started dialing a VPN connection using a per-user connection profile named test. The connection settings are:
Dial-in User = *********
VpnStrategy = L2TP
DataEncryption = Requested
PrerequisiteEntry =
AutoLogon = No
UseRasCredentials = Yes
Authentication Type = MS-CHAPv2
Ipv4DefaultGateway = Yes
Ipv4AddressAssignment = By Server
Ipv4DNSServerAssignment = By Server
Ipv6DefaultGateway = Yes
Ipv6AddressAssignment = By Server
Ipv6DNSServerAssignment = By Server
IpDnsFlags =
IpNBTEnabled = Yes
UseFlags = Private Connection
ConnectOnWinlogon = No
IPsec authentication for L2TP = Pre-shared key.
I have no installed this KB kb:5009543 for Windows 10
Can I use another, NON MS VPN client? which you suggest?
https://www.draytek.com/products/smart-vpn-client/
This might be as @Sob mentions, and Auto-update in my Windows 10 21H2 did fix the issue. check this with this connection or any none Microsoft devices.
the log you did provide is general and I can’t narrow it down.
However, take look at this but before you do any change please make sure this is related to your issue.
https://windowsreport.com/vpn-error-789/#:~:text=Why%20does%20VPN%20error%20789,Windows%2010%20in%20this%20case.
Another possibility is that it’s this long known problem:
In short, Windows don’t like servers with IPSec behind NAT. It’s not clear whether your router has that public address directly, or if it’s NAT 1:1. If it is, then the linked article describes how to change client config to work with it.