Connection problem from Vista - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

Connection problem from Vista

Author

Topic

fullonmac
Starting Member

1 Post

Posted - 2007-08-13 : 07:07:33

I can't connect from a Vista Client to a SQL 2005 Server.
I have been stuck on this problem over a week so any help would be greatly appreciated.

Overview:
I cannot connect from my client (vista business) except with SQL Server Management Studio.
I have tried Red Gate SQL Compare connection from a machine running XP and it connects ok.
I have tried connecting using ODBC from another machine running Vista Home and it connects ok.
I have no problem connecting to my local SQL Server (on my client).
I have tried using Windows Auth and a SQL login.

Environment:
Both the client and server are on the same domain and the user is a domain user.

Client:
Vista Business, SQL Server 2005 SP1 Client tools and Server, RedGate tools, Visual Studio 2005 SP1
Windows Firewall ON (but have tried it off with no difference)
Norton virus protection ON ((but have tried it off with no difference)
UAC is turned off.

Server:
SQL Server 2005 SP1, Remote connections allowed over TCP/IP Port 1433 (IPAll TCP Port 1433, not dynamic)
No windows firewall, Mcaffee virus running.

I get the errors below (or similar) connecting from:
SQL Profiler
Database engine tuning advisor,
Redgate SQL Compare (or any redgate software)
Setting up an ODBC connection
Visual Studio 2005 SP1

The only application that current connects is SQL Server Management Studio!??
If I apply SQL Server 2005 SP2 to the client it stops even SQL Server Management Studio from working.

I either get the following error:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
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: Named Pipes Provider, error:0 - No process is on the other end of the pipe.)

or (if I force the port and/or method e.g. TCP:192.168.130.3,1433)

A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
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: TCP Provider, error:0 - No connection could be made because the target machine actively refused it.)

Again any help would be much appreciated as I just can not seem to solve this.

Thanks

askben
Starting Member

8 Posts

Posted - 2007-08-17 : 23:35:22

You really should check the SQL Server Configuration Manager and make sure which port the TCPIP is listening and also check to see which protocols are enabled.

I just helped someone today at the office that got the Actively Refused error, and he found out that the port was not 1433, but another one. Once he used the right port, everything was fine.

------------
Ben Miller

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources