Unable to remote desktop Azure VM when IP changed from Dynamic to Static (Public IP). Previously with Private IP Address and port number I was able to remotely access azure VM.
Unable to remote desktop Azure VM when IP changed from Dynamic to Static (Public IP). Previously with Private IP Address and port number I was able to remotely access azure VM.
Your question is related with Azure VM, I will remove IPV6 tag and add the corresponding azure VM tag. Thank you!
As I can understand previously you were connecting the VM using private IP address and now is it public ? If you are connecting using public IP address then there might be a possibility that your network is blocking to take remote using public IP (Usually most organization do this). If you are using still private IP, then there should not be an issue if you just changed it to static. Just would like to know how you have changed it ? From Azure NIC level or within OS ?
Thanks & Regards,
Pritam Ghatak (Prips)
Do click on "Mark as Answer" and Upvote on the post that helps you, this can be beneficial to other community members.
@PrashantAndhale-0441 Welcome to Microsoft Q&A, Thank you for posting your here!!
If you have another VM in the same network (Virtual Network or subnet ) of the problem VM please check the connectivity by taking RDP with Private ip of the Problem VM from the other VM and also check if you are able to access the VM form serial console.
After each troubleshooting step, try reconnecting to the VM:
Reset Remote Desktop configuration.
Check Network Security Group rules / Cloud Services endpoints.
Review VM console logs.
Reset the NIC for the VM.
Check the VM Resource Health.
Reset your VM password.
Restart your VM.
Redeploy your VM.
Hope this helps!
Kindly let us know if the above helps or you need further assistance on this issue.
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
@PrashantAndhale-0441 Just checking in to see if the above answer helped. If this answers your query, do click “Mark as Answer” and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.
As I can understand previously you were connecting the VM using private IP address and now is it public ? If you are connecting using public IP address then there might be a possibility that your network is blocking to take remote using public IP (Usually most organization do this). If you are using still private IP, then there should not be an issue if you just changed it to static. Just would like to know how you have changed it ? From Azure NIC level or within OS ?
Thanks & Regards,
Pritam Ghatak (Prips)
Do click on "Mark as Answer" and Upvote on the post that helps you, this can be beneficial to other community members.
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.
5 people are following this question.