Re: SQL Server multiple instance problem
- From: "Geoff N. Hiten" <sqlcraftsman@xxxxxxxxx>
- Date: Fri, 20 May 2005 06:53:51 -0400
All instances of SQL Server will bind to all IP addresses at service
startup. This cannot be changed. The default instance will grab port 1433.
Other instances will randomly bind to an available port. UDP Port 1434 is
used to resolve port numbers and names in SQL Server multi-instance
installations. You can use the Server Network Utility to force an instance
to use a particular port.
Geoff N. Hiten
Microsoft SQL Server MVP
"John" <john@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:O1SQ$PSXFHA.228@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
>
>
> I have created 2 instances in SQL server on a windows 2000 server over a
> Public IP. The 1st instance is assigned the PUBLIC IP and can be accessed
> over a remote location.
>
> Whereas the 2nd instance cannot be accessed over the public IP.
>
>
>
> Now I want to change and assign the Public IP to the second instance, so
> that the 2nd instance can be connected from a remote location over the
> Internet.
>
> Thanks in advance
> John Mendonca
>
>
.
- Follow-Ups:
- Re: SQL Server multiple instance problem
- From: John
- Re: SQL Server multiple instance problem
- References:
- SQL Server multiple instance problem
- From: John
- SQL Server multiple instance problem
- Prev by Date: Re: Upgrade from SQL Server 2000 32 Bit to 64 Bit
- Next by Date: Re: SQL Server multiple instance problem
- Previous by thread: SQL Server multiple instance problem
- Next by thread: Re: SQL Server multiple instance problem
- Index(es):
Relevant Pages
|