Errors when logging in via RDP

Андрей Михалевский 3,461 Reputation points
2021-10-18T08:49:06.327+00:00

Hi. I have a terminal farm of 11 servers. Windows Server 2019.

Today I cannot log in to one of the servers.

Connect by FQDN i got this error:

141353-timeerror.jpg

i can connect with Enter-PSSession dattum-rdp-06 from my PC:

  1. The get-date command returns the correct time.
  2. The Get-NetIPConfiguration command returns the correct domain controller. The domain controller itself is functioning correctly, dcdiag /q does not return any errors.

InterfaceAlias : Ethernet0
InterfaceIndex : 2
InterfaceDescription : vmxnet3 Ethernet Adapter
NetProfile.Name : resoleasing.com
IPv4Address : 10.2.3.36
IPv6DefaultGateway :
IPv4DefaultGateway : 10.2.3.254
DNSServer : 10.2.3.1
10.1.0.1

  1. Get-TimeZone returns the correct time zone.

w32tm /query /status returns the correct values. Everything converges with the client.

  1. Test-ComputerSecureChannel return TRUE.

Connect by ip:

141323-nla.jpg

After disable NLA:
(Get-WmiObject -class "Win32_TSGeneralSetting" -Namespace root\cimv2\terminalservices -ComputerName $server -Filter "TerminalName='RDP-tcp'").SetUserAuthenticationRequired(0)

I got:

We can’t sign you with this credential because your domain isn’t available. Make sure your device is connected to your organization’s network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Андрей Михалевский 3,461 Reputation points
    2021-10-21T09:24:43.637+00:00

    Two days later, it's a problem again. Help solve it.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.