Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[InflatableMouse]

I'm going through the activity log and I have some questions .

my network is 10.26.13.0/24.
I have 52199 port forwarded to my server.

I also get (1.2.3.4 stands for my own public IP address):
GET: http://1.2.3.4:52199/MCWS/v1/Alive
GET: http://1.2.3.4:52199/MCWS/v1/Authenticate
POST: http://1.2.3.4:52199/MCWS/v1/Library/Get
GET: http://1.2.3.4:52199/MCWS/v1/Library/GetRevision
GET: http://1.2.3.4:52199/MCWS/v1/Playback/Zones
GET: http://1.2.3.4:52199/MCWS/v1/Library/GetRevision

Then I'm seeing that same list repeated and see that list with my internal IP address.

It repeats the /GetRevision hundreds of times.

From DLNA Media Renderer I see IP address 192.168.136.1 and 192.168.154.1. This is from VMware Workstation NAT interface.

I see from SSDP:
NOTIFY: http://239.255.255.250:1900*
M-SEARCH: http://239.255.255.250:1900*

The questions:
* How can I see who is connected to my server and what they are doing? I'm assuming the POST and GET with my internal and public IP addresses are logged when something connects to the server but I'm not seeing any client IP addresses, nor what they are doing?
* Can I bind MC to a specific interface to prevent it from meddling with the Vmware adapters?
* The repeated /GetRevision lines is that OKE or does it indicate a problem?
* The SSDP traffic, I tried to find out if thats routable over the internet but I can't seem to find any info about it. Do you know if thats the case and if it is, is it oke to block this stuff from going out?
* Last but not least: is this log on disk in text format too so I can search it?

Thanks!

[InflatableMouse]

Anyone? 

[MrC]

Probably the GetRevisions are Library Server checking the database revision, so that updates can propagate.

SSDP traffic has a low TTL, so it generally cannot travel across too many routers, so generally not for general WAN use.  Likely your ISP blocks the traffic at border routers in any case.

Don't know about binding to a specific interface.

I think MC's network logs are memory resident, and logging in general isn't available until you enable it (via the new Report Problem logging interface).  When enabled, output goes to Log.txt in the appdata\Media Center ##\ folder.