Does LiteManager Server Recognize No-IP Port 80 Redirects ?

Troubleshooting

Does LiteManager Server Recognize No-IP Port 80 Redirects ?

Postby bgillette » 19 Nov 2019, 17:19

I have an odd situation. hoping someone can help. At my work, the network security folks only allow ports 80, 443, and 52 outbound. I have lite manager server setup on my home pc and i often have to remote into it from my work, so i can ONLY use port 80 on lite manager viewer at work to get "out" to the internet. I have configured my home router to port forward traffic coming in on port 80 to the port my lite manager server is listening on, lets call it port 9999, and that works fine. but i wanted to not have this setup on my router, for obvious security reasons. I have a paid no-ip account with multiple domain names, and no-ip supports port 80 redirects. so i have setup a domain name, lets call it myrdp.com to do a port 80 redirect to my ip address and the port # i'm running lite manager server on. I have verified that when i go to myrdp.com that the redirect it happening and no-ip is redirecting my connection to myrdp.com:9999 (ie: myipaddress:9999) - however the connection from my work pc to my lite manager server at home doesnt' work. Its like lite manager is not recognizing the connection is coming in on port 9999 or something. In my litemanager viewer it shows the connection as "locked". If i change my router back to forward to internal port 9999 from external port 80 and remove the port 80 redirect on my no-ip domain name it works fine.
anyone know if there is any issues with using a setup like this, with port 80 redirects, with Lite Manger Server?

So here is my setup:
this works:
LIte Manger server listening on one of my home pc's on port 9999
My home router setup to forward port 80 to port 9999
My No-ip domain name myrdp.com setup to NOT redirect port 80
My Lite Manager viewer at work setup to work on port 80
My home PC Firewall setting to allow port 9999 on tcp/udp

This does NOT work:
LIte Manger server listening on one of my home pc's on port 9999
My home router setup to forward port 9999 to the ip of my home pc running Lite Manager server ( have also tried it with NO port forwarding at all on my home router)
My No-ip domain name myrdp.com setup to redirect port 80 to port 9999
My Lite Manager viewer at work setup to work on port 80
My home PC Firewall setting to allow port 9999 on tcp/udp

anyone have any idea why the 2nd setup, using the no-ip port 80 forwarding service would not work?
bgillette
 
Posts: 2
Joined: 19 Nov 2019, 15:37

Re: Does LiteManager Server Recognize No-IP Port 80 Redirect

Postby admin » 20 Nov 2019, 07:40

I'm not 100% understand situation
But seems it should works

Status "locked" mode mean that is connection is well but you can't authorizate on LM Server side

Turn on Logging on the LM Server side
Image

PS
Try to
My No-ip domain name myrdp.com setup to redirect port 80 to port 80 (on your router) and My home router setup to forward port 80 to port 9999
Does it will work ?
Best Regards LiteManagerTeam
admin
Администратор
 
Posts: 489
Joined: 07 Jun 2010, 13:19

Re: Does LiteManager Server Recognize No-IP Port 80 Redirect

Postby bgillette » 20 Nov 2019, 16:53

what i'm trying to do is avoid using a port 80 redirect on my router, and let my no-ip dynamic dns/dns records system handle the redirect from port 80 to the port that my LiteServer manager is listening on (9999).
my LiteManger server is listening on port 9999 but i can only use outbound port 80 at work. My current setup (that uses a port forward from port 80 to 9999 ) on my router works right now ok. but i really don't want to do port forwarding on my router from port 80 to port 9999. the no-ip domain name i have, allows, as part of their service, to do a "port 80 redirect", whereby they append any port you like to the domain name you use on their service. So my domain myrdp.com on the no-ip service is setup to use my current ip, and appends the port to it, like: http://myrdp.com:9999 when i call that url from my work from my browser, which is using port 80.

so my thinking was, this in effect, does the same thing i'm trying to do by forwarding port 80 to port 9999 on my router. basically instead of me forwarding port 80 to port 9999 on my router, when i configure my myrdp.com domain in LmViewer to use port 80, no-ip takes care of the redirect from port 80 to port 9999 by appending the port # to my domain name/IP address.
I have confirmed that the incoming traffic coming into my router is being converted (by no-ip) to my isp assigned IP address with the port appended. However, Lite Manger server is not (apparently)recognizing that. I "think" it may have to do with the fact that the no-ip port 80 redirect is only doing that for maybe http connections. not sure.
Got nothing in the logs that is useful. i clear the logs, and tried it by connecting from work using the router based port 80 forwarding to port 999 and got a succuessful connection in the log. then removed the the port 80 forwarding from my router and changed my no-ip domain name to do the port 80 redirect. it doesn't work, and got nothing in the log. I don't think Lite Manager Server is recognizing the connection attempt . my speculation is that the port 80 redirect on the no-ip service, is only doing it for http
bgillette
 
Posts: 2
Joined: 19 Nov 2019, 15:37


Return to LiteManager: Support

Who is online

Users browsing this forum: No registered users and 1 guest

cron