Print

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

[Facel]

Is it possible to access MC server from outside my network with a translation port on my router, instead of having the same port (52199) on the external and internal network, I have a different port number when accessing from outside that is leading to my 52199 port ?

[JimH]

You can use NAT to modify the port.

[Facel]

Yes ... but how can I tell MC that inside my network the server port is 52199, and outside my network the port should be 12345 ?

[JimH]

I'm not really expert on this subject, but the router should be able to do that with NAT.  You'd run the server on 52199 (although you could change it if you prefer).

The wiki has a topic on Network Access.

[Facel]

The router translate an External IP adress + Port number A  into  an  Internal IP Adress + Port number B

In JRiver case when you try to load a library JRiver first try to find the Internal IP adresse of the server then switch automatically for searching the External IP adress + Port number B for the client connexion.

This is quite nice because it is simple. 

I simply wanted to apply "my security policy" with having a different port number A on the external adress pointing to the internal port number B (that would also have been changed).

I understand that it is possible to modify Port Number B but port number B should remain the same as port Number A.

[RoderickGI]

You can't do that when you connect to MC from outside your network using the Access Key method. You need to connect to MC using an IP Address or URL. If you use either of those methods you lose the built-in capability to use WOL to wake your MC Server, but that may not be an issue for you. Lots of routers won't forward a Magic Packet into your LAN anyway.

You haven't' said what you are using to connect to MC from outside your network. Different Clients have different capabilities. i.e. JRemote verses a MC Client.

So inside your network, connect using the Access Key. Leave the MC Server running with port 52199.

From outside your network, connect using your internet IP Address or the URL of your network, perhaps using the DynDNS service, for example. i.e. www.xxx.yyy.zzz:12345, which is then port forwarded and translated to aaa.bbb.ccc.ddd:52199.

[Facel]

Thanks RoderickGI for your clear answer

You haven't' said what you are using to connect to MC from outside your network. Different Clients have different capabilities. i.e. JRemote verses a MC Client.

I am using MC client on my Windows Laptop, but I would like also to use JRemote on my Iphone. (I didi not have tested it yet, because I was trying
some "impossible" Networlk adress tranlation !!

Inside my network I also have a headless Linux MC Client (based on a Allo USBridge = Raspberry), but this client does not wake up my MC Server (based on a Windows NUC)
I have to find out this issue. This is why  I first use JRemote for waking up my MC server, and then I switch on my Linux MC Client.

[RoderickGI]

I would expect a headless Linux MC Client to wake a MC Server, if the MC Client is started or restated when you need to use it. The Client would need to be connecting to the Server library by default. But if the MC Client was already running but hadn't been used for a while and the MC Server had gone to sleep "underneath" it, then the MC Client will not wake the MC Server. This is something that JRiver needs to work on. (i.e. A Client which is already running should check if the Server is awake or asleep and should wake a sleeping MC Server is necessary.)

I don't know how you would get a headless Linux MC Client to wake a sleeping server at the moment, other than rebooting the Client. But your JRemote method is a good workaround if the Client reboot doesn't work.

As for waking a MC Server from outside your LAN, effectively Wake On WAN, the biggest issue is whether your Modem/Router will pass a Magic Packet from the WAN to the LAN, and if it will send that Magic Packet out on the broadcast address for your LAN. I tried to get this working recently using Wireshark to watch for Magic Packets, and using my mobile phone via the mobile network so that it was outside my LAN, and I found that my router simply will not pass the Magic Packet. So my MC Server stays on all the time if I want to access it from outside my LAN. I was using Gizmo, but the issue will be the same with JRemote.

[Facel]

I would expect a headless Linux MC Client to wake a MC Server, if the MC Client is started or restated when you need to use it. T

it is absolutly not the case.  MC server is asleep and headless linux MC client is switch off.  When linux MC client is switch on it does not wake up MC server.

[RoderickGI]

Well, as I said, I expect it should. There is something wrong. Or maybe WOL hasn't been implemented in MC on Linux, but I couldn't imagine why that would be the case. Linux, the OS I mean, supports WOL generally.

That Client definitely connects to the MC Server automatically when rebooted? If it didn't, that would be a reason for WOL not to be activated.