Re: SQL Server multiple instance problem

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: 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)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Only one instance of SQL Server can use TCP port 1434. ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL 200 Dev edition on workgroup will not connect
    ... I have been using sql server for about 8 years but mainly working with sql 2000. ... know your experience level with SQL Server and yes, sometimes things being messy but letting a SQL Server instance to accept remote connections and uninstalling it are generally straightforward tasks to perform. ... I suggest you to check for the dynamic port number that your SQL Server graps. ... Write down the port number in the "TCP Dynamic Ports" property and then run a Command Prompt and see if this port is bening listened. ...
    (microsoft.public.sqlserver.connect)