Your server setup

The airies mini was bloody cheap when it came out which is why Auralic discontinued it. You can pick one up with a 1TB HDD for about £300 at the moment. OK, that is more expensive than a Pi, but it is streamer, server, DAC etc all in one and is effectively bomb-proof.

1 Like

Is there Mac software that can stream from LMS?

Yeah both Squeezelite and Squeezeplay are available on Mac. You may also be able to use a DLNA bridge, if the Mac has a DLNA player (might be built in)

I just use the web interface to access LMS running on the desktop upstairs from my Mac.

I missed this. LMS is no longer working on my old Synology NAS, 213j I think. Is there an idiot guide anywhere about installing Docker ?

We had our router replaced and now the Pi in the living room (raspbian, desktop) can’t see the Pi server (piCore, headless) in network devices folder. The squeezeboxes can see LMS and both LMS and the picore web interface can be accessed from the browser. I set both Pi’s up with static IP addresses as before, and they were just reconnected to the new router without changing any settings on either Pi.

Any ideas from meatman tech-whizzes?

What are you expecting to see? Is it a samba share?

You may need to install winbind (sudo apt install winbind), as routers can use different services for device resolution.

Sometimes, typing the correct name into the address window works it out - it was there, but invisible!

Possibly check the Squeezelite settings on the raspbian Pi to see if it is looking for a fixed IP for LMS that is different to the current LMS IP?

Oh is it a SB player on the pi that can’t see the SB server?

No, actually the SB player on the Pi can see the server (well, LMS running on the server).

The server has samba enabled, but previously the server appeared as a folder under network devices (using the desktop GUI) and I could just drag files across. This has disappeared.

Nothing has changed on either Pi, the only thing that has changed is the router.

Did the old router have uPnP discovery runnning and the new one have it disabled, perhaps?

uPnP is the devil’s smegma by the way. If it turns out to be that I’d find some other way to make your piCore discoverable.

Just checked. uPnP is enabled.

Replacing the router hasn’t even fixed the issues we were having grrrrr

With samba shares, it’s normally best to actually mount the remote drive. Your /etc/fstab file is the place for this.

Ideally this would refer to the network name of the remote Pi. If badly configured, it might have the IP address. I’d check that.

Once it’s correctly in the fstab file, it’ll mount it correctly each time.

Is this stuff you know enough about or do you need a lot more help sorting it?

I know enough to get myself into problems and not more than that

Look up online how to mount a network share in Linux.

Basically you need to create a folder where the remote drive will be shown, and add the following to your /etc/fstab file

//SERVER/share /mnt/samba cifs username=user,password=password 0 0

You need the name of the server pi and the shared folder; /mnt/samba you change to the folder you created for the share to be shown on the remote computer, and obviously it’s your username and password on the server.

And do sudo mount -a to mount it, but with the above it’ll mount that every time you boot up

Thanks. Is “//SERVER” the host name or IP address?

Ideally it would be the name, like PiServer, although you could use the IP address

So, I couldn’t get the samba share to work, but I was able to connect (via the GUI) by SSH/STFP, by playing around with what i entered (it would only accept the IP address not host name) - not entirely sure what i did differently last time or why it is different now, but i was able to rip a cd and transfer across fine.

Yep, sounds like a standard Linux experience

1 Like