Bug 6631 – IP Adress from SqueezeCenter

Bug 6631 - IP Adress from SqueezeCenter

Summary:

IP Adress from SqueezeCenter

Status:	CLOSED REMIND

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Windows Installer
Version:	unspecified
Platform:	PC Windows Server 2003

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-01-17 02:34 UTC by Stefan Zemlicka
Modified:	2008-12-15 13:23 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Zemlicka 2008-01-17 02:34:32 UTC

Hi,

There is no chance to change the IP. Backround of this is following:

I have a Server running W2k3 with 2 Network Cards. One have the 192.168.1.50 and the other one have the 51. On the server is twonkyvision running at 192.168.1.51 Port 9000. The SqueezeCenter is running now at 192.168.1.50 Port 9000. The only chance to do this is to configure twonky at the second interface. Twonky can be configure. Squeeze not. I miss the option to configure the Software to a dedicatet network IP.

I use the latest SqueezeCenter 7.0 Software from 16.1.08.

Comment 1 Michael Herger 2008-01-17 03:57:30 UTC

squeezecenter.exe --help

will give you the full bunch of options. Among others:

    --httpport       => Activate the web interface on the specified port.
                        Set to 0 in order disable the web server.
    --httpaddr       => Activate the web interface on the specified IP address.
    --playeraddr     => Specify the _server's_ IP address to use to connect
                        to Slim players

Did you try any of these?

Comment 2 Stefan Zemlicka 2008-01-17 04:37:02 UTC

Hi,

Thats fine. I do not known that. I use the Software in Windows Service Mode. There is no way to change it easy in the application. But you are right. It's not a bug.

thx