Access to member server via RDP only with IP or with full FQDN, can't access via name

Arnold Mishaev 71 Reputation points
2022-01-17T15:25:20.007+00:00

Hey everybody,

we are encounter with an issue which happened in all domain.
in our environment we have 4 DCs and more than 60 member server.

the issue is when I tried to access to member server via name "SRV-01" i've getting message that said "Logon attempt failed" but the credentials are good.
but i manage to access via server\endpoint IP and via full FQDN example:"SRV-01.domain.com."
we can't find any related events to start investigation

Does anyone encounter with this issue or have any idea?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,116 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,234 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,021 questions
Windows Server Management
Windows Server Management
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Management: The act or process of organizing, handling, directing or controlling something.
421 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Limitless Technology 39,351 Reputation points
    2022-01-18T08:48:03.023+00:00

    Hello ArnoldMishaev,

    This looks like a Netbios connection issue. The NetBIOS configuration is done in the network adapter settings. Therefore, it is necessary to enter these settings, and then select “Protocol IP version 4 (TCP / IPv4)” and click on properties.

    After that, we must click on "Advanced ..." and then on the "WINS" tab. Down there we have the NetBIOS settings. Interestingly they were already in "Standard", which means that NetBIOS should be working. What I did was change to "Enable NetBios over TCP / IP" and then go back to "Standard". And so the problem was solved and never came back.


    --If the reply is helpful, please Upvote and Accept as answer--

    1 person found this answer helpful.
    0 comments No comments

  2. Arnold Mishaev 71 Reputation points
    2022-01-18T09:14:49.183+00:00

    Hello @Limitless Technology

    Thanks for your answer but it doesn't work for us

    We've did the next steps:

    1) Go into "Wins" tab under "Protocol IP version 4 (TCP / IPv4)" properties on the "problematic" NIC
    2) Under "NetBIOS setting" Uncheck the checkbox from "Default" and check checkbox "Enable NetBIOS over TCP/IP", apply new configuration and close the window
    3) Under "NetBIOS setting" Uncheck the checkbox from "Enable NetBIOS over TCP/IP" and check checkbox "Default", apply new configuration and close the window

    we did this on both source and destination, nothing change.

    0 comments No comments

  3. Arnold Mishaev 71 Reputation points
    2022-01-27T09:28:13.163+00:00

    The issue got resolve by demoting one of physical server, for some reason he's tried to connect with KDC of the DC that not longer part of domain.
    Once we demote the DC the issue resolved

    0 comments No comments