Slimserver 6.5 on Ubuntu edgy - port 9000 not enabled

[cfraenkel]

Hi

I've got 6.5 running on ubuntu, and it works fine accessed through localhost on this machine. But I can't get to it from any other machine on the network.

Nmap does not list port 9000 as an open port. How does one go about enabling the port?

[Mark Miksis]

The standard Ubuntu installation does not include any kind of firewall. Did you add one?

Also, on slimserver under Server->Security, you can configure which IPs are allowed to access the slimserver. However, the default is to not black anything. Did you change this?

Otherwise, it should "just work".

[cfraenkel]

No to added firewall. The linksys router is the firewall. I had slimserver running from a WinXp box in this same network with no problems getting to port 9000. Looking through synaptic, the only firewall package installed is iptables, and iptables shows no chains have been created.

Did not change anything on server->security (and just to make sure, I checked and it's still set to "Do not block")

All I've been able to google is numerous posts referring to ubuntu's "no ports enabled" policy - but none of them say how that's done or what to do to enable the ones you need. A port scan of the machine shows 3483 open, which appears to be the udp port used by slimserver. But 9000 is not open.

[Mark Miksis]

All I've been able to google is numerous posts referring to ubuntu's "no ports enabled" policy - but none of them say how that's done or what to do to enable the ones you need.

I'm petty sure that's referring to the fact the the default desktop Ubuntu install doesn't include any daemons that that listen on external ports. I'm don't think you need to enable anything when you manually install a daemon that does listen externally.

A port scan of the machine shows 3483 open, which appears to be the udp port used by slimserver. But 9000 is not open.

I'm no expert on nmap, but I know that it doesn't scan all high port numbers by default. Have you tried something like "nmap -p 9000 ip.of.the machine" to make sure it's really checking port 9000?

[Benway]

What have you got for the out of:

netstat -na | grep 9000

and

iptables -L -n | grep 9000

[cfraenkel]

Can't answer the previous two questions... I installed firestarter to enable port 9000. (go figure - put in a firewall to open a port) Port 9000 is now working.

This has partially fixed the problem. Now, the other machines on the network can see the slimserver web pages and winamp on the other machines can play the slimserver stream.

Now - the SB3 cannot connect.

a) It can't find the DHCP server (the linksys router)

and

b) If I give it a static IP address, the SB can see the server (it comes up with the network name) but cannot connect to it. It cannot connect to the squeezenetwork either.


Regarding a) - I've seen the other threads regarding linksys firmware upgrades causing exactly this problem, but I haven't upgraded the firmware (the SB3 was working fine as of a couple days ago), and I've an older WRT54G (v3) - the known linksys problem only affects v5 and v6, I haven't been able to locate any problems with the v3 version.

No clue why switching to the linux server software could break the SB's contact with the router.

[Benway]

The SB uses 3483 so open that as well as 9000(used by winamp+web gui).

The DHCP problem sounds completely unrelated. The connection of the SB to the network is seperate to the ubuntu box unless you were always using the ubuntu box for a dhcp server and didn't realise it (maybe the linksys passes on dhcp request to ubuntu etc...) in which case open up port 67.

[cfraenkel]

Just posting an update if anyone else runs into this.

To allow other machines to play access the slimserver on ubuntu, I had to install a firewall (firestarted) and open port 9000.

The DHCP problem now looks to be a problem with the linksys router. I installed the dhcp server on the ubuntu server and turned it off on the router and that problem went away.

I still can't get the SB3 to connect to either the slimserver running on ubuntu, the old slimserver on winxp, or slimnetwork. The SB3 connects to the network, and sees both slimservers ok, but when it tries to connect, it just goes to a blank screen. Pressing left arrow you get a "failed to connect to ...." error message.

[Benway]

Dont forget you have to open port 3483 for the SB