First of all, i configured port 80 in my modem router which is 192.168.1.1 and in windows firewall, but although when i check it in websites that does my port 80 open or not?
I get this result: it is closed, how to solved it, call internet provider or what? does it have any other solution that u can help me
Please Help
Regards
if your web server is installed/setup behind a router(local) you need to configure your router for port forwarding pointing to your server ip and port.. you can also enable DMZ and set to point to your server local ip address.
http://lifehacker.com/127276/geek-to-live--how-to-access-a-home-server-behind-a-routerfirewall
Related
I have a java program that uses SQL queries. The goal is to send them from my home PC to a workstation on a different network elsewhere.
The SQL server is on Windows Server and I opened port 1433 for inbound connections. From that computer, I can successfully ping the port. However, I can't ping the port from the public ip address, only the local (192.168...), so it doesn't work if I were to try to ping it from my home computer.
Is there a way that I can ping it from my home computer? If so, how would I specify the address for JDBC?
Thanks!
It sounds like your Windows Server is behind an internet gateway/router. You need to configure the gateway to allow and forward inbound connections to TCP port 1433 to the IP of the computer that has SQL Server installed.
Here are some guides that explain how to enable port forwarding on different devices:
How to Forward Ports on Your Router (lifewire.com)
How to Port Forward (No-IP.com)
Also, note that we can ping IP addresses, not ports.
I want to access my raspberrypi from outside my local network, in particular using ssh. When I searched for answers, almost all mentioned port forwarding. My understanding is a little thin, but I think I have forwarded the port. Instead of the standard port 22 I use something like port 2222:
ssh -p 2222 bla#raspberrypi
This works locally, but it didn't work when I tried it outside, and I found that port 2222 is closed. My impression was that port forwarding was synonymous with "making the port available outside LAN". How do I actually open the port for outside access? Thanks in advance.
Go to your routers admin page, usualy at 192.168.1.1 (especaly cisco), sometimes is at 192.168.100.1. Another concern is that you have to have static ip from isp because there is a refresh rate which if you have the ip is resetting. You could open a port to the dynamic ip but it will be eventualy changed. I have tested this and it work until the ip changed.The default port is 22 but you could change it, here is a tutorial and explanation by Eli the Computer Guide. If you couldn`t port forward watch a tutorial on how to port forward on your router. I recommend because you have little knowledge in port forwarding that you should go with the default port.
Keep Hacking. Good Luck :) !
I have a Ubuntu Server 16.04 running on a machine in my local network.
The machine has static assigned IP and running apache2. There is no problem in connecting to it from my local network.
I have port-forwarding for ports 22 and 80 setup on my router to the IP address of the machine.
When I check the ports with my public IP address on sites like http://www.canyouseeme.org/ the result is that the ports are open. When I try to connect using my public IP address and using those ports the connections are refused.
I tried disabling firewall in the router and also on the machine, no result.
What else should I try? It seems that the server is getting no incoming connection when I check with netstat.
Just for troubleshooting purposes:
Setup port forwarding on port 22 and try to ssh into your server using the public IP? If it works, it means apache is refusing the connections and not your router or ISP
On your router, setup the server on the DMZ temporarily and check if it works
Add another port forwarding rule on your router to redirect all http requests on port 8000,for example, to port 80 internally, then try to access your server with http://[public_ip]:8000
Have you changed anything on the apache2.conf file? Also, explain how you are testing the connection, internally using the public IP or from the Internet?
I open IE explorer & Chrome in my computer and type localhost:80 and I get the index page.
Here I think my machine's IP is same to both connections (IE explorer & Chrome) and ports are too (80).
Note: Source port will be different (as destination is same: localhost IP), this is my second question.
So how webserver (lets say apache) handles this port 80 connections without failing? Does it port forwarding? In OS level even I tried with addr re-use, port re-use parameters and it is all same we cannot make multiple connection with same IPs & ports.
Now, probably you have came up with a solution: although source ports and IPs are same, destination port is different in package: <protocol>, <src addr>, <src port>, <dest addr>, <dest port>.
A. I got 49483~50004 ports as you can see on image. How client knows which destination port (49483~50004) is bound by webserver? If it is random between 0 and 65355 the webserver always binds all ports, it is very resource consuming. How webservers avoid from this?
Look at this image: command prompt-> netstat
If this question is related with low level sources it is OK, I understand Embedded TCP/IP/UDP, Phy MAC communication and package structures.
You have this all back to front.
All the port numbers at the server are the same: 80. So the client only has to know port 80.
All the port numbers at the client are different: 49483-50004 etc. So there is no ambiguity in the connection, because the 4-tuple you mentioned is unique.
All http request by default call to servers in the port 80, because servers listen by default in that port. So you only give an IP or hostname and the web browser add the default port (80). You can give a custom port if you web server is listenning in another port (usually Tomcat listen by default in 8080) for example you call it in: http://www.youamazingweb.com:8080.
A good example is see the IP as the home and the port is the door where clients enter to consume some resource hosted in server.
I have a Windows 2008 R2 server that will need to listen on a particular port (e.g. 1234) in order for an application upgrade to work, but currently the application doesn't have a listener service configured for port 1234.
Our firewall is managed by a third party, but I would like to check in advance that the port 1234 has been opened before I install the update. Is this possible?
I know I can telnet to the server on other listening ports, but as this server has no application listening to 1234 I can't be certain that it is in fact, open. Telnet results are inconsistent when connecting to ports that are apparently listening in netstat.
Is there anything I can do in Powershell or VB for instance, to set up a listener for port 1234 in advance of the upgrade to ensure it will go smoothly?
Many thanks in advance.
Anything that accepts traffic would work.
Run some other service on port 1234 and see if you can connect to that.
Use a network sniffer like WireShark on the server and see if you're getting connection attempts to port 1234.
Install netcat on the server and tell it to listen to port 1234 then connect to that port on the firewall. If it connects, the port is open. (This is really the same as #1 but without an actual service.)