MS SQL 2000 TCPIP Port Number and SQL Replication

[nik]

Hi all

I'm struggling to find an answer to this one!

We've configured our SQL boxes to run under a different port number,
e.g. from 1433 to 4533. This works fine under our Citrix enviornmnet
where the dsn is configured to use the new port. The problem comes in
terms of SQL Server management. For example, when you try and
configure SQL Replication, it is not possible to add the subscriber
unless the SQL Servce runs under port 1433, the default port. The
same goes when you try to add the server as a registered server within
the Enterprise Manager MMC.

Does anyone know how you can configure SQL Server to run under a
different port number, without naffecting SQL REPLICATION, etc?

Many thnaks
Nik
ni*@nastek.co.uk

[Simon Hayes]

ni*@nastek.co.uk wrote in message news:<a3********************************@4ax.com>. ..

Hi all

I'm struggling to find an answer to this one!

We've configured our SQL boxes to run under a different port number,
e.g. from 1433 to 4533. This works fine under our Citrix enviornmnet
where the dsn is configured to use the new port. The problem comes in
terms of SQL Server management. For example, when you try and
configure SQL Replication, it is not possible to add the subscriber
unless the SQL Servce runs under port 1433, the default port. The
same goes when you try to add the server as a registered server within
the Enterprise Manager MMC.

Does anyone know how you can configure SQL Server to run under a
different port number, without naffecting SQL REPLICATION, etc?

Many thnaks
Nik
ni*@nastek.co.uk

I haven't tried this myself, but this KB article seems to suggest that
creating a server alias (in Client Network Utility) with the correct
port number should work:

http://support.microsoft.com/default...&Product=sql2k

Simon

[Joe Maloney]

sq*@hayes.ch (Simon Hayes) wrote in message news:<60**************************@posting.google. com>...

ni*@nastek.co.uk wrote in message news:<a3********************************@4ax.com>. ..

Hi all

I'm struggling to find an answer to this one!

We've configured our SQL boxes to run under a different port number,
e.g. from 1433 to 4533. This works fine under our Citrix enviornmnet
where the dsn is configured to use the new port. The problem comes in
terms of SQL Server management. For example, when you try and
configure SQL Replication, it is not possible to add the subscriber
unless the SQL Servce runs under port 1433, the default port. The
same goes when you try to add the server as a registered server within
the Enterprise Manager MMC.

Does anyone know how you can configure SQL Server to run under a
different port number, without naffecting SQL REPLICATION, etc?

Many thnaks
Nik
ni*@nastek.co.uk

I haven't tried this myself, but this KB article seems to suggest that
creating a server alias (in Client Network Utility) with the correct
port number should work:

http://support.microsoft.com/default...&Product=sql2k

Simon

We have some servers with non-standard ports. We access them using the
Client Network Utility with the correct port and have no problems with
MMC, ISQLW or OSQLW or even ODBC.