Cannot create ODBC connection to Hyper-V VM using DNS Name, but can with IP

Category: sql server smodmo


Brian McGuigan, Software Architect, On2it Software on Sat, 05 Jul 2014 00:08:25

We have a Windows Server 2008 R2 machine running Hyper-V.  Inside which we have created a VM running Windows 7 called 'GEM-SERVER'.   It has an SQL Server Instance called 'GEMSQLSRVR'.  We used to be able to create a ODBC Data Source using 'GEM-SERVER\GEMSQLSRVR'.  Suddenly we have to use its IP address rather than its DNS Name.  We can connect using '\GEMSQLSRVR'. 

We have no idea what has suddenly changed.  I have enabled 'NetBIOS over TCP/IP' on the NIC's on both the Server and the Client PC.  It has made no difference.  I can Ping both 'GEM-SERVER' and  I can also RDC to both 'GEM-SERVER' and

 Anyone any idea what else to check?


yarkandstar on Sat, 05 Jul 2014 02:19:16

Just make sure it is not a typo in the question - you say you used to use 'SERVER\GEMSQLSRVR'. But your server name is 'GEM-SERVER'. Should it be 'GEM-SERVER\GEMSQLSRVR'?

Brian McGuigan, Software Architect, On2it Software on Fri, 11 Jul 2014 22:10:01

No that was a typo in the question.  GEM-SERVER\GEMSQLSRVR is what we are trying to use.  (I copied and pasted it to make sure that I made no mistakes.  But when I pasted it into this text control, it lost the "GEM-".)

It HAS worked successfully for years.  We recently had a meltdown of the O/S on the real server in which GEM-SERVER resides.  As a result of which we bought a new hard drive and re-installed Windows Server 2008 R2 on that.  Now for very strange reason the system cannot find

I've re-edited the original question, to ensure I don't confuse anyone else.

Brian McGuigan, Software Architect, On2it Software on Sat, 20 Sep 2014 03:59:47

Well I don't know what was causing the problem.  However re-installing the Windows 7 O/S on my machine cured it.