Re: SQL Management Studio will not connect to x64 bit SP2 server

I think I might have found the problem. SQL server config manager|sql server
2005 network configuration|Protocols for Server|TCP/IP|IP addresses was
pointing to wrong address(orginial address where server was built). I will
have to restart the service off hours to see if correcting the IP address
works.

"Jason Massie" wrote:

Management studio communicates over the port that SQL is listening on. The
default is 1433. It is usually different for named instances. If UDP 1434 is
open, the client(SSMS in this case) can dynamically determine the port.
Please look in the errorlog at the startup messages to see what port SQL is
listening on the named instance.

--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio



"Cindy" <Cindy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3F97F763-F727-4A1C-8A8A-6156D6F06865@xxxxxxxxxxxxxxxx
Does Management Studio communicate over 1433? Below what works and what
doesn't.

Management Studio on the x64 bit server with named instance.
1. Connects to named instance on itself
2. Connects to 32bit remote 2005 Server
3. Connects to 32bit remote 2000 Server

Management Studio on my XP SP2 workstation
1. Connects to 32x remote 2005 Server
2. Connects to 32x remote 2000 Server
3. Fails to connect to x64 named instance 2005 Server

If port 1433 was not working I don't think other connections would connect
without issue.

Thanks,


"Jason Massie" wrote:

Hi Cindy,
I don't think it is possible for x64 to be the issue. Once we start
talking
TCPIP, we don't care what the hosts are.

I just caught that this is a named instance. Are you sure it is 1433?
Double
check in the errorlog. If we can connect with telnet, try creating
creating
an alias forcing TCPIP and hardcoding in 1433.

--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio

"Cindy" <Cindy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:703457D7-6943-4095-B810-AF2EA740CEE9@xxxxxxxxxxxxxxxx
The server was put in production this weekend and is doing fine
answering
applications over port 1433. That is not the issue. Management Studio
will
not connect from non x64 OS.

"Jason Massie" wrote:

I would start of by trying to telnet to the server to verify ports are
open.
telnet YourServer 1433 (or your port)


--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio

"Cindy" <Cindy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:503B8FE2-E013-4464-AEAE-6D6876F26911@xxxxxxxxxxxxxxxx
I cannot connect from my XP computer using SQL Management Studio to
2005
X64
SP2 SQL named instance. I can connect to 2005 x32 SP1 fine. Below
is
error,
also in seems to be a SSL error on server I am trying to connect to.
I
can
connect directly on the server. Remote connections are allowed.

An error has occurred while establishing a connection to the server.
When
connecting to SQL Server 2005, this failure may be caused by the
fact
that
under the default settings SQL Server does not allow remote
connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance
Specified) (Microsoft SQL Server, Error: -1)










.

Relevant Pages

  • Re: ADOCE 3.1 SDK
    ... ADOCE's provider cannot connect to a remote server. ... > I am attempting to access a remote SQL Server 2000 running on a Windows ... We desire to access a remote SQL Server 2000 via ADOCE and call ...
    (microsoft.public.windowsce.embedded.vc)
  • dts package transfer local file remote server idiosyncrasy
    ... purposes and the other at a remote location. ... I developed a DTS package on my local PC and on the local SQL Server ...
    (microsoft.public.sqlserver.dts)
  • Re: highly appreciated.
    ... "David Gugick" wrote: ... >> server before registering the named instance on my machine? ... This just makes me think there's a firewall issue on the remote ... > make the named instance 1433 and cycle the SQL Server. ...
    (microsoft.public.sqlserver.clients)
  • Setup problem: General Network Error
    ... I have a problem re-installing a named instance of Sql server 2000. ... Disk 1 with data/logs sql server named instance ...
    (microsoft.public.sqlserver.server)
  • Setup problem: General Network Error
    ... I have a problem re-installing a named instance of Sql server 2000. ... Disk 1 with data/logs sql server named instance ...
    (microsoft.public.sqlserver.setup)