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

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: VB app connect THROUGH proxy to a remote SQL database
    ... The whole "HTTP proxy is way more secure than allowing outgoing ... the client app and the SQL server are on ... incoming connections to the SQL server are not the problem - it's ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... If I cut the maximum number of connections to for ... SQL Server simply blocks any further try to open another table until I close ... This doesn't happen with the SQL Server 2000 but with SQL Server ... No, I think ms-sql-s means that SQL 2000 is using port 1433, which is ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Management Studio cannot connect remotely
    ... firewall has the TCP port 1433 and UDP port 1434 open). ... Server is listening on TCP port 1433. ... Use SQL Server Configuration ... protocol connections are using. ...
    (microsoft.public.sqlserver.connect)
  • Re: How to Direct connect with ActiveSync
    ... Server 2000, Visual Studio 2008. ... I run this and get the "Can't find Server or Access Denied". ... Again sorry if this should be in another form but you say that SQL Server ... My web connections and desktop project connections to SQL Server ...
    (microsoft.public.sqlserver.ce)
  • Re: Cant connect to local SQL Server 2005 from .adp
    ... One caution is that your SQL Server is now available to any computer which can connect to yours on TCP port 1433. ... I'm not sure I remember that correctly, so if it doesn't work, see what SQL Books OnLine says about shared memory connections. ... you can disable the remote connections again. ...
    (microsoft.public.access.adp.sqlserver)
Loading