Re: SQL Server multiple instance problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

So you moved the default instance off of 1433?

You should connect either via server_ip_address,port_number or
server_network_name\instance_name. When you put a non-default instance on
1433, you must specify the instance name or the port number. If you connect
via network name or ip address, SQL assumes you are looking for the default
instance and will return an error.

Geoff N. Hiten
Microsoft SQL Server MVP

"John" <john@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uxGmD6TXFHA.2684@xxxxxxxxxxxxxxxxxxxxxxx
> Hello Geoff
>
> I have made the 2nd instance to use the default port 1433 but still it
> doesnt seem to connect through remote location over internet.
>
> Also I am trying to connect to the second instance with the following
> server
> name;
>
> server_ip_address\server_name
>
> I hope the above parameter to connect to the server is correct.
>
> I get the error message "SQL Server does not exist or access denied"
>
> Thanks
> Regards,
> John Mendonca
>
>
>
>
>
> "Geoff N. Hiten" <sqlcraftsman@xxxxxxxxx> wrote in message
> news:O2R83pSXFHA.1044@xxxxxxxxxxxxxxxxxxxxxxx
>> 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
>> >
>> >
>>
>>
>
>


.

Relevant Pages

  • Re: Connecting to an instance in a cluster
    ... "Geoff N. Hiten" wrote: ... you cannot reuse port numbers. ... Microsoft SQL Server MVP ... That is the port you have to open on the firewall. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Connecting to an instance in a cluster
    ... Each virtual server has its own IP address so you can reuse port numbers between instances. ... Microsoft SQL Server MVP ... "Geoff N. Hiten" wrote: ...
    (microsoft.public.sqlserver.clustering)
  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... Either SQL Server 2000 or SQL Server 2005. ... So you have to move one of them to another port. ... You could allow an program exception in your firewall instead of a port number exception. ... I understand that you can connect to SQL 2000 named instance on the local ...
    (microsoft.public.sqlserver.setup)