disputin wrote:
> There's nothing listening to port 9000. I'm not sure why moving LMS to
> port 9001 or 9002 would make a difference.
>
> telnet localhost 9000
> Trying ::1...
> Trying 127.0.0.1...
> telnet: Unable to connect to remote host: Connection refused
>
>
>
> SeanWith a stock SBS/LMS/UEML config, you'll only be able to telnet to port
9090 -- that's the CLI port. It's to be expected that the SBS http
server on 9000 should refuse a telnet connection.
You can tell what's on which ports using this script:
tcpview.sh:
Code:
--------------------
#!/bin/sh
netstat -n -A inet
lsof -i
--------------------
Run that via:
# sudo tcpview.sh
On my ubuntu box, that command returns this info that's relevant:
Code:
--------------------
slimserve 1675 lms 8u IPv4 9671 0t0 UDP *:3546
slimserve 1675 lms 11u IPv4 9672 0t0 UDP *:3483
slimserve 1675 lms 12u IPv4 9673 0t0 TCP *:3483 (LISTEN)
slimserve 1675 lms 25u IPv4 33554 0t0 TCP
192.168.0.198:3483->192.168.0.200:62899 (ESTABLISHED)
slimserve 1675 lms 29u IPv4 9681 0t0 TCP *:9090 (LISTEN)
slimserve 1675 lms 31u IPv4 9682 0t0 UDP *:42128
slimserve 1675 lms 33u IPv4 9695 0t0 TCP *:9000 (LISTEN)
--------------------
You can "see" slimserve has an active connection to my Transporter,
which is configured statically to 192.168.0.200 on my network. Port
9090 is the CLI; port 9000 is the http interface; port 3483 is the slim
discovery & control port. I'm not sure what ports 3546 & 42128 are for
here. Anyone have an idea?
Also, what is the state of your firewall?
# sudo ufw status
To me, it seems odd that the web interface isn't working while iPeng is.
iPeng communicates SBS/LMS/UEML mostly (I believe) via JSON over http
on port 9000.
------------------------------------------------------------------------
gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115
View this thread: http://forums.slimdevices.com/showthread.php?t=96892
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
