• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1950
  • Last Modified:

cannot connect to SQL Server housed in Hyper-V container

We have a Hyper-V system running a Windows Server 2008, within a Windows Server 2008 box. the SQL Server cannot be accessed from the outside, not even within the box running the Hyper-V.

The credentials are correct but we can't even see the SQL Server instance from SS Management Studio.

Strangely enough, the SQL Server is the backend of an MS Access frontend. However, it performs horribly slow.

Any thoughts on why we can't connect? Thanks!
0
ironpen45
Asked:
ironpen45
  • 3
  • 2
1 Solution
 
AeridenCommented:
Can the Hyper-V Guest running SQL Server connect to the outside world (to other servers in the LAN, to the Internet)?  Is the Windows Firewall setup to allow TCP 1433 through?  Can you connect to SQL Server from the same machine running SQL Server using SQL Management Studio?  If so, what protocols are being used (e.g. Share Memory, Named Pipes, TCP)?  I generally recommend making sure TCP works.
0
 
ironpen45Author Commented:
I don't know if the Hyper-V guest serves other functions besides housing the SQL Server instance.

I am able to connect Management Studio from within the Hyper-V guest. I am also able to connect to another SQL Server instance within the machine where the Hyper-V guest runs on.

I will need to recheck the firewall settings and protocols and get back to you. Thanks.
0
 
AeridenCommented:
By default, firewall settings usually don't interfere with local connections (via (local), localhost, or the local computer NetBIOS name).  I know this is overly obvious (so sorry! :-)), but is the SQL Server windows service running?
0
 
ironpen45Author Commented:
yes, its running for sure. i can connect to it (with its own Management Studio). an MS Access client also connects to it, but horribly slow.

i restarted the server, the services, etc. but no improvement.
0
 
AeridenCommented:
Check the SQL Connections settings on the SQL Server.  To do this, open SQL Management Studio on the SQL Server.  Right-click on the server and select properties (on the left pane).  Once the server properties dialog box appears, click on Connections on the left pane.  Check the settings.  Normally I have 0 (unlimited) maximum number of concurrent connections, I don't use a query governor, Remote connections allowed with a 600 second query timeout, and I don't require distributed transactions for server-to-server communication.
0

Featured Post

2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now