January 23, 2007 at 2:15 pm
Hello everyone,
I have installed a named instance of SQL Server 2005 on a server (standard edition).
There is also a default instance of SQL Server 2005 on this server (developper Edition).
Connecting to the default instance from a SQL Server 2000 client is ok (no problem).
When I try to connect to the named instance (still from a SQL Server 2000) client I receive this error:
[DBNETLIB]Specified SQL server not found.
[DBNETLIB]ConnectionOpen (Connect()).
But I am able to connect using osql with the name pipe protocol:
osql /S\\sql5\pipe\MSSQL$gcrm\sql\query /E
Also, using netstat -ano, I can see that the server is listening on ports related in the server log file:
Server is listening on [127.0.0.1 <ipv4> 3139]
Server is listening on ['any' <ipv4> 3416]
The client is MDAC 2.8 sp1 on Windows XP sp2.
Could it be a problem with port 1434 which is supposed to give information on the dynamic port chosen?
Any idea on this problem?
Regards.
Carl
January 23, 2007 at 2:24 pm
Try using port number with instance name...
MohammedU
Microsoft SQL Server MVP
January 23, 2007 at 2:28 pm
Hello Muhammed... what do you mean exactly?
Regards.
Carl
January 23, 2007 at 4:13 pm
Mohammed means that you use Client Network Utility (cliconfg) and specify the port for TCP/IP alias if you use TCP/IP. Or you may just create a named pipes alias. In SQL Server 2005 you can use SQL Server Configuration Manager for configuring Client Connections. It would show the same alias properties as Client Network Unility.
It could also happen that the Firewall prevents connection on your instance TCP/IP port but would allow Named Pipes port 445.
Regards,Yelena Varsha
January 24, 2007 at 6:37 am
Hello Muhammed, Yelena,
I had mention in the first post that I had done a test using named pipes and it worked:
osql /S\\sql5\pipe\MSSQL$gcrm\sql\query /E
It is obviously the same thing if I do an alias using named pipes.
I made an alias using TCP/IP "hardcoding" the port 3416 and it work also.
This would be an interresting work around but I wanted to know why without using alias, I am unable to connect to the named instance using TCP/IP and dynamic ports? And why this named instance is not published on the network?
Regards,
Carl
January 24, 2007 at 7:04 am
I finally found the problem: It is only that the SQL Server Browser service was not running...
Nothing was listening on UDP port 1433 to give the dynamic port allocated (3416) for incoming cient connections.
The service was disabled... Not sure if it is the default on SQL Server 2005 (for security reasons).
Best regards.
Carl
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply