It couldn’t have been the VM itself because he could remote in with the RDP port.Īfter help from our networking team, we realized what the problem was. But we still couldn’t connect from outsize Azure/VNET. netstat –aon clearly showed that SQL Server process was listening on port 1433. Secondly, we verified that he was able to connect to the port/SQL from a different VM in side the same VNET. First we made sure that the inbound rule in the network interface NSG had port 1433 configured. We started to verify to make sure everything was correct. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)” Verify that the instance name is correct and that SQL Server is configured to allow remote connections. The server was not found or was not accessible. “A network-related or instance-specific error occurred while establishing a connection to SQL Server. He did exactly that but couldn’t get it to work and got a very generic message like below. We got a customer call who was very puzzled. This will enable you to access your SQL Server from internet. In Azure portal, you create an inbound rule in the Network Security Group (NSG) associated with the network interface on that VM
#EXCEL CONNECT TO MYSQL HOSTED ON VM WINDOWS#
In your VM, create an inbound rule for port like 1433 SQL Server listens to in Windows Firewall configuration. It has very detailed step-by-step instructions.
If you need to open up your SQL Server on an Azure VM to public internet access, you need to look no further than this documentĬonnect to a SQL Server Virtual Machine on Azure (Resource Manager)
0 kommentar(er)
