Posted by basuritta on 02/07/07 11:53

I am trying to add a SQL2000 subscriptor to a SQL2005 publisher and
distributor using the Management Studio.

I'm using a non-standard port in both ends, but I have set the port
for the TCP/IP protocol to the non-standard port in both the server
and client network configuration.

I can add the SQL2000 server to the Management Studio console without
problems, and even without haveing to specify the port I'm using (as
expected)

But when I try to add the SQL2000 server as a subscriptor I get an
error of "Unable to connect to server".

I have use external tools to check the network traffic between both
servers and I see that the SQL2005 server is trying to connect to the
SQL2000 server using the standard port (1433), not the one I put in
the network configurator.
Moreover, if I use the naming convention of "SERVERNAME, Port" in the
server name field when doing this, I get an error saying the only the
servername is expected. No aliases or IP addresses.

SQL Server 2000 is SP4 and running in Win 2000 Server SP4
SQL Server 2005 is SP1 and running in Win 2003 Server R2 SP1

Is this a known bug? How can I solve this problem? Why the management
studio is using the standard port for this? Any suggestion/idea out
there?

Thanks in advance for your help!

• Next in forum: Re: Stored procedure and SQL Job Agent Task
• Prev in forum: Re: "insert on existing update" in MS SQL Server?
• Thread view: SQL Server 2005: Unable to add SQL2000 subscriptor using non-standard port!

[Reply to this message]