8da54f72   
   From: esquel@sommarskog.se   
      
   Joe Cool (joecool1969@live.com) writes:   
   > I can map a network drive to a share on the Server from my notebook. I   
   > can log into the server and connect locally either with Windows   
   > Authentication or SQL Authentication. While logged into my account on   
   > the notebook I cannot establish a remote connection either with   
   > Windows Authentication or SQL Authentication. The "establish remote   
   > connections" property is turned on. The SQL port 1433 is added to the   
   > list of exception ports in the Windows Firewall settings. Turning the   
   > firewall off (which is not a desired fix) does not help.   
      
   I don't know what this "establish remote connection" is; it is nothing   
   I recognize.   
      
   On the VM which is running SQL Server, open SQL Server Configuration   
   Manager. Under the node SQL server Network Configuration, verify that   
   TCP/IP is enabled. If not enable it. Also double-click TCP/IP and   
   verify that the port is 1433 and that the IP-adress is active. When you   
   are done restart SQL Server, even if you did not change anything. (In   
   case you forgot to restart SQL Server last time you changed something   
   here.)   
      
   Also verify that the servername you use actually map to the IP address   
   used by the server. You can also try to connect by IP address.   
      
   I don't know how confident you are with your firewalls, but it is a   
   good idea to disable all firewalls until you get a connection working.   
   Then you know that your firewalls are not blocking the road for you.   
   Once you are there, you can start configuring the firewalls.   
      
      
   > The exact error message I get is Microsoft SQL Server Error 64.   
   > Basically the text of the message says that the server is either not   
   > configured to allow remote connection or I am specifying the wrong   
   > instance name. The server is only running one instance of SQL and was   
   > configured as the default instance. So when connecting all I am   
   > specifying for the Server name is just the computer name of the server   
   > with no specific instance specified.   
      
   Could you post the exact error message? From your description it sounds   
   like the standard error message when the server is not reachable, but   
   that message has number 53, not 64. So maybe there is something in the   
   message that gives a specific hint.   
      
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)