I was hoping someone with Windows 8.1 (RTM) has possibly seen this issue, as I am not 100% fluent yet with Windows 8.x... If I reboot my machine it can see my unRAID server (5.0) fine, over time however, if trying to browse it \\HADES it just throws a "the Network path was not found" error. puTTY connects fine from windows 8.1 as does the browser, it is only browsing the machine. I tried turning off Windows Firewall as well, but it did nothing, any thoughts would be greatly appreciated, its rather frustrating

In the FWIW department, I've got a Windows 8.1 machine, and although it's not my main system, I HAVE used it quite a bit with UnRAID ... and have NOT seen this issue.

 

In the FWIW department, I've got a Windows 8.1 machine, and although it's not my main system, I HAVE used it quite a bit with UnRAID ... and have NOT seen this issue.

 

I don't think its Windows 8.1 issue, I just think I have something set somewhere messing with it...

 

I can ping the machine fine at all times and I can browse to it via IP it appears at all times, but via machine name no luck.

I've seen other setups that had the same issue -- I suspect (but have not confirmed) that it has something to do with the router's client table.  Most commonly, it happens after UnRAID has been rebooted (or shutdown and restarted).  A reboot of the client system has always fixed it in my experience.

 

The simplest "fix" is to use a static IP for your UnRAID server and simply access it via IP (An "UnRAID" shortcut on your desktop -- or a mapped drive --  is handy for this).

 

I had this issue with 1 out of 3 Windows 8 boxes in my house.. none of them were on 8.1

 

I never actually managed to resolve it and just used the IP address from that particular PC.  The other two PC's had no issues at all.

I've seen the same issue on both Vista and Windows 7 boxes as well -- as BetaQuasi noted, using the IP address fixes it ... and to ensure that it ALWAYS fixes it, it's best in those cases to use a static IP for the UnRAID server.

 

If the problem boils down to the Windows machine connects/browse via IP and not by name, double-check you unRAID's "Settings" -- "SMB" using the webGUI. It should be set to "Local Master" and the same Workgroup as your Win8 box.

 

This type of problem can also be fixed editing Windows' HOSTS file usually located in C:\Windows\System32\Drivers\Etc folder.

 

And I agree, unRAID should be either on a DHCP reservation from the router or internally fixed IP so it doesn't change.

I have something similar. On my windows 8 laptop the unraid server doesn't show up in windows explorer in the network section even though both the win 8 laptop and the unraid server are in the same workgroup and the unraid server is local master.  If i type the server path into windows explorer (I.e \\tower) it finds it without issue and shows all the shared folders. Its the only computer on my network that has this issue....

 

my unRAID server is static, I will see if the other solutions help out. Using the IP is fine, just a pain for people non-computer friendly since they can't just click the network->MachineName...

Delete any saved credentials.

Delete any saved credentials.

 

Not sure I follow... on unRAID or windows?

On Windows.

On Windows.

 

My shares are open on my network, so no saved credentials. That being said, my server comes back fine if I reboot unRAID first, once I reboot my PC though the same thing occurs again. So basically this is the full run down:

 

unRAID reboot after PC is on:

\\HADES works

\\IPADDRESS works

ping HADES works

puTTY HADES works

 

PC Reboot AFTER unRAID in on:

\\HADES fails

\\IPADDRESS works

ping HADES works

puTTY HADES works

Is local master set on unraid?

Could there be any issue with Win8 running an advanced version of SMB that isn't talking to the lower forms (versions) of SMB? Don't get me wrong, I'm sure MS has our best interests in mind, but......just sayin'

 

 

There's a hostname issue that seems to show up as soon as static IPs are set: http://lime-technology.com/forum/index.php?topic=28977.0

I think I was having your same issue. It replicated itself a little differently. I could access it most of the time from my windows 8, but it would NOT work from anything non-windows (mac, android, etc) by hostname.

 

My solution turns out that my router wasn't recognizing the hostname. I setup a static lease in DDWRT and the issue 100% went away.

 

Static leases take the MAC address and assign a hostname = ip address. It is a very simple if you have dd-wrt (go to services->services), enter mac,hostname,ip, client lease time->hit save, then apply settings (weird, but it makes you do it in that order or it wont save on my build)