INTERACT FORUM
More => Old Versions => JRiver Media Center 25 for Mac => Topic started by: Bernhard on April 07, 2019, 12:09:45 am
-
First I have to explain my setup: MC is installed on a HTPC and I control it with my notebook remotely connected to the main library on the HTPC.
Whenever my MacBook goes to sleep-mode and MC25 is still running, I get this message on the notebook, which I do not remember I ever got in the past. I of course have to abort with NO, because the connection is up, as soon as the computer is unlocked.
How to deactivate that message?
-
I assume that your HTPC is the MacBook then?
This is a new feature. What is happening is that when the MC Server goes to sleep with a connected MC Client, and the user does something in the Client, the Client will try to wake the Server using WOL commands. If it fails, or takes too long, you get that message. Prior to this feature a sleeping Server while connected to a Client required a restart of the Client to wake the Server. It would be fair to say that this isn't a polished feature.
Reading for you:
https://yabb.jriver.com/interact/index.php/topic,119661.msg827571.html#msg827571
https://yabb.jriver.com/interact/index.php/topic,118288.msg821813.html#msg821813
-
No, the HTPC is always up and running. Music is playing, and other devices (like iPad) always have access to it.
Just the "controller", the MacBook goes to sleep mode. When I login again, I see that message.
To me it does not really make sense - of course the connection brakes, when Wifi stops during sleep mode.
Same behavior as on the iPad, there I get no message.
-
Oh, so you have a Windows PC running as a HTPC, which is running MCServer, plus a notebook running Windows and MC for Windows, plus a MacBook running MC for MAC? Your first post wasn't clear. You still aren't being clear. Yes, I realise that your "notebook" is probably the MacBook. You used the terms interchangeably.
You can't deactivate that message if conditions are met to cause it.
Did you read the threads I posted? That is all I know.
-
Sorry Sir for confusion:
HTPC = Windows = MC server and always on
MacBook = notebook = MC controller for HTPC
no other computers
If the message is new in MC25 and wanted, then I wonder why iPad app does not show it? We have identical behavior there, whenever we lock it. The engineers shoud add it to the iPad app too.
Which of course is nonsense ;)
-
Well, the iPad is running a different Operating System, iOS, and a different application, I assume JRemote? So it isn't surprising that it hasn't been added.
This new message and the changes beneath it are still a bit experimental I think, and have only been added to MC so far. Maybe that will change in the future. But I suspect that there will be some changes to how it works, and if so, the message may hardly ever appear. We shall have to wait and see.
-
Hi, this is my first post so I
I am unable to access MC via LTE. I can set up a server connection on the LAN but not via Internet/LTE. This is what I get:
Finding computer addresses associated with access key 'correct access key'
Response received
<?xml version="1.0" encoding="UTF-8"?>
<Response Status="OK">
<keyid>EUeRkv</keyid>
<ip>correct IP address</ip>
<port>52199</port>
<localiplist>correct local IP addresses (Ethernet and WiFi)</localiplist>
<macaddresslist>Correct MAC addresses</macaddresslist>
</Response>
Found 3 addresses
Connecting to IP: correct local IP address Port: 52199
Timed out
Connecting to IP: correct local IP address Port: 52199
Timed out
Connecting to IP: Correct WAN IP address: 52199
Timed out
What do I need to do?
Many thanks!
-
Your router needs to be set to forward communication on port 52199 to the MC Server on your LAN. MC, JRemote, or similar will try to connect to your Public IP Address, which is the internet address of your router. From there the network traffic needs to be sent to the IP Address of the Mac running MC Server. Your Mac needs to be switched on and running for this to work without more setup. Search for discussion on "Port Forwarding".
If you allow your MC Server to sleep when not in use, then your router also needs to be capable of sending Broadcast Wake On LAN packets. Many won't do this, for security reasons mostly. Search for discussion on "Wake On LAN", "Wake On WAN", WOL over the internet" and similar.
-
Thanks for your quick reply!
My router/cable modem has port forwarding set for 52199 (TCP&UDP). MC Server is running and I am still not able to connect. I have a NAS which I can access remotely without problems. I'll try to reset my cable modem, maybe that helps...
-
A firewall can also block access.
This may help:
https://wiki.jriver.com/index.php/Network_Access
-
Just got it to work. For some reason my gateway assigned a different IP address to the port from what it was supposed to be (i.e. my iMacs IP). So I reset the iMac IP to the one where the port is effectively being forwarded to and now it works. It was all a problem with how ComCast regulate what you can do with router/modem settings. Thanks for your help!