Re: Failed connections to remote 2k SQL Server
- From: "James Vickers" <JamesVickers@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 28 Oct 2005 00:26:02 -0700
Sue,
Thanks for taking the time to reply to my post. I have checked, the instance
that I want to connect to is running on 1433, and the instance that I don't
want to connect to is running on 4527 - I assume the default port used by
Veritas for their backup software.
I have also double checked the firewall, it is open on TCP & UDP ports
1433-1437.
Anything else it coule be?
Jamie
"Sue Hoegemeier" wrote:
> It could be a port issue - that would be my first guess. The
> default instance (no instance name) will use the default
> port of 1433. Check to see what ports your instances are
> actually listening on - you can find it in the SQL log at
> start up, from the Server network utilities (check the
> properties for TCP/IP), from the registry in the
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\<InstanceName>\MSSQLServer\SuperSocketNetLib\Tcp
> key.
> If you aren't using a static port and are going through a
> firewall, you need to open up UDP 1434 for SQL Server name
> resolution for the named instance.
> The following articles have more information:
> INF: TCP Ports Needed for Communication to SQL Server
> Through a Firewall
> http://support.microsoft.com/?id=287932
> How to use static and dynamic port allocation in SQL Server
> 2000
> http://support.microsoft.com/?id=823938
>
> -Sue
>
> On Tue, 25 Oct 2005 00:50:02 -0700, "James Vickers"
> <JamesVickers@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >Hi Everyone,
> >
> >I have a SQL Server 2k running SP4 installed on a Windows 2k3 server. It has
> >two named instances, because the server also runs Veritas Backup Exec, which
> >itself, installs an instance of SQL Server to log it's actions. This server
> >is remotely managed by myself.
> >
> >When I use enterprise manager on the server, all is fine, both as
> >registering under the server name, and the server IP address, using the
> >format of:
> >
> >x.x.x.x\instance_name.
> >
> >I am logging in as SA, with a password that I have verified, many, many,
> >times.
> >
> >
> >However,
> >
> >When I try to register the server in Enterprise Manager remotely (with SP4
> >applied), I cannot gain a connection. On both networks, port 1433 is open. On
> >the network hosting the SQL Server, I have allowed 1433-1437 for both TCP and
> >UDP access to the SQL Server's IP through it's firewall. On my network, I
> >have access to any host over port 1433, and already have other external SQL
> >Servers (not managed by me) registered successfully. I have checked the SQL
> >server's network utility, and client network utility, and ensured that they
> >are using TCP/IP over port 1433.
> >
> >I have run a netsh diag iphost connect to the server over port 1433, which
> >succeeds. If I try and connect without using a named instance, it connects,
> >and errors to tell me to use a named instance! When I try and connect with a
> >named instance, i.e. x.x.x.x\named_instance it waits for about 2 minutes,
> >then says that the server does not exist, or access denied - I know the login
> >details are correct, and I know the server IP is correct - given that it
> >errors without a named instance, I assume that it is connecting.
> >
> >Is there anything that I am missing?, I'm afraid that my level of knowledge
> >with SQL Server is now exhausted!
> >
> >Any help would be much appreciated.
> >
> >Best regards,
> >
> >James Vickers,
> >me@xxxxxxxxxxxxxxxx
>
>
.
- Follow-Ups:
- Re: Failed connections to remote 2k SQL Server
- From: Sue Hoegemeier
- Re: Failed connections to remote 2k SQL Server
- References:
- Re: Failed connections to remote 2k SQL Server
- From: Sue Hoegemeier
- Re: Failed connections to remote 2k SQL Server
- Prev by Date: Re: Backup Question
- Next by Date: Re: Memory requirement
- Previous by thread: Re: Failed connections to remote 2k SQL Server
- Next by thread: Re: Failed connections to remote 2k SQL Server
- Index(es):
Relevant Pages
|
