This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 6%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAT%3C/text%3E%3C/svg%3E)
I had a Windows VM with "D2_v3" running. Then changed it to "B2S". Now I can't connect any more to my VM. I restarted but still doesn't work. I resetted the configuration but still doesn't work. Now after reading hundrets of documentation sites and hours or trials I am stuck. I can't connec to my VM any more.
The configuration was a bit too small. I am wondering why the "Azure-portal" allows me choose a too small configuration for my virutal computer and also why the error messages when connecting via RDP didn't tell me about this. I selected a bigger, more expensive configuration and now it works. -> Issue solved.
Hello @AndreasT-0720,
Could you please check the deployment logs and see anything helpful available there?
Also check activity logs https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/view-activity-logs
From azure portal, you can connect the VM through serial port also as explained here to get more details of the issue: https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshooting/serial-console-windows
Please mark as "Accept the answer" if the above steps helps you. Others with similar issues can also follow the solution as per your suggestion
Regards,
Manu
Dear @ManuPhilip thanks a lot for your prompt answer, which was helpful to learn more about Azure. See my PDF to know, what I received from your links:
Furthermore I already did the following:
But I still can't connect to the virtual machine. See screenshots in PDF what I can see.
Thanks a lot for your help. Andreas
And here is another Screenshot, which says "All issues should be solved", but I still can't connect to my VM any more. See documentation in my PDF above.
Hello,
Thanks for providing more details with screenshots. Unfortunately, I can't read the texts in different language. At the final page, it shows the error showing the exact issue. Could you please send translation of the error message in English so that w can understand your issue correctly
Thanks,
Manu
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 98%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
@AndreasT-0720 Please provide the details as requested above so that we can help you better. Thanks :)
The final page says (translation below):
German:
"Dieser Computer kann keine Verbindung mit dem Remotcomputer herstellen.
Zwischen den beiden Computern konnte in der vorhergesehenen Zeit keine Verbindung hergestellt werden. Wiederholen Sie den Verbindungsversuch. Wenden Sie sich an den Beitzer des Remotecomputers oder an den Netzwerkadministrator, wenn das Problem weiterhin besteht. "
English:
"This computer cannot connect to the remote computer.
No connection could be established between the two computers in the foreseen time. Try the connection again. If the problem persists, contact the remote computer operator or the network administrator."
Thanks for the details. Please check if Port 3389 is open to be connected to the VM. If not, allow the port and try again
Regards,
Manu
Yes, port 3389 is open and I tried again, but it doesn't work.
Then I changed the protocol from TCP to any and received the following error message:
German: Die Sitzung wurde aufgrund eines Protokollfehlers Code 0x112d getrennt. Versuchen Sie, die Verbindung mit dem Remotecomputer wiederherzustellen.
English: The session was disconnected due to a log error code 0x112d. Try reconnecting to the remote computer.
I also tried to configure new ports using the Azure-Portal and then the menu "settings" g->"network". For example I configured 8888. Then reconnected with RDP and received another error message:
German:
Der Remotedesktop kann nicht hergestellt werden weil
English:
The Remote Desktop cannot be manufactured because
No matter what I do using different ports I can't connect to the virtual machine any more.
See comment below. And PDF above. Do you need more?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I had a similar issue that a customer changed the private IP address after login in to the vm.
What i did was to:
Stop and deallocate the vm
Go to networking and click on "Attached interface"
You may need to create a new interface.
You can now delete the old NIC, if you want
You can then assign a new IP or use the existig public ip
I used these methods to resolved the issue.
Let me know if these method helped.