Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to set up a home Linux server (running Arch Linux ARM on a Raspberry Pi), and I can't seem to get my Windows desktop machine to recognize it via hostname (in this case "whitey"). I have it set to a static IP address in my router (at, and (in theory), my router is functioning as a DNS server. When running "ping whitey" on Windows, I get

Ping request could not find host whitey. Please check the name and try again.

However "ping" works. What's curious is that both my Linux laptop and, curiously, a Linux virtual machine running on the Windows PC can find my server (using "ping whitey"). This leads me to believe that the issue lies on the Windows side, and not with the router or the server.

Any ideas?

I've tried

ipconfig /flushdns

as well as manually setting my router as the DNS server for IPv4 addresses.

share|improve this question

migrated from Dec 8 '13 at 16:48

This question came from our site for system and network administrators.

What gives you hostname whitey on a Windows cmd ? How did you configure your router to act as DNS server ? – Levans Dec 8 '13 at 17:20
@Levans I'm not sure what the first part of your question is asking. Windows can't find "whitey" in any aspect. As to the second part, I didn't need to do anything far as I can tell my router does it automatically if I turn on DHCP and I don't specify a different DNS to use. – Hounddog Dec 8 '13 at 17:41
I meant, what is the output of the command nslookup whitey in a windows CMD ? (sorry, I mixed command names) – Levans Dec 8 '13 at 17:55
Output is: Server: Address: *** can't find whitey: non-existent domain – Hounddog Dec 8 '13 at 17:58
@Levans: Installing Samba (per strange walker's suggestion) got me working. Thanks for your help! – Hounddog Dec 8 '13 at 18:00
up vote 3 down vote accepted

Windows uses DNS to resolve FQDN names - for example.

In your case, whitey is the NetBIOS name and DNS have no (and shouldn't have) knowledge of it.

I'm not a Linux expert, but as far as I know your Linux server needs Samba in order to be able to broadcast its NetBIOS name across Windows machines.

share|improve this answer
Installing samba solved it! Thanks!! – Hounddog Dec 8 '13 at 17:59

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.