-2

I cannot ping the Windows 2008 R2 server by hostname from Windows XP Home machines, but I can ping it from Windows 7 Ultimate machines. I already disabled ipv6. I need to access a shared folder: \server\a

All computers are on the same local network, there is no DNS in use. Just every computer in the same Workgroup.

Any ideas why?

EDITED: I have heard that the problem could be that different systems chose different Master browsers.

theSpyCry
  • 129
  • 1
  • 2
  • 10
  • Can you ping it by IP address? – MDMarra Dec 27 '12 at 18:40
  • yes i can ping it by IP adress – theSpyCry Dec 27 '12 at 18:43
  • perhaps another topic is, the server has a dynamic IP provided by local DHCP. As all computers should only access WebServices on server/Services.asmx I do not know if it would not be a problem – theSpyCry Dec 27 '12 at 18:45
  • If you can ping it via IP address. You should flushdns (ipconfig /flushdns) and see if it works now. – davidb Dec 27 '12 at 18:46
  • no, cannot find the hostname. But it is on the LAN with no DNS server or anything. – theSpyCry Dec 27 '12 at 18:47
  • How is it supposed to work? By what mechanism are you expecting the machine to get the IP address from the hostname? – David Schwartz Dec 27 '12 at 20:08
  • Why do you have a server with DHCP assigned address and why don't you have DNS? Are you deliberately trying to make things harder for yourself? – John Gardeniers Dec 27 '12 at 22:05
  • i can imagine that with no DNS server i cannot translate the hostname to an IP address. But it works e.g. on XP machines where all peers are equal. So i supposed it could work like this: a machine sends a broadcast and asks who has this hostname, then the right one responds. – theSpyCry Dec 28 '12 at 09:57
  • @DavidSchwartz isn't that NetBios ? – theSpyCry Dec 28 '12 at 10:45

1 Answers1

6

Judging by your comments that you aren't using DNS, your problem is NetBIOS name resolution.

NetBIOS over TCP/IP is disabled in Windows Server 2008 R2 by default, however it is the only way for XP to handle local name resolution without a DNS server. This problem does not exist for newer OSes on your network, because they use LLMNR/WS-Discovery, and not NetBIOS.

You can enable the NetBIOS responder in the WINS section of the IPv4 network settings: enter image description here

You also need to make sure that the Computer Browser service is started and that Windows Firewall is allowing inbound IPv4 NetBIOS traffic.

user1686
  • 10,162
  • 1
  • 26
  • 42
MDMarra
  • 100,734
  • 32
  • 197
  • 329
  • I have enabled it but still no luck :/ – theSpyCry Dec 27 '12 at 18:53
  • 1
    See my last edit. You're also going to need to make sure that the computer browser service is started and that Windows Firewall (if enabled) is configured to allow NetBIOS traffic. – MDMarra Dec 27 '12 at 18:55
  • What do you recommend as the most elegant way of losing this problem? Should I make the computer a wins server or some other who would care of translating names to ip addresses? Or a domain controller? Or it is an overkill for this purpose – theSpyCry Dec 27 '12 at 19:40
  • 1
    Use DNS. WINS is a dying (dead) technology. – MDMarra Dec 28 '12 at 15:20