Set up web server with port forwarding to web server 80, for some reasons, ouside world is unable to see web page, but machines on local network can see it properly. Any idea?
Internet provider is Verizon. How can I tell packects reach to my router? How can I tell packets are forwarding to my web server?
Any help is appreciated.
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Do you mean that you need to access an server on your LAN from the outside world ?
The manual is on the second result of a google search for smcd3gn and the table of contents has clickable links.
The machine you run any inside server on needs a static IP address (192.168.0.11 for example) and you configure the gateway so that your outside request to address and port (http://10.10.10.1:8080) gets mapped to your inside machine's IP address and the port you are running the server on (192.168.0.11:8000) for example.
If you are only using one internal web server just map port 80 to port 80 along with the inside IP and you can omit the port number in the external URL. (If you are running more than one server you should be able to figure it out.) Remember to disable external access to the router's configuration if you do this because that also runs on port 80.
My example mapped outside port 8080 to inside port 8000 just so they would be different. Remember that one outside port can be mapped to a single inside address and port. You can run two inside machines with a service on their own port 80 but they need different ports on the WAN interface.
When you use port forwarding in Virtual Servers and try to test it from within the local network, it may fail. When for example, port 80 is forwarded to a web server in the local network, you may get the router's home page instead of the web server's one or you may get nothing at all. When you try to use the server from outside the local network it will work fine though.
This can happen when you try to access the router's WAN IP address from within the local network. In order for port forwarding to work from within the local network, the router needs to support a feature called NAT loopback. This is not a part of the specification of Belkin routers and modem-routers, so most of them will not have the feature, and if a router does have it, it is not supported.
In order to use the server from within the LAN, you can address it by its internal LAN IP address (e.g. 192.168.2.101).
If the WAN IP address has a DNS host name associated with it, such as www.example.com, and you need to use that name to connect to the server, you can do so by associating the name to the local IP address in the hosts file (a file called hosts with no extension). This file lists IP addresses and host names and is used before actual DNS lookups are done. You can add lines to the hosts file using a text editor like Notepad on Windows. The lines look like:
The lines contain an IP address and one or more host names separated by white space. Anything that follows a hash sign is a comment and will be ignored. You will need to change the hosts file on all machines in the LAN that need access to the server.
On Windows, the hosts file can be found in C:\Windows\System32\Drivers\Etc on Windows XP, Vista and Windows 7, in C:\WinNT\System32\Drivers\Etc on Windows 2000, and in C:\Windows on Windows 98 and ME. You need to have administrator rights to edit the file; on Windows Vista and Windows 7 you need to run Notepad as administrator.
The best way to find out what is being forwarded is to look at the traffic with the Wireshark program. You can install this from the Internet.
Wireshark is perfect for this but you have to learn how to filter traffic or there will be too much information collected. It is also regarded as (a bit of) a burglar tool so don't use it at work without permission.
I would recommend that you connect a PC to a wired port on the inside LAN and configure the router to forward outside requests to the PC. When you run wireshark on the inside PC with a filter that selects for tcp port 80 (or tcp port == 80) you will see traffic forwarded from the router.
Use your outside machine to request a page from the router's outside address and the port you are forwarding. If you have forwarding set up correctly, you should see a TCP connection attempt. If you are not running a web server on the inside PC, there will be no connection so you will only see the SYN packet from. outside. If you have a web server on port 80, you will see a fair number of packets in both directions. (SYN -- SYN-ACK -- SYN -- some HTTP Headers an HTTP GET / a response and FIN -- FIN-ACK).
Once you see successful port forwarding (your are forwarding TCP packets, right?) at the PC, change the destination of the forwarding to the camera.
This is really technical but Wireshark is so good that it is quite easy to use.
To unlobck your website by your NETGEAR firewall.
Go to the router's Port Forwarding Menu to enter the port numbers and IP address of the server. You will want to enter PORT 80 for your website and forward that to the machine that have the website running.
To find the IP of the server that is running the website,
start-> run ->cmd
for linux and mac
To recap, what you want to do is forward port 80 to that IP of the web server.
To access "localhost" you must have a web server ( IIS or Apache - IIS is the simplest and is found in add/remove programs, Windows components usually) running on the PC that Joomla is installed on. You must also use http://localhost for it to work. Localhost means you are only doing a loopback to your own pc for testing purposes. By default most web servers run on port 80 if the port is changed then you must use "http://localhost:port". Depending on how your network is set up - If you have a router or firewall you may also have to "open" or do a port forward to port 80 for the software to see the server holding the Joomla pages and also allow internet access as a server. First try the default web page the server has usually default.htm or index.htm as http://localhost/default.htm etc, if it loads then you know localhost is functioning, then try the Joomla page you want to see using it in place of default.htm. If no page loads at the start - then check your Apache(Xampp) configuration file to be sure it is set up and working properly - if I recall it is hhtp.conf open it with notepad to configure and save as "all files" not text. You might also check your Joomla configuration options as well to be sure the correct port and location are used for serving pages.
In order to access your default web page remotely, port 80 "INBOUND" must be open to the internet.
To access your web server, two things need to happen.
The first is you or someone else must initiate a http request on port 80 using the public IP Address of your DSL connection.
Second, your router must forward that request to your servers internal ip address.
Ex. Lets say your public ip address is 22.214.171.124. In a browser window from a remote location, you enter the URL http ://126.96.36.199 The request will be sent to your router on port 80.
Your web server will not have the ip address 188.8.131.52 because it's on the private network side of your router. So, lets say the private ip address of you server is 192.168.1.100
You need to configure your router to take the http request coming from the internet on port 80 to ip address 184.108.40.206 and forward that request to 192.168.1.100. This is known as port forwarding.
You also need to configure the host header name of your "web page" so it knows it needs to display the web page.
Since we're just using ip addresses in this example and not an actual FQDN (fully qualified domain name), you would make a host header entry for the web page of 220.127.116.11.
To do this open IIS.
Navigate to the web site in question and right click on it then select properties.
On the website tab, ensure the port number is set to 80 and choose the appropriate internal ip address if you have more than one network adapter in the server.
Next click on the advanced tab and look for the heading Multiple identities for this site. This is where you enter the ip address 18.104.22.168.
If you have a fully qualified domain name, you would enter the domain name instead of the ip address as specified in this example.
Host header names are the key to running multiple websites from one physical server as long as it has the necessary horsepower to do so.
Hope this helps and isn't confising. If you're confused in any way, don't hesitate to ask for clarification.
Verizon blocks port 80 traffic to residential customers. If you want to host a website, they expect you to pay for the business service and a static IP.
I am monkeying around with my DNS records on goDaddy to see if I can get http traffic to go to port 8080 instead of port 80. So far, I have not had any success.
I did find no-ip.com, which, for $25/year, will "host" a simple redirect for you, so that when people type in http://yourdomain.com, it actually gets redirected to http://yourdomain.com:8080. That :8080 does show up in the address bar, but I think that's okay. Especially for $25/year.