v4.1 & Network Drives, bug?

[mattrowe]

Hi folks,

I recently upgraded to v4.1, and Subsonic no longer recognizes my shared network drive. I keep seeing "No music folders found. Please change the settings."

I've verified that my server (Windows 7) is connected to my network drive, and that it can read from it.

Is anyone else experiencing this issue?

[DamnedBrit]

I store my music on a shared network drive and it worked fine under 4.0.1. Now all I keep getting is 'No music folders found. Please change the settings.'

I am now without music at work

Am trying to see if I kept an older copy so I can downgrade and get back to listening to music.

[DamnedBrit]

Well I had vague recollections of trying to get this to work last time and I believe it all cocked up because the installer removes the old service and creates a new and I didn't take a note of how it was running before the install.

But I did get it to work. I have a user account with the same login/password on the MP3 server and on machine running Subsonic (can't run Subsonic on the MP3 server because it's hard-coded in the installer and somewhere inside the program to use the C: drive as the root drive. Install Windows to anything but C: and Subsonic fails to run (or fully install)).

The user account can access the shared MP3 folder without issue from the Subsonic machine. Subsonic is set in the Services applet to login as the user (and not Local System Account).

Then in Subsonic, when you go to add the folder to the library, don't try using a drive letter mapping (because the service may not see it) but instead use the UNC path. So while my user on the Subsonic computer can 'see' M:\Music, I set Subsonic up to use \\mp3server\m$\media\music instead (you may need to use / instead of \ depending on your setup).

That worked for me, I'm now back to listening music at work.

EDIT: Oh yeah, this was reinstalling using 4.0.1. I'll try the same stunt again when I'm at home to see if it works on 4.1.

[DamnedBrit]

Upgrading to 4.1 did break the music folders until I set the Subsonic server back from using the LSA credentials to using the shared user account that existed on the MP3 server and the Subsonic host server.

And the install did 'lose' the different port that I had Subsonic running on.

[armedmonkey]

Are you saying you somehow specified a different account for the service to run on? My problem is that the share I want to use:

- doesn't have a network drive to it from the System account
- requires credentials to access.

[DamnedBrit]

Are you saying you somehow specified a different account for the service to run on? My problem is that the share I want to use:

- doesn't have a network drive to it from the System account
- requires credentials to access.

Hi ArmedMonkeyy,

No what I did was create an account with the same username and password on both the PC where I was running Subsonic as well as the PC that had the share I wanted to connect to.

On the PC that had the share I added the new account to have rights to read the share (I also gave it write rights so I could upload as well).

On the PC with Subsonic I set the Subsonic service to run with the new account credentials and set it to run.

I was then able to login to the Subsonic web interface and set the Music folder to use the share with a UNC naming convention (e.g. \\myserver\media\music) and it was able to browse the folders and build the library.

Hope this helps,

Thanks

Damned Brit

[armedmonkey]

I should have thought of that, seeing how I tried everything *BUT* that.

Thanks very much DamnedBrit. Works!