I have a server that has both Apache and IIS running simultaneously.
Both apps are configured on different ports and both apps use HTTPS.
The app on Apache (port 433) is accessible on any computer on the network, but I can't get the IIS app (port 4433) to work. It says: This site can’t be reached
I can ping the server.
I'm trying to access both websites with IP address of the server and port after it.
The IIS app works on the server, both with localhost address and server IP address.
I have tried all the solutions I found:
1. disabling firewall
2. allowing just the port I needed through the firewall
3. allowing anonymous access in IIS
4. different ports (4433, 7200...)
Nothing seems to work.
I will be grateful for any help.
I assume your IIS binding looks something like this:
Specifically, "All Unassigned" for the IP address, and no host name defined.
If that is what you have, then it sounds like a firewall problem. i.e. The traffic is not reaching your server.
The easiest way to check this is to turn off Apache and change the IIS binding to use port 443. If it works, then you know it's just the other port that doesn't work.
You can also use something like Wireshark to actually see if any traffic on port 4433 is making it to your server (you can use the filter tcp.port == 4433). If you don't see any traffic there even though you've made a request from another computer, then something is blocking it.
And when I say "firewall", I don't mean Windows Firewall. I mean either a router or dedicated firewall appliance that would need to be configured to allow traffic to that port.
Related
I created an asp.net core web app that works locally.
not configured for https if that matters.
I did the port forwarding for the app through my router in two ways
dmz way
firewall rules way
I set the firewall on the computer and router for port numbers 4999-5002
here are the settings for the firewall on the computer
inbound rule
outbound rule
Here is the console window that comes up when running the website
console window
So when I try to access the app using my IP that I get from IP chicken.com the browser will say too long to respond.
What am I missing?
My Isp is att and I do believe they allow hosting of a web server with my plan
I have 3 websites running on my server, all of them on different ports. One is on port 80 and it works fine, the other one is on port 88 and it also works fine. Today I deployed a third one on port 8080, opened the port in Firewall.
I can access it with http://localhost:8080/, with 127.0.0.1:8080 and with it's internal IP address. I can't access it using the external IP address for some reason. I tried accessing it locally using the external IP address and I tried from another computer.
It is worth noting that the website on port 8080 is almost identical to the one on port 80.
Initially I thought it was a firewall issue but I disabled the firewall and tried again and I get the same result (The website took too long to respond).
I am using Windows 10 on the server.
Any ideas as to why this is happening?
I figured out the answer. I am using an EC2 instance from Amazon Web Services for a server. I forgot to go into the console in AWS and open the port there too. I did that and now it's working as it should.
There could be couple of reasons.
Cloud Provider(AWS) Specific
Check your subnet's ACL rules. Both ingress and egress
Check the security group attached to the instance. It should allow ingress
on that port/protocol
Windows Server Firewall: All windows servers and desktops have firewall running which blocks any non-standard traffic. Make sure to add a custom rule to allow the traffic that you want to allow. I found this https://computingforgeeks.com/how-to-open-a-port-in-windows-server-firewall/ link helpful
I am attempting to spin up an application that listens on a port and responds to HTTP requests. I am on a Windows 8 machine connecting through a Netgear router that provides port forwarding. I have:
modified my DNS zone file of one of my domains to point to the IP address that is assigned to my cable modem
Added a port-forwarding rule to my router that sends requests to port 8080 to port 8081 on my computer
Opened port 8081 on my Windows Firewall
Executed netsh http add urlact http://+:8081/ user=Everyone listen=yes as administrator
Started up my app which uses the simple webserver solution found at http://codehosting.net/blog/BlogEngine/post/Simple-C-Web-Server.aspx which uses an HttpListener object with a prefix of http://+:8081/.
From any machine on my local network, I can browse to http://home.example.com:8080/blah/blah and everything works great. Whenever I attempt the same URL from a machine connected elsewhere on the Internet, the connection times out. I have tried using the IP address instead the domain name, and have tried disabling my Windows Firewall (temporarily), still with no luck.
I'm sure this is more of a network setup issue than a code issue, but I thought I would ask anyway to see if there is anything I can do. Sorry for the spaces in the urls above. This is my first post to SO, and I apparently don't have enough of a reputation to post more than a single link.
By "elsewhere on the Internet", I am assuming you are attempting to access it from a different ISP.
The thing about some ISPs is that unless you are paying for a "business class" connection, they will do all sorts of tricks to ensure that you remain a "consumer". What you need is an unNATed static IP address.
By this I mean that the IP address that you may have at your home may not be accessible to the outside world because the ISP is actually NATing (or other) that address to you. This is a fairly common practice because of limited IP4 addresses. If you really want a service accessible via the WWW, I would suggest moving your product to a VPN, or at least a commodity hosting provider.
Edit: Try a VPN service like Hamachi
So I'm trying to setup my home server that is accessible from the Internet. I have created my Web site in ASP and configured my IIS. It works great on my local machine AND other computers on the local network can access it. I want to make it online, so that it can be accessed from elsewhere. I created an account on DynDns, and configured it to redirect the requests to my Internet IP. Then, I configured my router to forward all the incoming requests on port 80 to my local IP address, on which my Web site runs. However, when I go to my DynDns address, it redirects me to my router's home page instead. I have disabled my firewall (I know, not a good idea, it's just for testing purposes) but still no success. Does anyone have any idea what could be going wrong? I have a SMCWBR14S-N4 if that helps.
I've heard of some routers that have reserved port 80 for there configuration pages. I think the general work around there is to run your webserver on a non-standard port like 8080, but I don't have a whole lot of experience with this, so it could be something else entirely. :)
Update: For any future readers, always remember to test your external address and port forwarding on a computer outside of the network the server is on.
I am hosting an asp.net MVC 3 application on my local IIS 7.5 server. People can connect using my IP and the port I set. I can connect by typing localhost:port in a browser. If I type the IP:port however, the browser says it cannot connect.
Using wamp and other hosting programs (and even IIS at one point if memory serves), I could always connect using my own IP.
How can I set IIS to let me connect using my own IP? Or is the problem somewhere else?
My firewall is disabled, the port is forwarded and other people can connect just fine (people outside my LAN) and I have tried 3 browsers.
You cannot connect to your IIS using static IP, but, howerver you can by adding your Static IP as a lookup entry.
Please check this link:
How to Edit Your Windows Hosts File
The article explains how to resolve the IP to reach the IIS locally.