I renamed the server and now I cannot connect

Jeff Wright (QMF) 0 Reputation points
2024-06-19T18:51:06.7333333+00:00

Hello, I have renamed the server in the Windows side and now I cannot connect. The old name was "WindowsReadytouse" or something like that.

Azure Bastion
Azure Bastion
An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.
248 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,572 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. akinbade abiola 8,215 Reputation points
    2024-06-19T19:49:21.0966667+00:00

    Hello Jeff Wright,

    Thanks for your question.

    Try connecting to the VM using its IP address rather than the new server name. This will help to isolate DNS resolution issues.

    See: https://learn.microsoft.com/en-us/azure/bastion/connect-ip-address

    Regards,

    Abiola

    You can mark it 'Accept Answer' and upvote if this helped.

    0 comments No comments

  2. Jeff Wright (QMF) 0 Reputation points
    2024-06-19T20:08:39.6933333+00:00

    I stopped and Started the server (not shutdown or restart) and it came back up properly. Strange.

    0 comments No comments

  3. Jeff Wright (QMF) 0 Reputation points
    2024-06-19T20:46:33.0266667+00:00

    Stop Start Fixed it.

    0 comments No comments

  4. ChaitanyaNaykodi-MSFT 24,391 Reputation points Microsoft Employee
    2024-06-19T22:07:03.07+00:00

    @Jeff Wright (QMF)

    Thank you for posting the resolution and glad to know the issue was resolved.

    I understand the issue was resolved after you stopped and started the server. Based on the solution achieved, one explanation of this issue can be because the resource state might have stuck in Updating or Failed when the server was renamed. To restore succeeded state it is recommended to run another write (PUT) operation on the resource. When you stopped the server this operation might have restored the server to succeeded state.

    Reference document: https://learn.microsoft.com/en-us/azure/networking/troubleshoot-failed-state

    Another explanation here can be if the DNS label was updated/ renamed in this scenario then DNS propagation can take some time to propagate.

    Reference article: https://learn.microsoft.com/en-us/azure/virtual-machines/custom-domain#add-custom-domain-to-vm-public-ip-address

    If you wish to determine the exact cause of this issue creating a support request will be recommended in this case as a support engineer can access the backend logs and help determine the cause.

    Meanwhile since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

    Issue: I have renamed the server in the Windows side and now I cannot connect.

    Solution: I stopped and Started the server (not shutdown or restart) and it came back up properly.

    If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.


    Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

    0 comments No comments