MySqueezebox.com & Squeezebox Server

[garymc]

---

garymc wrote:

I can't help here other than to point out that LMS (and earlier SbS versions) does work on network shares. I'm using network shares on two different machines currently with no issues.  So your problem requires more diagnosis as it is not as simple as LMS no longer works on network shares in general.

---

Just tested from scratch. LMS 7.7.1 running on Win7(64) desktop.  browsed to a network share (mapped to drive letter p:/) selected it, did a clear and rescan and all was picked up and plays ok.  I'm wondering if this is not a NAS issue vs a LMS issue.  I don't doubt the problem but just wanted to be clear that waiting for a logitech fix may not be the way to go if this is NOT actually a problem on the logitech end.  Anyhow, just my 2 cents.

[kuben72]

I have tried 7.7.x on a Windows 7, a Windows XP and on Windows WHS and none of these can access a networkshare.

[CatLogitech]

---

gavd wrote:

Hello Cat,

I see you are from Logitech. Could be possible to get an explanation why we are not able to use network shares? Do you have any workaround? Can we expect that it will work in a short time (new release)? Also if you are not planning to make it possible, some reason would be appreciated.

Gr.

Gustavo 

---

The Squeezebox Development team are always working on software updates and you can always try the nightly versions from here.

http://downloads.slimdevices.com/nightly/

That being said Logitech employees cannot comment on any release date of products, software or services.

Have people checked their Routers and opened the ports we use, just to make sure nothing is being blocked as well as checking the firewalls on their network shared devices?

If you have a request or a bug you can post a bug report at http://bugs.slimdevices.com . If it is a feature request you need to set the severity to Enhancement. Just make sure you search the data base their first to be sure it has not been filed already.

[gavd]

Hi,

The bug is already reported and the answer is "I don't have it in my computer, thus the bug doesn't exist"... it comes in line with some other assertions in this thread as well...

I can accept that employees cannot comment on releases but you are given support through this foro, thus you are at least trying to help people with problems, something that the development team is not doing. That is valuable and appreciated from you.

Regarding your comment about ports, could you please elaborate somehow? Which ports should be open? I cannot find any information about it. The "Diagnostics" tab of the Control Panel indicates no problems with ports 3483, 9000 and 9090 and those ports are open as well in the server with the media files (the share in the network)

Thanks in advance,

Gustavo

[CatLogitech]

It is hard for the engineers to reproduce things if it is not happening in their labs. Usually if a bug gets enough votes it will get more attention. You can also check at our third party forums at http://forums.slimdevices.com as well since a lot of people go there especially for custom setups.

Depending on the share device, it may have a firewall. The server is only reporting the ports on the Server and if it can get to mysqueezebox.com.

3483 TCP/UDP

9000 TCP

9090 TCP

9092 TCP

[gavd]

Ok, I found the problem. I need to say, I have my thoughts about your developers and (specially) your testing teams...

It is really simple: if you use the option "Startup Option" - "Automatically run at system start" (from the "Status" tab in the "Logitech Media Server Control panel") you CANNOT use a network share. Set it in "Automatically run at login" and everything works properly.

It seems to me the first Test Script that I would make if I was in your testing team. And the first thing that I would test if I was one of your developers.

In any case, I hope this will help somebody here.

Gr.,

Gustavo

[CatLogitech]

Hello Gustavo,

Someone else posted that, but I wanted to make sure everything else was correct first.

If you have that bug number add to it what you have found and also post the bug remote here so others can follow it.

[over-the-hill]

Hi Cat

How do you do a clean install on a Mac?

I have a seperate music folder with mostly FLAC files as well as an iTunes folder. I just check the box in the server settings for iTunes.

[GeminiAlpha]

Could it be that a share doesn't work, but only a full UNC-path must be configured? Ie, my share to the network drive is drive V: at pc start up initiated by a batch file containing: "net use v: \\NetworkSpace2\myname\MP3\Albums\"

but I have to configure the following UNC path: \\NETWORKSPACE2\myname\MP3\Albums\ in "media server control panel" as the place where my media files are stored.

BUT  I've still a problem because I need to configure a userid an a password somewhere to get access to the network drive/path \\NETWORKSPACE2\myname\MP3\Albums\ because it's secured to block  other network users.

how can I overcome MY problem?

[earthling]

The problem is that when you start something as a service, it cannot access network shares that are created under user credentials.  In essence, the user credentials that the service uses at boot which are probably like 'network service' or something like that do NOT match the credentials you use as a user when you log in, even if you have the machine set to automatically log in (no user/pass).  So, you have to make the credentials match.

You can either set the service with the right credentials and make matching credentials on the NAS, or you can use the sysinternals tools to map the drive (net use) while under elevated priviledges to begin with.

For this hack you will need SysinternalsSuite by Mark Russinovich: http://technet.microsoft.com/en-us/sysinternals/bb842062.aspx

Step one: Open an elevated cmd.exe prompt (Run as administrator)

Step two: Elevate again to root using PSExec.exe: Navigate to the folder containing SysinternalsSuite and execute the following command "psexec -i -s cmd.exe" you are now inside of a prompt that is "nt authority\system" and you can prove this by typing "whoami". The -i is needed because drive mappings need to interact with the user

Step Three: Create the persistent mapped drive as the SYSTEM account with the following command "net use z: \servername\sharedfolder /persistent:yes"

It's that easy!

WARNING: You can only remove this mapping the same way you created it, from the SYSTEM account. If you need to remove it, follow steps 1 and 2 but change the command on step 3 to: "net use z: /delete"

NOTE: The newly created mapped drive will now appear for ALL users of this system but they will see it displayed as "Disconnected Network Drive (Z". Do not let the name fool you. It may claim to be disconnected but it will work for everyone. That's how you can tell this hack is not supported by M$