all groups > sql server connect > february 2006 >
You're in the

sql server connect

group:

SQL Server running on a different port.


SQL Server running on a different port. Clarkie
2/20/2006 12:00:00 AM
sql server connect: Hello!

I am trying to understand how connections are made to a SQL Server when the
server is running on a different port.

My SQL Server 2000 SP4 is configured to listen on port 465 for TCP/IP. I
used the server network utility. My client has no idea of this but still
manages to connect using the following connection string:

Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=Cleo;Data Source=192.168.0.156

I create and test the connection string by a UDL-file. I have verified that
the server is listening on port 465 and not 1433 by running "netstat -a" in
the command prompt.

So why do I manage to connect? Another thing that confuses is that if I
specify port number like this:

Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=Cleo;Data Source=192.168.0.156:465

it does not work. Error message.

Test connection failed because of an error in initializing provider.
[DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection.

Regards

Clarkie



Re: SQL Server running on a different port. Jens
2/20/2006 5:59:40 AM
Its:

Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=Cleo;Data Source=192.168.0.156,465

HTH, Jens Suessmeyer.
AddThis Social Bookmark Button