UNABLE TO ACCESS CUSTOM PORT

Dhruv Soni 0 Reputation points
2024-07-10T08:49:15.4566667+00:00

Hey Reader !

I am having an issue opening a custom port in my virtual machine. Tried everything from configuring Inbound rule from portal to configuring The rule inside my windows server 2019 Datacenter but nothing seems to open the port.

Tried opening it through PowerShell too, but the port checker says it to be closed and i tried the same with multiple resource groups, multiple resources and cross resources too.

So if anyone from the community can help me troubleshoot it would save a lot of R&D and get back to a smooth operational flow.

Hope to receive a response soon.

Thank you and have a great day ahead :)

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,287 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2024-07-10T08:49:15.46+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It seems like you are having trouble opening a custom port in your virtual machine. You mentioned that you have tried configuring inbound rules from the portal, configuring the rule into your Windows Server 2019 Datacenter, and using PowerShell, but the port checker still says that the port is closed.

    One thing you can try is to check if the port is allowed in the network security group associated with your virtual machine. You can navigate to the Networking settings of your virtual machine in the Azure portal and check the inbound security rules for the network security group. Make sure that there is a rule that allows traffic on the custom port you are trying to open.

    If the port is allowed in the network security group, you can also try checking if the application or service that is listening on the custom port is running and configured correctly.

    I hope this helps you troubleshoot the issue.


    References:

    0 comments No comments