MS SQL Port

How can I determine which port MS SQL is running.
I known that this can be set at SQL Server Network Utility, but I
wonder why my ASP.NET script can connect to SQL Server even I change
its running port.

Another thing I want to know... actually it doesn't concern with SQL
that is,
how can I watch all the enviroment variable in Windows XP, such as
%systemroot% and how can I set that one"=aKe=" <darkgod1987@.hotmail.com> wrote in message
news:36e545c4.0404140338.6b6e5440@.posting.google.c om...
> How can I determine which port MS SQL is running.
> I known that this can be set at SQL Server Network Utility, but I
> wonder why my ASP.NET script can connect to SQL Server even I change
> its running port.
> Another thing I want to know... actually it doesn't concern with SQL
> that is,
> how can I watch all the enviroment variable in Windows XP, such as
> %systemroot% and how can I set that one

You can look in the SQL Server Log for the port, in the registry, or use the
SQLDMO Registry2 object's TcpPort property.

SQL Server listens on two ports - 1433 and 1434 (by default). A client can
connect to port 1434 to get connection information about all the instances
on the server, inclluding their ports. See "Controlling Net-Libraries and
Communications Addresses" in Books Online.

As for environment variables, you can use SET in the Windows shell, or use
an interface such as WMI which returns all the current variables. WSH has a
built-in object for this, I believe, perhaps the Network object but I'm not
entirely sure.

Simon

MS SQL 2000 TCPIP Port Number and SQL Replication

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
nik@.nastek.co.uknik@.nastek.co.uk wrote in message news:<a30v10lk653eu3j878hfj0tpflub252qrl@.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
> nik@.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/defaul...2&Product=sql2k

Simon|||sql@.hayes.ch (Simon Hayes) wrote in message news:<60cd0137.0402030644.62669b66@.posting.google.com>...
> nik@.nastek.co.uk wrote in message news:<a30v10lk653eu3j878hfj0tpflub252qrl@.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
> > nik@.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/defaul...2&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.