Hi I think we have all had the same issue with slimserver. on the pc running slimserver, the web interface on 127.0.0.1:9000 is accessable.
however assuming the pc running slimserver has address 192.168.2.3 then entering 192.168.2.3:9000 in a web browser elsewhere on your lan results in the page timing out. my Lan uses addresses on 192.168.2.x most other home routers will use something different see http://www.duxcw.com/faq/network/privip.htm for details. On the server configuration page of the web interface (local) we have -------- home servers settings security BLOCK INCOMING CONNECTIONS This option allows you to enable blocking of incoming CLI and HTTP requests by source IP address. Do Not Block -------- is selected but still we are unable to connect to the slimservers web interface. cure1 (untested)(from localhost:9000 in your webbrowser) This is probably a bug with the default config set to block but the browser sets this to do not block by default when update settings is run it ignores this setting as aparently its unchanged! (someone want to try changing this to block rebooting the server then changing the value to do not block and rebooting again) cure2 (tested) I run ubuntu but this will apply to windows too, what we need to do is edit the prefs file for slimserver the name might be different on windows but the contents should be the same or similar (ubuntu) sudo gedit slimserver.pref actually something seems a bit wrong here because I have 2 places with slimserver.pref the above one is in my homefolder and is the one i edited to get the remote web interface access initially. There is a further version in /etc/slimserver/slimserver.pref I have a feeling that if I start slimserver from my account the prefs file used will be from my account and if the daemon starts slimserver it will use the version in /etc/slimserver/slimserver.pref (pauses to reboot the server) ok after a couple of reboots I think i am correct in thinking it matters who starts the server if it's me it uses my personal config and if its started automatically its going to use the etc/slimserver/slimserver.pref I think thats a feature :/ --- MMMMixType: 0 MMMSize: 12 MMMStyle: 0 MMMVariety: 0 MMSHost: localhost MMSport: 10002 MusicMagicplaylistprefix: "MusicMagic: " MusicMagicplaylistsuffix: '' allowedHosts: 127.0.0.1,192.168.2.4,127.0.1.1 ---.... the above is the start of my slimserver.pref file the important line is allowedhosts. as you can see I have added 192.168.2.4 (the address of my laptop) to this line and now It can connect to the webinterface of slimserver. You can use a wildcard so 192.168.2.* allows every PC on my lan access to the server interface. The change doesn't take place straight away if you edit slimserver.pref the changes will not take place until the server is restarted. It also takes a minute from the system being rebooted and presenting the logon screen before the slimserver service is ready for incoming connections. When I was running ubuntu dapper there wasn't a problem however on Edgy all versions seem to block remote access by default. (If I am right about cure1 then your config file is set to block by default and this method just gives exceptions to the block rule) cure3 alternative method to impliment cure2 (localhost:9000) ------------------ on home server security in the allowed addresses enter the following 127.0.0.1,192.168.2.*,127.0.1.1 and then reboot the PC running the server and then it should have this information in the box when you connect locally or remotely remember the server will not recognise the change before a reboot has taken place! notes: This has been tested on the unstable debian version cure1 and 3 need to be applied on the pc acting as server cure2 can be applied remotely. if you have openssh server installed you can open a terminal on a remote PC and enter ssh [EMAIL PROTECTED] -X (your username = username you use locally on the server IP Address here is my IP address for myserver change it for yours -X must be uppercase and allows you to run programs on the server with the GUI on your remote PC (also if you port forward port 22 in your router you can access the PC from anywhere on the internet) Openssh server is available for windows but you need to have set up an Xserver on your windows box to be able to export the display to your remote PC (this is part of cygwin which I don't use and can't help with)otherwise you are limited to command line tools if your server runs on linux you can use ssh and a command line tool such as nano. (for example you are on a windows box your slimserver is running on top of ubuntu. you have openssh client installed on the windows box so run cmd and then ssh [EMAIL PROTECTED] followed by sudo nano /etc/slimserver/slimserver.pref with Linux you can use XDMCP to login remotely, if you install xnest you can have your remote desktop in a window, you need to have enabled remote login on the PC you want to connect to. VNC is also an alternative. ssh is the fastest most responsive and secure way of connecting remotely. VERSION INFO SlimServer Version: 7.0a1 - 11542 - Debian - EN - iso-8859-1 Server IP address: 192.168.2.4 Perl Version: 5.8.8 i486-linux-gnu-thread-multi MySQL Version: 5.0.24a-Debian_9ubuntu1 -- blackest_knight ------------------------------------------------------------------------ blackest_knight's Profile: http://forums.slimdevices.com/member.php?userid=10442 View this thread: http://forums.slimdevices.com/showthread.php?t=32547 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
