Remote Dekstop to Windows Server 2016 not working

Question

Remote Dekstop to Windows Server 2016 not working

Leirk Enterprise 21

Hi,

I was able to remote desktop from a different subnet to my windows server 2016 for weeks. One day I install Hikvision's app on the server and since then I've not been able to access the server. Tried a couple of things that didn't work:

checked whether I've enabled port forwarding on the cisco firewall (yes)
checked whether remote desktop is enabled on server and unchecked connection requiring NLA (yes)
checked whether the server is listening on the port (yes)
checked group settings to see whether the server allows incoming connections (yes)
checked whether 'require use of security layer' in group settings is enabled and configured for RDP (yes)
checked windows firewall to see whether the inbound port rule is correct & allowed (yes)
checked whether the particular port is configured in the registry ,since I'm not using 3389 (yes)

I'm now stuck. Anyone with any ideas what the issue could be?

Leirk Enterprise 21 Reputation points

2021-09-15T07:56:33.087+00:00

when I used the troubleshooting toll on the windows server, it gave me the following msg

"The IPsec security policies of the two computers don't match. This is preventing the connection.
Contact your network administrator Completed

Your computer's security policy doesn't match the policy on the computer you're trying to reach. The security policy settings need to be modified."

Anyone know how to resolve this between a Windows 10 Client and Windows 2016 server?

Accepted answer

8 additional answers

Your answer

Leirk Enterprise 21 Reputation points

2021-09-15T07:56:33.087+00:00

when I used the troubleshooting toll on the windows server, it gave me the following msg

"The IPsec security policies of the two computers don't match. This is preventing the connection.
Contact your network administrator Completed

Your computer's security policy doesn't match the policy on the computer you're trying to reach. The security policy settings need to be modified."

Anyone know how to resolve this between a Windows 10 Client and Windows 2016 server?

Answer 1

Anonymous

Might try from PowerShell from source and target (use target ip address in both cases).

Test-NetConnection -ComputerName "192.168.49.142" -CommonTCPPort "RDP" -InformationLevel "Detailed"

--please don't forget to upvote and Accept as answer if the reply is helpful--

Anonymous

2021-09-14T12:59:18.637+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--
Leirk Enterprise 21 Reputation points

2021-09-15T07:36:54.077+00:00

will this work from another subnet? also, I changed the port from standard 3389 to another port
Anonymous

2021-09-15T13:08:37.53+00:00

Then do;
Test-NetConnection -ComputerName "192.168.49.66" -Port "999" -InformationLevel "Detailed"
Anonymous

2021-09-15T14:40:19.597+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--
Leirk Enterprise 21 Reputation points

2021-09-15T14:58:36.477+00:00

ComputerName : XXX.XXX.XXX.XX
RemoteAddress : XXX.XXX.XXX.XX
RemotePort : 5137
NameResolutionResults : XXX.XXX.XXX.XX
MatchingIPsecRules :
NetworkIsolationContext : Internet
InterfaceAlias : Wireless Network Connection
SourceAddress : 192.168.100.20
NetRoute (NextHop) : 192.168.100.1
PingSucceeded : True
PingReplyDetails (RTT) : 24 ms
TcpTestSucceeded : False

Could it be that this command line tries to attempt a connection to TCP 5137 and what is open on the firewall is UDP 5137?
Anonymous

2021-09-15T15:01:47.357+00:00

Please post unedited results from both source and target
Leirk Enterprise 21 Reputation points

2021-09-15T15:13:09.403+00:00

ComputerName : XXX.XXX.XXX.XX
RemoteAddress : XXX.XXX.XXX.XX
RemotePort : 5137
NameResolutionResults : XXX.XXX.XXX.XX
MatchingIPsecRules :
NetworkIsolationContext : Internet
InterfaceAlias : Wireless Network Connection
SourceAddress : 192.168.100.20
NetRoute (NextHop) : 192.168.100.1
PingSucceeded : True
PingReplyDetails (RTT) : 24 ms
TcpTestSucceeded : False

could it be that since this command attempts to establish a TCP connection, it won't work cause the open port on the firewall is a UDP port?
Charles Thivierge 4,171 Reputation points

2021-09-15T15:13:26.777+00:00

Rdp need tcp connection and optionally udp connection
Anonymous

2021-09-15T15:15:42.153+00:00

Yes, you'll need to allow TCP connection on the given port.

--please don't forget to upvote and Accept as answer if the reply is helpful--
Leirk Enterprise 21 Reputation points

2021-09-15T15:19:13.01+00:00

I have to edit out the public ip of the target for security reasons

the command results from the target server are below:

ComputerName : 192.168.2.20
RemoteAddress : 192.168.2.20
RemotePort : 5137
NameResolutionResults : 192.168.2.20
MatchingIPsecRules :
NetworkIsolationContext : Private Network
InterfaceAlias : Ethernet
SourceAddress : 192.168.2.20
NetRoute (NextHop) : 0.0.0.0
TcpTestSucceeded : True
Anonymous

2021-09-15T15:21:48.883+00:00

Looks like TCP 5137 is being blocked.

--please don't forget to upvote and Accept as answer if the reply is helpful--
Anonymous

2021-09-15T15:27:23.023+00:00

These are the two defaults created when you allow remote RDP connection. I'd check that you have added two news ones both set to 5137

--please don't forget to upvote and Accept as answer if the reply is helpful--
Charles Thivierge 4,171 Reputation points

2021-09-15T15:36:43.033+00:00

From what i can see, it seems that the port is open on the server itself

It could be a firewall issue between the 2 sites...
Leirk Enterprise 21 Reputation points

2021-09-15T15:38:20.72+00:00

since you can't edit the default rule by changing the port numbers, I created my own rules for both TCP & UDP 5137 to allow connections.

I'll open TCP port 5137 on the firewall to see whether it'll change anything. I had already opened UDP 5137 on the firewall and it had been working fine
Anonymous

2021-09-15T15:39:24.757+00:00

Sounds good.
Anonymous

2021-09-15T19:41:45.533+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--
Leirk Enterprise 21 Reputation points

2021-09-16T10:53:43.803+00:00

you were right. I opened TCP port 5137 and it now works perfectly. Thank you
Anonymous

2021-09-16T12:45:28.35+00:00

Glad to hear, you're welcome.

Answer 2

Limitless Technology 39,926

Hello,

Thank you for your question.

I would like to suggest you to check below Troubleshooting steps.

Please try to ping the server
Disable Firewall on Client computer and on the Server for temporary.
Disable Antivirus on Client computer and on the server for temporary.
Please check date and time are synced
Download PortQry from below Microsoft site to see if the port open and reachable from client computer
https://www.microsoft.com/en-in/download/details.aspx?id=24009

Hope this helps,
Thank you,

Leirk Enterprise 21 Reputation points

2021-09-15T07:51:55.38+00:00

I've tried to disable the windows firewall on both client and server as well as sync the time, but RDP still doesn't work.

Thanks for the tool, it returns the following query

UDP port 5137 (unknown service): LISTENING or FILTERED
portqry.exe -n xxx.xxx.xxx.xx -e 5137 -p UDP exits with return code 0x00000002.
Limitless Technology 39,926 Reputation points

2021-09-15T19:38:34.677+00:00

Hello,

Please chech what port is used by Hikvision application , it may be the port conflict and used by this application.

Try stop Hikvision services and see if you are able to access RDP. If yes then you may need configure this application port to other port.

Hope this helps.
Limitless Technology 39,926 Reputation points

2021-09-16T13:39:26.933+00:00

Hello @Leirk Enterprise

If uninstalling or stopping Hikvision software fixes the issue, most likely the problem is the conflict of network usage, and you may want to get more information from the manufacturer about the coexistance with other services like RDP.

Does any difference if you access from the same subnet?

On the other hand, to remove this problem (also for enhanced port security) you can configure a port redirection in your router for RDP incoming connections to the server meaning that you can assign a new "public" port, that gets redirected to the 3389 (RDP) internally. the only difference would be that currently your machines will be connecting with xxx.xxx.xxx.xxx as destination and then will need to connect with xxx.xxx.xxx.xxx:<publicporttoredirect>

Hope this helps in your case,
Best regards,

Answer 3

Charles Thivierge 4,171

What is the particular RDP port you are using ?

Is it possible it has an issue with one of the port the application is using ?

hth

Leirk Enterprise 21 Reputation points

2021-09-15T07:53:09.023+00:00

UDP 5137

It could be, but it worked fine for weeks so I don't understand why the port would suddenly have an issue

Answer 4

Charles Thivierge 4,171

If you open a cmd with admin rights on the Windows 2016 server, run this command

Netstat -anob > c:\temp\portlist.txt

Then look for the RDP port and look for the process that is associated with the port

Leirk Enterprise 21 Reputation points

2021-09-15T10:52:03.45+00:00

UDP [::]:5137 : 368
TermService
[svchost.exe]

it shows the RDP process 'termservice'
Charles Thivierge 4,171 Reputation points

2021-09-15T11:04:08.887+00:00

So TCP 5137 and UDP 5137 are configured on the port 5137 and it's Termservice the associated process...

If you run the command line:
Test-NetConnection -ComputerName "192.168.49.142" -Port 5137 -InformationLevel "Detailed"

Everything is working?
Leirk Enterprise 21 Reputation points

2021-09-15T11:18:49.407+00:00

ComputerName : 192.168.2.20
RemoteAddress : 192.168.2.20
RemotePort : 5137
NameResolutionResults : 192.168.2.20
MatchingIPsecRules :
NetworkIsolationContext : Private Network
InterfaceAlias : Ethernet
SourceAddress : 192.168.2.20
NetRoute (NextHop) : 0.0.0.0
TcpTestSucceeded : True

Answer 5

Charles Thivierge 4,171

Does it try to negotiate a connection?
Can you see... "Securing remore connection" or "Configure remore session" or there is nothing

Leirk Enterprise 21 Reputation points

2021-09-15T11:38:58.11+00:00

The remote desktop app from my client (different LAN) just says "Initiating remote connection"...then fails (see attached image)

I hope that's what you're asking?

Share via

Remote Dekstop to Windows Server 2016 not working

8 additional answers

Your answer