Hello All,

Not sure if this is the right forum group, but the problem appears to be on
the client side;

I have 2 Windows 7 installs (Pro) on my network, and neither one of them can
connect to SQL Server 2005 (which is installed on my Win2k8 domain server).

I get a return message that says "SQL Server does not exist or Access Denied".

One of my Win7 installs is running in a virtual machine on Vista Ultimate.

The Vista host connects with no problem, but the Virtual Win7 install will
not.

I also have a stand alone Win7 Pro install and I get the same error message...

I have a Win2k and XP virtual machine on the Vista host that both connect to
SQL Server via DMO with trouble.

As a side note, the Win7 RC connected with no problem. This is the RTM
version that is having trouble.

I have opened and even completely turned off the firewalls to no avail.

Anyone have any ideas?

Thanks.

Gary Bouchard (GaryBouchard (AT) discussions (DOT) microsoft.com) writes:
What protocols are enabled on the client and the server? (Use the
SQL Server Configuration Utility to find out.)

Are you able to ping the server machine from the Win7 machines?

--
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
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erland,

I have both TCP and Named Pipes set on the server, and have switched
recently to TCPIP only. doesnt make any difference.

Yes, I can ping the server from both the Virtual PC's and from the
standalone, can open the Network icon and see all the machines on the
network, and access them from both the standalone and virtual pc's.

I have the software firewalls turned off inside the network, so I dont
believe that it is being blocked... also turned off my Trend firewall inside
the local segment.


"Erland Sommarskog" wrote:

Gary Bouchard (GaryBouchard (AT) discussions (DOT) microsoft.com) writes:
I guess that when you connect, you connect by name. Have you tried to
connect by the IP-address?

Also is the instance you are connecting to listening to 1433 or a dynamic
port?

--
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
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Actually, I went into the registry and changed the listening port, and
restarted the service, and when I did that, it put the port to 1095, and I
was able to connect.

Thank you for your help!

"Erland Sommarskog" wrote: