Re: Cannot connect to SQL Server

Is the SQL Browser service running on S2?
Did you read http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html ?

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Rick Byham, (MSFT)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:7F6297AB-2D3D-41FF-932D-A0971C0188F4@xxxxxxxxxxxxxxxx
So you can connect:
C1 -> S1
C2 -> S1
S2 -> S1
but cannot connect:
C1 -> S2
C2 -> S2

Some things to check:
Can you connect from S2 to S2? If this fails, I suspect the SQL Server is not started, or you have the name wrong because it's a named instance such as S2\MSDN, or it is not accepting any connections on the protocol you are using.

If you can connect from S2 to S2, then I would double-check the firewall. I see that you said you tried turning off the firewall, but the Windows firewall that is turned on in SP2 causes most of these problems.

What protocol are you using? If TCP/IP, try connecting using the TCP address and port number, such as 120.24.118.17,1433. It's possible you have a problem resolving the computer name. That would cause this error.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"Henri" <foucauld@xxxxxxxxxx> wrote in message news:%23ZoxT3gyHHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
I have almost the same problem than Clive (cf 18/07). I have 2 servers S1, S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
The two servers are indentical, but if the two clients can connect S1, they cant' connect to S2 ""Access denied or SQL Server does not exist" (but S2 can connect S1).

- I have checked the Server Network Utility and ClientNetwork Utility : all is correct
- I have tried with the firewall unactivated : no change...
- The version of SQL 2000 on the two servers are the same.
- The network is a wire LAN.

Can anyone tell me where else to look or what else to try?

Many thanks in advance

Henri (Paris)




.

Relevant Pages

  • Re: newbie Frage zu Server-Explorer - Datenverbindungen
    ... "Microsoft SQL Server " an. ... Ich könnte den Firewall wohl ausschalten, da die Maschine via Proxi ins Netz geht. ... Ich versuche doch nur - lokal innerhalb meiner eigenen Machine - auf der ich als Admin arbeite - hinzubekommen, dass der Servername (oder meinetwegen auch lokal oder was angezeigt wird. ... Im SQL Server Configuration Manager habe ich Shared Memory, Named Pipes, UND TCP/IP Aktiviert. ...
    (microsoft.public.de.german.entwickler.dotnet.datenbank)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: some thoughts on the Slammer fiasco
    ... it can break SQL server. ... the port its better to do it at the router level so the firewall can do the ... > WTF are you running a software firewall on an SQL box for. ... > firewall of your choice) block port X. ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Server does not exist or access denied
    ... > Windows 2003 SP1 includes a firewall. ... > Mike Epprecht, Microsoft SQL Server MVP ... >>> It did not even get to SQL Server on the server. ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)