Can't resolve servername on local network

I've just installed a new Windows Server 2008 R2 Hyper-V. I can connect to the remote desktop fine if I type in the ip-address but when I type the name of the server I get an error. Also, when creating a network map in Win7 I don't see the server showing up. All the other pc's and servers show up fine. There is no domain, it's just a workgroup and all pc's have the 'WORKGROUP' name and the TCP/IP NetBIOS Helper service is running on the server.

What's the reason that a servername cannot be found?

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : hyperv1
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
   Physical Address. . . . . . . . . : 00-1E-0B-8F-56-D6
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b1ce:ca74:5968:8f26%19(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.140(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 318774795
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-71-F1-9B-00-1E-0B-8F-56-D6
   DNS Servers . . . . . . . . . . . : 192.168.0.144
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{69A27254-895C-4FBB-916E-9C75C8BA9038}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #17
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 17:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:1879:36e8:3f57:ff73(Preferred)
   Link-local IPv6 Address . . . . . : fe80::1879:36e8:3f57:ff73%21(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

What does it resolve to in DNS? A Hyper-V server, by default, won't have file sharing enabled in the firewall and thus NetBIOS based name resolution isn't going to work.

Ok, I added an entry (vhost.local) in the dns and now I can connect to the server using remote desktop. Do I need to change the computername too? It's still on hyperv-1.

@ZippyV: Probably a good idea. You'll run into all sorts of wierd quirks if the underlying DNS name doesn't agree with the computer name, because of the way the Hyper-V tools verify they're talking to the genuine host.