Clever Geek Handbook

SQL Server Instance Name with IP Address

I have a very strange situation and I hope someone knows why.

I have TCP / IP for all ports on the standard port 1433.

All tests are compatible with SQL Server Management Studio and my program.

It works:

  • ComputerName \ InstanceName
  • 127.0.0.1
  • 127.0.0.1,1433
  • 192.168.1.100
  • 192.168.1.100,1433

This does not work:

  • 127.0.0.1 \ InstanceName

Note. I know this is not firewall related because I can telnet at 127.0.0.1 to port 1433.

Note2: The connection string doesn't matter as the tests are compatible with Management Studio, but I'll give it anyway: server={0};Integrated Security=True;Database=MyDatabase

When reading MSDN it seems that you should be able to connect to the instance name via the IP address.

What's going on here?

+2


source to share


1 answer


Named SQL instances listen on a random port by default. You need a SQL Browser service , this listens on UDP on 1434 and responds to instance discovery requests by instructing the client on the true listening port. Also you need to allow the firewall to trigger holes based on the process name so that SQL can communicate on whatever port it senses.



Otherwise, you must explicitly force a named instance to an unnamed port.

+7


source






More articles:


All Articles