0

I'm working through configuring SQL Server express (2017) to listen directly on TCP/IP ports per the other conversations without the browser.

Enable remote connections for SQL Server Express 2012

With there being a 32 Bit and 64 Bit "Native Client" (both asking for TCP/IP), as well as a 32 Bit and 64 Bit SQL Server Network Configuration (only the later having any information about TCP/IP addresses and ports),

Can all 3 (of the 4 options sets? Why is the one omitted) be set to the same listening TCP/IP port or does this create a clash requiring a segmentation.

32 Bit Native Client Configuration 64 Bit Native Client Configuration 64 Bit Network Configuration 32 Bit Network Configuration

ffejrekaburb
  • 656
  • 1
  • 10
  • 35
  • Why are you trying to set a named instance to listen on port 1433? Just install a default instance in this case! – Andrey Nikolov Jan 14 '19 at 16:18
  • It was the default install. I could have missed something in the installation. I want to remove the complexity. Is this not possible after installation? I can uninstall and reinstall without a name then set to listen to 1433? – ffejrekaburb Jan 14 '19 at 16:22
  • Yes, you must install a new default instance. It will listen on port 1433. – Andrey Nikolov Jan 14 '19 at 20:03

0 Answers0