First you should test whether another computer on your local LAN can log into the server.
Do this by entering the Static IP address of the server in the Address Bar of your web browser (for a web server), or by using an FTP client (for an FTP server).
Use the INTERNAL IP address of the computer the server is running on, the one you've already configured as a STATIC IP address.
This will test whether the server is configured correctly. If you can’t log in locally like this, no one from the Internet is going to be able to log in either.
Once you can log in from your local LAN, most people immediately want to try logging in just like someone out on the Internet would do it, by entering the EXTERNAL IP address of the router into the web browser or FTP client.
And then they freak out because it doesn’t work. If anything, they get the router’s login screen, not the server. And nothing they do to the router or the server makes it work. And they tear their hair out for days, because it SHOULD work, but it doesn’t.
And actually- it WILL NOT work this way.
You CAN NOT test a server by trying to log into the EXTERNAL (or “Public”) IP address (the WAN interface) from a computer that is located on the INTERNAL (or “Private”) side of the router.
The router simply WILL NOT pass the connection attempt through from the Local LAN side OUT to the External WAN side of the router, then BACK IN to the Local LAN side, to the server.
This is called a “loopback” and most of the small routers used for home networks don’t have loopback testing implemented.
Think of it this way- the router is DOING its job. It’s supposed to “route” the connection to its proper destination, and it KNOWS the destination (the server) is on the LOCAL side, so it WON’T route the connection in the wrong direction.
So- how do you test a server..?
For a complete test, you need to test it from OUTSIDE the local network. From somewhere ELSE on the Internet, OUTSIDE the router. From a friend’s house, from your workplace, from a library or an Internet Café. Call a friend and have them do it.
Anywhere that is NOT on your local LAN.
If you still have a "dialup" account with your ISP and a modem attached to a phone line, it should be possible to dialup a connection and access your web or FTP server that way because the dialup connection isn't going through the router.
If you don't still have dialup, there are a few other things you can try:
In the case of a web server, there’s actually a rather clever workaround that will at least indicate whether your web site is visible from outside, and that can be tested from INSIDE your local LAN.
#1 With your normal web browser, go to http://web-sniffer.net/
#2 If this server:
a) does not have SSL support, type in http:// enter your EXTERNAL IP address and port number as need be, just like anyone on the Internet would to view your web site. This is your router's "WAN" IP address, the one assigned by your ISP.
b) has support for SSL, type in https:// enter your EXTERNAL IP address and port number as need be, just like anyone on the Internet would to view your web site. This is your router's "WAN" IP address, the one assigned by your ISP.
#3 Press Submit
#4 You should see the HTTP Headers of your web server.
** And for FTP servers, place holder for FTP Directions ***
Remember, for a complete test, to see your site as others will from out on the Internet, you need to test it from somewhere outside your router.
But however you do it, you may be pleasantly surprised to find out it’s actually working already..!
Do this by entering the Static IP address of the server in the Address Bar of your web browser (for a web server), or by using an FTP client (for an FTP server).
Use the INTERNAL IP address of the computer the server is running on, the one you've already configured as a STATIC IP address.
This will test whether the server is configured correctly. If you can’t log in locally like this, no one from the Internet is going to be able to log in either.
Once you can log in from your local LAN, most people immediately want to try logging in just like someone out on the Internet would do it, by entering the EXTERNAL IP address of the router into the web browser or FTP client.
And then they freak out because it doesn’t work. If anything, they get the router’s login screen, not the server. And nothing they do to the router or the server makes it work. And they tear their hair out for days, because it SHOULD work, but it doesn’t.
And actually- it WILL NOT work this way.
You CAN NOT test a server by trying to log into the EXTERNAL (or “Public”) IP address (the WAN interface) from a computer that is located on the INTERNAL (or “Private”) side of the router.
The router simply WILL NOT pass the connection attempt through from the Local LAN side OUT to the External WAN side of the router, then BACK IN to the Local LAN side, to the server.
This is called a “loopback” and most of the small routers used for home networks don’t have loopback testing implemented.
Think of it this way- the router is DOING its job. It’s supposed to “route” the connection to its proper destination, and it KNOWS the destination (the server) is on the LOCAL side, so it WON’T route the connection in the wrong direction.
So- how do you test a server..?
For a complete test, you need to test it from OUTSIDE the local network. From somewhere ELSE on the Internet, OUTSIDE the router. From a friend’s house, from your workplace, from a library or an Internet Café. Call a friend and have them do it.
Anywhere that is NOT on your local LAN.
If you still have a "dialup" account with your ISP and a modem attached to a phone line, it should be possible to dialup a connection and access your web or FTP server that way because the dialup connection isn't going through the router.
If you don't still have dialup, there are a few other things you can try:
In the case of a web server, there’s actually a rather clever workaround that will at least indicate whether your web site is visible from outside, and that can be tested from INSIDE your local LAN.
#1 With your normal web browser, go to http://web-sniffer.net/
#2 If this server:
a) does not have SSL support, type in http:// enter your EXTERNAL IP address and port number as need be, just like anyone on the Internet would to view your web site. This is your router's "WAN" IP address, the one assigned by your ISP.
b) has support for SSL, type in https:// enter your EXTERNAL IP address and port number as need be, just like anyone on the Internet would to view your web site. This is your router's "WAN" IP address, the one assigned by your ISP.
#3 Press Submit
#4 You should see the HTTP Headers of your web server.
** And for FTP servers, place holder for FTP Directions ***
Remember, for a complete test, to see your site as others will from out on the Internet, you need to test it from somewhere outside your router.
But however you do it, you may be pleasantly surprised to find out it’s actually working already..!
Comments
Post a Comment
https://gengwg.blogspot.com/