I have a strange one. I have a Windows 7 Home Premium notebook which has no problems access

\\tower\sharename

or

http://tower/

. However my Windows 7 Ultimate PC can not access it via the domain name. However it will access it via its IP access. SO

\\10.0.0.245\sharename

and

http://10.0.0.245/

both work, but

\\tower\

and

http://tower/

do not work. Any clues as to what might be up with my windows 7 Ultimate PC. As my notebook is working OK, I assume unRAID is OK. Note the Notebook and the PC are on the same workgroup and can see each other.

Make sure unRaid is in that same workgroup.

unRAID, my notebook and my PC are all on the same network. But only the notebook and see the unRAID server via its name.

right click on my computer and click properties. what does it say under Domain:

When you say "all on the same network" I'm assuming you meant unRaid is assigned to the same "workgroup" as the others.

 

Try opening a command window and type: ping tower

Does it reply with it's IP?

 

What about: arp -a

Is the Tower IP and MAC listed?

 

Try doing: ipconfig /flushdns

then: arp -d *

 

Do the above ping again and see if it shows.

The Notebook, PC and unRAID are all on a workgroup call "workgroup"

 

ping tower from the notebook returns IP address of 10.0.0.245

ping tower from the PC returns "ping request could not find host tower"

ping 10.0.0.245 from the PC returns "Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)"

arp -a from the notebook returns "10.0.0.245            f8-d1-11-02-e0-ab    dynamic"

arp -a from the PC returns "10.0.0.245            f8-d1-11-02-e0-ab    dynamic"

 

I am really scratching my head with this one.

Is this name resolution issue only with Tower on that pc?

 

Post ipconfig /all for both win7 systems. Also confirm unRaid is set as master browser.

The problem is only with the PC. Here are the ipconfigs for both

ipconfig_notebook.txt

ipconfig_pc.txt

Thanks for the pointers everyone. I found the subnet mask was wrong on my PC. I corrected it and now it is working. Very strange that is has not caused a problem before. Once again. Thanks

The most likely reason it did not see it with a wrong subnet mask is the broadcast address was wrong.

IP networking will broadcast on the highest ip  (ie 192.168.1.255 with a mask of 255.255.255.0) of your mask was 255.255.0.0 then is would broadcast on 192.168.255.255. The broadcast is looking for other pc on the same subnet. A DNS server on the network would return those not needing to broadcast for the LAN.

Networking is fun so they tell me.

John

Thanks for the pointers everyone. I found the subnet mask was wrong on my PC. I corrected it and now it is working. Very strange that is has not caused a problem before. Once again. Thanks

 

You beat me to it. Glad it all worked out.