Re: highly appreciated.

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

David, you are very right but how can I change the port of default instance
to 1434 and named instance to 1433 ... basically this is our production
machine and couple of databases are running to hit default instance.. what u
think if i do this then all would be in trouble right....

Looking forward to your reply.

Thanks

"David Gugick" wrote:

> Rogers wrote:
> > David, what I am thinking right now... do I need to create linked
> > server before registering the named instance on my machine ?
> >
>
> If you're just connecting over the internet (which I assume from your
> last post that you are), you're correct that you'll need to use the IP
> address. This just makes me think there's a firewall issue on the remote
> PC or remote network preventing communications on that IP over port
> 1434. To determine this, you could swap ports on the remote server and
> make the named instance 1433 and cycle the SQL Server. If you then
> connect to the named instance, you'll know it's a firewall issue.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
>
.

Relevant Pages

  • Re: Cannot connect remotely but TCP/IP is enabled
    ... Are you using a named instance? ... "Brent Horine" wrote in message ... > I connect to this server using remote desktop and I can use osql to login. ...
    (microsoft.public.sqlserver.msde)
  • Re: highly appreciated.
    ... This just makes me think there's a firewall issue on the remote PC or remote network preventing communications on that IP over port 1434. ... you could swap ports on the remote server and make the named instance 1433 and cycle the SQL Server. ...
    (microsoft.public.sqlserver.clients)
  • Re: highly appreciated.
    ... "David Gugick" wrote: ... >> I am trying to connect the named instance from my client computer... ... >> that SQL Server doesn't exist or access denied.... ... > Why are you defining an alias? ...
    (microsoft.public.sqlserver.clients)
  • Re: SQL Management Studio will not connect to x64 bit SP2 server
    ... SQL server config manager|sql server ... Management Studio on the x64 bit server with named instance. ... Connects to 32bit remote 2005 Server ... connecting to SQL Server 2005, this failure may be caused by the ...
    (microsoft.public.sqlserver.connect)
  • Re: unable to connect to sql server remotely
    ... Is it a default or named instance? ... Andrew J. Kelly SQL MVP ... 'An error has occurred while establishing a connection to the server. ... this failure may be caused by the fact that under the default settign SQL does not allow remote connections....' ...
    (microsoft.public.sqlserver.security)