Skip to main content

Gina Trapani Feature 9/23/05 5:33pm 826,10236 Geek to Live: How to access a home server behind a router/firewall

Recent Lifehacker features have covered how to run a personal web server, how to control your home computer from anywhere, and how to set up a personal wiki. For users on a home network with a router installed, home servers are not accessible from the Internet because of many modern routers' built-in firewall.
Today we'll cover how to open up specific ports on your router to allow access to a home server behind a firewall.
Please note: this tutorial is for advanced users. Your router's firewall is there to protect you from evildoers who try to control your computer over the Internet. Make sure that any service you expose to the Internet is secured with a strong password.
Enabling outside access to an internal computer on a home network requires that you set up NAT - "network address translation," or port forwarding. Forwarding sends requests for ports on the outside of your firewall to the right computer on the inside.
For instance, someone on the outside requests a page from a web server at your router's IP address. With port forwarding set up, your router knows to forward requests for port 80 (a web server's default port) to the computer with the web server running only - and none of the others on your network.
Port forwarding is only necessary when you want to expose a service to computers on the Internet outside your firewall. Some servers you'd want to do that with:
  • a home web server
  • a personal wiki
  • a BitTorrent client uploading as well as downloading
  • a VNC server
  • a home FTP server
While all routers vary slightly, port forwarding is fairly simple. Here's how to get it set up:
Step 1. Determine your server's internal IP address.
All the computers on your internal network have an IP address which looks something like 192.168.0.XXX. Get on the computer with the server running and open a command window. Then type ipconfig to determine the machine's internal address, like so:
C:\Gina>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 192.168.0.11
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
In this case, as you can see, the server's internal IP address is 192.168.0.11.
Step 2. Configure your router.
Most routers have an web-based administrative interface that's located at http://192.168.0.1. (This address does depend on your model. Consult your router user guide for more info.)
Once you've gone to the router administration, entered the password (if one is set up), there should be an area called "Port forwarding." There, you'll set the port number that requests from the Internet will come in, and the internal computer that should fulfill those requests. Here's a screenshot of my Netgear router set up to port forward 5900 to my VNC server, which is at 192.168.0.11 (see above). Click on the image to see a larger version.
Geek to Live: How to access a home server behind a router/firewall
Here's a table of common services and their default port numbers.
ServicePort number
Web server80
VNC (remote control)5900
Instiki wiki2500
FTP21
BitTorrent6881-6990
Labels:

Comments

Post a Comment

https://gengwg.blogspot.com/

Popular posts from this blog

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into ...
Post a Comment
Read more

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checkin...
2 comments
Read more