We just installed SQL Server 2016 on a Windows 2016 server. I am having issues connecting to the Named Instance of that server. I have noticed that the server isn't listening on port 1434 either. Normally we would see it in log as:
Server is listening on [XX.XX.XX.XX <ipv4> 1434>
But the only thing I see in the logs are:
Server is listening on [ 127.0.0.1 <ipv4> 63229]. Server is listening on [ ::1 <ipv6> 63229].
I can seem to connect to this named instance other than on the local server. We have apps running that will hit this Named Instance but it seems like we are having issues connecting.
I also did a
netstat -ao | findstr /I "processID" and I couldn't see the 1434 ports. I had configured my TCP/IP to use the TCP Port 1434 for my IP but it's still not working.
Any ideas why it's not listening on 1434?
I checked in Configuration Manager and everything looked fine. TCP/IP was enabled and SQL service restarted. It doesn't seem to be listening on that port when it starts up.
The SQL Browser service is turned on. The TCP Port 1434 is assigned to the IP but the TCP Dynamic Ports and TCP Port is blank in the
Maybe the question is how is the named instance supposed to be set up? This was to replace an old server that was running SQL 2012 and that server had it set this way and it's been running fine. So I copied the same setting and we can't seem to connect to the named instance.