connect to SQL port other that 1433

facade

Hello

Does anybody know how to connect to sqlserver\instance and different port.
I'm trying to create a new db on sqlserver\instance:port (ie SQL\CLIENT:5555) but that doesn't seem to work ?
I've tried to telnet SQL\CLIENT 5555 - and this works.

Waldo

Did you try to modify your host and services file?

facade

Host i modified
sql.ip.addr.ess SQL\instance

What should I do with services - it's sql we're talking about?

Waldo

host:
sql.server.ip.address choosename

services:
choosename 5555/tcp #somekindofdescription

choosename = just a name that you want to use in Navision. When using this name, navision will look in your host file to konw the IP, and in the services file to know the port no.

Hope this helps...

Waldo

Forgot something:
you have to place the port number in order, not just at the end of the services file.

facade

Ok thanks I'll try it I though it applied only to navision server

GoMaD

You can always try to change the settings on the level of your SQL Server.

Use the "Server Network Utility" in your SQL Server menu.

Choose properties of the TCP/IP Protocol (should be in the "Enabled Protocols" list) and change the "Default Port" number.

Restart your SQL server and during the first communication from the Navision Client to the SQL server, the SQL server will "push" the correct Port number to the client.

Note: All communication to your SQL server over TCP/IP will use this port.

Regards

kine

I have similar problem... MS SQL server is installed on port 2433. But problem is that I am connected on terminal server in DMZ and I cannot use the Server list (it is empty).

facade: Have you solved the problem?

GoMaD

connect to your server with the following notation (place this in the server name field of your navision client when connectin to the db):

<ip adress server>:<port number>

eg:
10.0.0.1:2433

facade

Use Client Network utility to define an alias for it with different port. Or better yet change the default SQL port on Client Network Utility to your port.

Connecting with ip:port - does not work for SQL - you cannot access SQL like this.

GoMaD

really?

I connect to a Navision SQL DB every day with this notation.

Waldo

Me too ... ip:port works like a charm \:D/

facade

I'll try to see what you guys see ...
laters.

kine

Alll is working ok. Problem was that server was set to "Hidden"... :whistle:

vaprog

I tried all possibilities I could think of to connect to a SQL Server on a different port. Nothing worked, even tough I knew the server accepted connections on that port, since an external tool (Java) could communicate. Finally, the help to SQL Client configuration, creating aliases using TCP/IP gave me the hint:

The syntax is

tcp:<servername>[\<instancename>],<port>

and even in NAV (2009 R2 at least) the port needs to be separated by a comma, not a colon!

afarr

I know that this is an old thread, but I spent a lot of time trying to connect NAV 2016 to SQL 2016 with a non-default port, and the only syntax that worked (for SSMS, RTC and NAV Development Environment) is the one mentioned by vaprog, that is tcp:<servername>[\<instancename>],<port>

It still doesn't work for NAV Development Environment from a different server, but that may be due to some port being blocked.

So, thanks vaprog.