I would like to upgrade a desktop from Windows 7 to Server 2008 and
host SQL instances on it in my home Workgroup network. But before I do
that, I am running a test of this configuration with a VMWare Virtual
Machine.

I have just a single instance of SQL2008 installed in a VM running
Windows Server 2008. The VM is in the same workgroup as my Windows 7
notebook. I have an login account on it that is the name login name
and password as I am logged in on my Windows 7 Notebook that also has
SQL2008 installed. If I can get this working I plan to remove SQL from
the notebook and reinstall just the client connectivity tools.

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 have added rules for the SQL2008 Management Studio executable and
the SQL Port 1433 to the notebook's outbound firewall rules. The
notebook is running McAfee anti-virus software and is configured to
allow SQL Management studio and the SQL port full access.

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.

Any help would be appreciated.

TIA.

On Sep 25, 5:01*pm, Joe Cool <joecool1... (AT) live (DOT) com> wrote:
Forgot to mention that I goggled this problem and did not find a
solution that helped.

Joe Cool (joecool1969 (AT) live (DOT) com) writes:
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.


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 (AT) sommarskog (DOT) 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

On Sep 25, 5:54*pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:
Sorry, didn't properly describe that. On the server properties window,
on the Connections page, there is a checkbox that is labelled "Allow
remote connections to this server".

Thanks, this was the problem. TCP/IP was not enabled. Once I did I was
able to connect from my notebook to the VM.