Mục lục bài viết
Update: 2022-02-25 04:39:06,Quý khách Cần tương hỗ về Cannot connect to Windows Server 2019 Remote Desktop. Bạn trọn vẹn có thể lại Báo lỗi ở cuối bài để Admin đc lý giải rõ ràng hơn.
Tóm lược đại ý quan trọng trong bài
· · ·
Pure Capsaicin
OP
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Nov 6, 2020 at 13:54 UTC
102 Best Answers
339 Helpful Votes
For some reason, this just isn’t working. I had no issues with the previous deployment, so I feel that there must be some special consideration or something when using a virtual machine?
Nope. A VM isn’t any different once it’s up and running. You turn it on via hyper-v instead of a power button, sure, but otherwise? It’s just Windows Server.
for the licensing role, which the server the hyper-v virtual machine is installed on is hosting.
You realize this uses up one of your OSE licenses, right? With a 2019 Standard license you only get 2 OSEs and you’ve used one on the hypervisor and one on RDS, so your license won’t allow for any other VMs. Generally speaking it’s best to not run any other roles on the hypervisor itself, leaving that second OSE license to be used on another Server VM.
1
· · ·
Pure Capsaicin
OP
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Nov 6, 2020 at 13:55 UTC
102 Best Answers
339 Helpful Votes
When I try to remote desktop in, I get nowhere. Nothing, nada. It attempts, and then just says cannot fine the remote computer. I am able to ping the ip it points to, and traceroute completes just fine.
Did you try to RDP via IP? Did you make sure to enable RDP access to the Server itself? Did you try turning the Server firewall off, to see if something is set wrong there?
1
· · ·
Mace
OP
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Nov 6, 2020 at 14:10 UTC
50 Best Answers
207 Helpful Votes
Can you access it from a device internal to your network? Can you access it via IP address as suggested? If you telnet to port 3389 from an internal machine, do you get an answer?
1
· · ·
Sonora
OP
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Nov 6, 2020 at 15:12 UTC
Unfortunately I am dealing with budget constraints and limited equipment, so I’m not too worried about the licensing, though I do appreciate the advice. To answer the questions poised so far:
I have tried RDP via both IP and fqdn, neither one work. I should add, when remoting in internally or over VPN, I have no issues. It’s just when attempting to remote in over the WAN that there is an issue. Sorry if I didn’t make that clear in the original post. Firewalls are off temporarily while troubleshooting, so there isn’t a concern there.
0
· · ·
Mace
OP
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Nov 6, 2020 at 15:25 UTC
50 Best Answers
207 Helpful Votes
Are you using RDGateway? If so, do you have port 443 forwarded through your firewall to your server?
If not using RDGateway how are you connecting? Please don’t say you have RDP open to the web.
2
· · ·
Pure Capsaicin
OP
Best Answer
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Nov 6, 2020 at 15:31 UTC
102 Best Answers
339 Helpful Votes
I have tried RDP via both IP and fqdn, neither one work. I should add, when remoting in internally or over VPN, I have no issues. It’s just when attempting to remote in over the WAN that there is an issue. Sorry if I didn’t make that clear in the original post.
Ah, this makes a huge difference.
This would indicate an issue with your firewall / router not properly directing traffic to the RDS Server.
0
· · ·
Sonora
OP
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Nov 6, 2020 at 15:32 UTC
I am using rdgateway, it is installed on the vm as one of the roles. I do not have terminal services open from the WAN , it has only been allowed for a select few addresses. In testing this, I have added my home IP as an allowed IP, but it won’t connect over the WAN (it also won’t connect from any of the other allowed IPs). 443 should also be allowed through to the rdgateway. I will double check that right now, though,
0
· · ·
Mace
OP
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Nov 6, 2020 at 15:34 UTC
50 Best Answers
207 Helpful Votes
If everything works internally and works remotely via VPN, your issue most likely is with your perimeter firewall.
1
· · ·
Sonora
OP
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Nov 6, 2020 at 16:25 UTC
Well, I didn’t want to believe it, but I went back and combed over the firewall and that was absolutely the issue. I had looked at it a dozen times before and didn’t see the mistake I had made, but now that I have corrected it it is allowing access from my specified IPs. We use a mixture of NAT and access rules and on one of them I had fat fingered and reversed the source/destination. I was so set on the issue being with the fact that I had deployed this one as a VM compared to the previous one being physical that I was stuck on that being the issue.
Thanks all!
1
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please
ask a new question.
Yes
No
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Thank you.
Use these steps when a Remote Desktop client can’t connect to a remote desktop but doesn’t provide messages or other symptoms that would help identify the cause.
Hey there,
I have users RDPing to a Windows 2019 Server.
Users are complaining that they cannot reconnect (by clicking on the X to close out the RDP session) and have their programs still running.
I know Windows 2019 is still pretty new, but I’ve been trying to find answers and haven’t been able to solve this.
Do any of you know about specific RDP settings/configurations that should be enabled or disabled for this?
I’m at a loss.
Thanks y’all
remote-desktop-servicesremote-desktop-client
Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
▼
Toggle Comment visibility. Current Visibility: Visible to all users
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.
JiaYou-MSFT answered • Aug 24, ’20 | JiaYou-MSFT commented • Sep 7, ’20
HI
Usually RD Connection Broker will reconnect the user to the correct RD Session Host server and their interrupted session.
1. Could you please provide more details about your RDS environment?
1) which rds server role have you built？
2) How many Session Hosts and are they in the same collection ?
3) How many collections have you created in the Connection Broker？
2. Does this issue happen only to one collection or all the collections?
3. Have you tried query session command, is there a different session ID when you reconnect?
4. Is there any sự kiện logs that has captured some details regarding this issue? Enable the Analytic and Debug logs Event Viewer first.
Check on CB server:
Applications and Services Logs-> Microsoft-> Windows-> TerminalServices->SessionBroker
Check on SH server:
Applications and Services Logs -> Microsoft -> Windows -> TerminalServices->LocalSessionManage
RDS server roles:
docs.microsoft/en-us/windows-server/remote/remote-desktop-services/rds-roles
RDP sự kiện logs:
woshub/rdp-connection-logs-forensics-windows/
Reference document/link:
docs.microsoft/en-us/windows-server/administration/windows-commands/query-session
docs.microsoft/en-us/windows-server/remote/remote-desktop-services/rds-roles
woshub/rdp-connection-logs-forensics-windows/
Comment
Comment · Show 2
Comment
5 |1600 characters needed characters left characters exceeded
▼
Toggle Comment visibility. Current Visibility: Visible to all users
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.
MarcoCruz5-8693 · Aug 26, 2020 at 04:16 PM
Hey @JiaYou-MSFT ,
Thank you for getting back to me.
To clarify: This is one remote host that is running Windows 2019 Server. Multiple users are RDPing into it.
I’m not seeing anything weird in the Window Event Viewer Logs under Windows -> System, Application, and Security.
Currently, the workaround for this has been to set an idle timeout time to 1 minute. This is so that if the users close the session, the session will close out in a minute, and they are able to log back in. Of course, this is a brand new session and none of their applications are running. That is expected.
However, I am looking to disable idle timeout and see if I could have the users return to their previous session?
Unsure if this is even possible in WIndows 2019 Server.
Thank you again
0 Votes 0 ·
JiaYou-MSFT MarcoCruz5-8693 · Sep 07, 2020 at 01:57 AM
HI
Is there any progress on your question?
0 Votes 0 ·
JiaYou-MSFT answered • Aug 27, ’20 | JiaYou-MSFT edited • Aug 27, ’20
HI
1.can you enter below powershell command on issue w2019 server then look if we installed “remote desktop session host” role ?can you also check if you install remote desktop licensing and remote desktop connection broker in this issue w2019 or other thành viên server by using below ps command ?
Get-WindowsFeature | where name -Like “rds*”
2.in general,if we not install “remote desktop session host” role on w2019,there will be only 2 concurrent active session for 2 users.so if we want to more than 2 users remote access w2019 concurrently ,we must install “remote desktop session host” role and we also need to install RD licensing role then enroll the RDS cals on RD licensing server. in past, I saw some IT friends didn’t install “remote desktop session host “role and “fsinglesessionperuser” registry key to 0 then cause end users can not reconnect to exist session.
can you check the value for “fsinglesessionperuser” registry key on your issue is 1?by default it should be 1.
HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindows NTTerminal Services
“fsinglesessionperuser”=dword:00000001
HKEY_LOCAL_MACHINESoftwareWOW6432notepoliciesMicrosoftWindows NTTerminal Services
“fsinglesessionperuser”=dword:00000001
we can enter gpedit.msc in command prompt on issue w2019session host server.
Go to Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostConnections.
Set Restrict Remote Desktop Services user to a single Remote Desktop Services session to Enabled.
Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
▼
Toggle Comment visibility. Current Visibility: Visible to all users
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.
Janne Ruostemaa
staff
Troubleshooting Updated on 2021-03-30 72
If you have problems using Remote Desktop (RDP) with your Windows server, there are a couple of things you can fix. This troubleshooting guide aims to help rule out some of the most common causes for poor functionality.
Try UpCloud for không lấy phí! Deploy a server in just 45 seconds
Let’s try to figure out how to fix an RDP connection error This computer can’t connect to the remote computer. It occurs when you try to connect to a remote computer or Remote Desktop Server (RDS) using the built-in Windows RDP client (mstsc.exe).
The problem looks like this: when you try to connect to a remote Windows server/desktop via RDP, the mstsc.exe client freezes for a minute, and a window with the following RDP error appears:
Remote Desktop Connection
This computer can’t connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
First of all, check if the remote computer is accessible from your device over the network, and the default Remote Desktop port (TCP 3389) is responding (and not blocked by firewalls).
Make sure the DNS address of the remote RDP host is correctly resolved from your computer. Use the following commands:
nslookup rdp_server_name1
ping rdp_server_name1
If the DNS name is not resolved properly, check your DNS settings or try connecting to a remote host using an IP address.
You can check the RDP port availability on a remote server from a client workstation using:
The Telnet client:
telnet rdp_server_name1 3389
PowerShell 4.0 and higher:
Test-NetConnection rdp_server_name1 -Port 3389 -InformationLevel Quiet
Note. If this command returned True, then the RDP port responds on the server and it’s not blocked.
PowerShell all versions:
New-Object System.Net.Sockets.TcpClient).Connect(‘rdp_server_name1’, 3389)
If port 3389 is unavailable, you should check if the Remote Connection is enabled on the remote server (right-click on Start button > Settings > System > Remote Desktop > Enable Remote Desktop).
You can remotely enable Remote Desktop on a Windows computer by changing the fDenyTSConnectionsregistry.
Every admin should be familiar with this RDP error. The most common cause of a failing RDP connection concerns network connectivity issues, for instance, if a firewall is blocking access.
You can use ping, a Telnet client, and PsPing from your local machine to check the connectivity to the remote computer. Keep in mind ping won’t work if ICMP is blocked on your network. The main advantage of Telnet and PsPing is that you can connect via TCP, and you can check whether the RDP port 3389 is open.
The Telnet client isn’t enabled by default. Use this command to enable Telnet from a command prompt:
dism /trực tuyến /Enable-Feature /FeatureName:TelnetClient
And use this one from a PowerShell console:
Install-WindowsFeature -name Telnet-Client
Use PsPing if you have problems enabling the Telnet client. PsPing also lets you test the connectivity to a specific TCP port. It is portable, so no installation is required.
First, try to ping the remote computer’s hostname or IP address.
The remote machine connection timed out with PsPing
As you can see in the screenshot above, I was unable to ping the remote machine, and the port was not reachable as well.
If this works, and you are unable to ping the machine using the FQDN name, check whether DNS resolution is working properly. Sometimes the hostnameis pointingto another machine on DNS that is either offline or not in use.
If you can’t connect at all, a local firewall (Windows Firewall or third-party security software) or a network firewall might be blocking the port. The PowerShell command below lets you display the Windows Firewall state on the remote machine.
Invoke-Command -ComputerName [ComputerName] -ScriptBlock netsh advfirewall show allprofiles
Remote computer firewall status
For testing purposes, you can disable Windows Firewall on the remote computer with this command:
Invoke-Command -ComputerName Win7 -ScriptBlock netsh advfirewall set allprofiles state off
Note that you should enable PSRemoting on the remote computer to execute the above command. If not, you can use PsExec to enable PowerShell remoting with the command below:
psexec \RemoteComputer -u administrator -p. PASSWORD netsh advfirewall set allprofiles state off
Reply
3
0
Chia sẻ
– Một số từ khóa tìm kiếm nhiều : ” đoạn Clip hướng dẫn Cannot connect to Windows Server 2019 Remote Desktop tiên tiến và phát triển nhất , Chia Sẻ Link Tải Cannot connect to Windows Server 2019 Remote Desktop “.
Quý khách trọn vẹn có thể để lại Comments nếu gặp yếu tố chưa hiểu nha.
#connect #Windows #Server #Remote #Desktop Cannot connect to Windows Server 2019 Remote Desktop