I searched and read through all the threads I could find on windows network, unc path, etc. issues here on the forums.  And did a google search to see what I could find elsewhere.  Hoping someone has further suggestions:

 

unRaid box has been configured and working well for many months, picked up fine by my winXP and win7 computers, no problem adding directories from XBMC on pivos xios either.

 

HOWEVER, I recently installed crushftp on the windows XP box because I desire to utilize a sftp service to make a share folder on the unRaid box available to several colleagues for storage/backup.  crushftp is working fine, can login and see any files/folders shared on the XP machine.

 

HOWEVER, crushftp cannot seem to see or find the unRaid box or shares.  I mapped the unRaid folder as a network drive on the XP machine, but apparently MS does not make mapped network drives visible to services, which crushftp runs as. 

 

I also tried specifying the direct UNC path to the unRaid folder within the crushftp virtual file system (add shared files/folders) section as was suggested by crushftp support, with no success.  I tried \\tower\directory    //tower/directory    smb:\\tower\directory    smb://tower/directory.

 

It seems that crushftp simply can't see the unRaid box or shares.  This sounds similar to problems others have reported with unRaid not being visible to explorer on windows machines.  Except that mine is and pretty much always has been. 

 

Any other thoughts?

 

Two minutes of googling found this.

Sure, been there already, tried it, for whatever reason didn't work even though the tool said it executed successfully.

 

After lots of experimenting, it seems crushftp didn't like a space I had in part of the path. Windows and the pivos didn't seem to care. Guess that's a UNC no no.

Some applications can parse spaces in UNC if you surround the entire thing in double quotes. "\\server\share name"

Thanks for the tip. I'll try it out and see if crushftp accepts that just so I'll know.