![]() 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. but i really don't want to do port forwarding on my router from port 80 to port 9999. My current setup (that uses a port forward from port 80 to 9999 ) on my router works right now ok. My LiteManger server is listening on port 9999 but i can only use outbound port 80 at work. ![]() 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 No-ip domain name setup to redirect port 80 to port 9999Īnyone have any idea why the 2nd setup, using the no-ip port 80 forwarding service would not work? bgillette Posts: 2 Joined:, 15:37 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 home PC Firewall setting to allow port 9999 on tcp/udp My Lite Manager viewer at work setup to work on port 80 My No-ip domain name setup to NOT redirect port 80 My home router setup to forward port 80 to port 9999 LIte Manger server listening on one of my home pc's on port 9999 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.Īnyone know if there is any issues with using a setup like this, with port 80 redirects, with Lite Manger Server? In my litemanager viewer it shows the connection as "locked". Its like lite manager is not recognizing the connection is coming in on port 9999 or something. I have verified that when i go to that the redirect it happening and no-ip is redirecting my connection to :9999 (ie: myipaddress:9999) - however the connection from my work pc to my lite manager server at home doesnt' work. so i have setup a domain name, lets call it to do a port 80 redirect to my ip address and the port # i'm running lite manager server on. I have a paid no-ip account with multiple domain names, and no-ip supports port 80 redirects. but i wanted to not have this setup on my router, for obvious security reasons. 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. 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. At my work, the network security folks only allow ports 80, 443, and 52 outbound.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |