Hello, I am new to the community and recently setup my first unraid this past week. I Have 2x 2TB drives one being the parity drive. I have tried both the Local Master as on and off but with the same results.  Basically when I try to transfer from my Win7 Laptop w/ wireless N a large file, or even the windows backup it fails and gives the following errors both when using the name (Tower) or the ip-address:

 

There is a problem accessing \\192.168.0.160\Storage (Or \\Tower\Storage)

 

Make sure you are connected to the network and try again

 

When attempting a windows backup from my laptop it gives me this error:

"Windows backup encountered an error when accessing the remote shared folder.

Details: The network path was not found."

 

Another issue is just randomly trying to access the unRaid Server after it has been stalled sometimes i get:

"\\Path\to\shared is currently unavailable"

 

I do not have a cache drive, nor any advanced user security, which I do plan on implementing as soon as i get all my stuff transfered. I have transfered over following some of the instructions before enabling parity, then added parity drive and everything has checked up.  The only issue it seems is that sometimes the netbios or something seems to have it disconnect from the network and make these large transfers fail.  It also happens from a Vista Desktop computer that is hard wired to GigE.

 

I am wondering if there is anything I can do to make this be more stable because I did plan on unraid on storing my media for XBMC, as well as hold all the backups from all the computers but right now it seems to disconnect itself or they seem to have issue talking to unraid reliably.  Not sure if I installed too many packages from unMenu or anything like that.  So far I have not installed sabnzbd or sickbeard yet but that is on my to-do list.

 

Any tips for how to setup user security to avoid any problems with backups and xbmc I would also appreciate, but I really would like to know why these errors keep coming up from all different scenarios of different computers trying to send large files to the unRaid Server. Please ask any questions and i can provide hardware specs or screenshots or whatever is needed to diagnose this. I also am going to get upgraded version, so if that will do it, I just need to know, but i got plenty more to transfer and plenty of big files so that is a biggie right now.

 

Edit:

A couple of notes, The same large file was able to get transfered from win7 laptop to vista desktop no problem wirelessly, so its something with unRaid.  Then I was finally able to get this 4.5gb file to take from desktop to unraid while hitting the refresh directoy on a browser window that was browsing the uNRaid, not sure if that had anything to do with it, it was annoying but it didnt "freeze up" like the dozens of other times I had attempted.

There is a problem accessing \\192.168.0.160\Storage (Or \\Tower\Storage)

 

Make sure you are connected to the network and try again

 

Sounds familiar. I replaced my router (and probably some cables during that) so solve the problem.

 

You could connect unraid and your PC/Notebook directly or with a separate switch and fixed IPs. If it works, try to replace the router.

 

 

 

Is your server locking up and requring a forced reboot when this issue occurs?  Mine was and I had to disable the onboard nic (Realtek) and use a slot based card.  Since I did that, haven't had a single problem.

The server does not just lockup completely, basically I can hit the "Try again" button and it starts again and it will come up with the same error.  For some reason I dont think its the router since I was able to transfer just fine between laptop to desktop. It was just from Laptop to unRaid, or desktop to unRaid that had the issue?    I also swapped out the network cable to unRaid with same results, even installed a cache drive with the same results.  I have not tried it with a switch, but for example from Laptop to unRaid its going wireless. 

I am attaching a screenshot of what it looks like, that comes up and you can hit try again, over and over and over and over until eventually it attempts it again, but it seems like its not finding/recognizing it for some time causing it to error, then when immediately trying again it normally doesnt work, it has to be a little while before resuming.