Forum Discussion
RDP connection through VPN only to RAS IP not to main IP
Agreed on routing issues. Dual gateways would likely be problematic. I'd hope by "DC-02" you didn't mean a domain controller. Multi-homing a domain controller will always cause no end to grief. If so I'd recommend installing the RASS / VPN roles on a member server.
W-05 is a developer computer with visual studio. Hyper-V role is installed.
The problem occurs on all computers connecting to DC-02 via VPN. Computers in the LAN of DC-02 don‘t have any problems.
Ok, gotcha. I'd still try from PowerShell
Test-NetConnection -ComputerName "xxx.xxx.xxx.xxx" -CommonTCPPort "RDP" -InformationLevel "Detailed"
From both source (pc you're connecting from) and also on target (pc you're connecting to) If it fails on source and succeeds on target then there appears to either be a firewall issue or possibly a routing issue.
and as mentioned the dual gateways could be problematic so might also try to VPN from a desktop without either Hyper-V or the dual gateways.
Great news, and you're welcome.
I moved the Routing and RAS role from the DC to the member server. Now everything is ok.
Thanks a lot.
Sounds good, you're welcome.
- Yes it is a domain controller. I will try tomorrow to move the RAS to a member server
I“ll keep you informed.
Thanks for the moment. Agreed on routing issues. Dual gateways would likely be problematic. I'd hope by "DC-02" you didn't mean a domain controller. Multi-homing a domain controller will always cause no end to grief. If so I'd recommend installing the RASS / VPN roles on a member server.
- I tried it from a different laptop. As for W-05 I tried and it failed and for DC-02 it succeeded..
I think it“s a routing problem. I can RDP several server and workstations in the DC-02 LAN through the VPN connection even DC-02 when I use the IP of the RAS-dialin interface (which can change). Just when I use the IP of the LAN interface of DC-02 it fails. Same on DNS requests.
I turned of the firewall and Kaspersky on DC-02.