I have a website hosted in IIS in my local PC.
I can access to my IIS from other computers in the network by typing in http://my_lan_IP. However, when I try to get access to a specific port (http://my_lan_IP:8888) in my local PC, it says the "The site can't be reached."
I disabled all my firewalls and even tried allowing the specific port through Windows Firewall, but it didn't work. Viewing my IIS hosted site on other machines on my network
Thanks so much for your help :)
FYI: I am using Windows 10. My goal is to connect to the locally hosted ASP.NET website from other machines on the network.
Your web server needs to be configured to serve HTTP on port 8888 "for that particular website", in order for a client to connect to that port.
By default, your website is served on port 80, which is omitted from normal addresses. All http web addresses, if not specifying a port, is actually running on port 80, or 8080.
Your windows firewall will not effect local connections you make to your own pc. Get it working on your own machine, and then worry about firewalls that block connections from other machines on the network.
I was able to solve the issue by configuring a host header for a website. Thank you all for your help :)
https://technet.microsoft.com/en-us/library/cc753195(v=ws.10).aspx
Related
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.
I have setup a Virtualbox with a Linux environment running a web server. The host is running Windows 7, and I can access the web served by the server in the virtual machine from the host's browser.
However, I would like to be able to access this web server from another computer; say, a colleague on the same network that the host is in. Is there a way of doing so?
Summary:
Host (win7) interfaces:
- 172.16.1.15 (internet facing)
- 192.168.55.1 (VM facing)
Guest (linux with web server running) interface:
- 192.168.55.2
Web server is reachable from Host (through 192.168.55.1 - 192.168.55.2 interface)
Web server is NOT reachable from other computer on 172.16.1.X network.
Can you guys help me out on what I may be able to do in order to achieve this?
Thank you!
Well, despite downvotes without any kind of explanation why (thank you!), I have found a way of doing what I intended on Virtualbox settings:
On machine, right click, Settings > Network > Advanced > Port forwarding, and then, fill with corresponding data, i.e.:
host ip could be 0.0.0.0,
host port should be the port other users will use to access your computer (and thus the VM),
guest ip is the VM ip, and
guest port should be 80 if it is a web server typically).
Thank you, hope this helps to the next one running into this!
On my computer I have deployed my web site on IIS. If I access this website locally with :8080 works perfect, but when I try to access this site from another machine or my Android phone I get 'The site can't be reached. my_ip_address took too long to respond ERR_CONNECTION_TIMED_OUT –' this error.
I have tried solutions from this question, but nothing worked for me. Need some help!
There are few factors which can affect the accessibility of the site hosted on your local computer:
Is the client machine (including your phone) in the same network as the Server (In this case your site)
Is the firewall configured to allow connections on port 8080
Have you tried accessing the server using the IP Address. For e.g. http://192.168.0.1:port
Steps to isolate
Ping the server Ip from the client machine and see if it is able to connect to it.
ping 192.168.0.1
If the above fails, then I would assume that you are not on the same network. If it succeeds then check if the port is open.
You can also use nmap to see whether the ports are open or not
nmap -p 8080 kaushal.com
If the above fails, then open the port in your Firewall configuration and then try again.
Try this and share the results.
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.
I have created an ASP.NET application on my local machine. In order to test this application in IE 6, I have created a VPC. I am trying to connect to this web application through the VPC. However, I cannot connect to it. I can however connect to the internet.
What am I doing wrong?
Can you ping from the virtual PC? If not, you have network configuration issues.
Otherwise, check firewalls, and make sure that port 80 is open and sending traffic to IIS.
there are many possibilities. first I'd consider would be any firewall rules on the ASP.NET side preventing incoming HTTP connections.
What is the URL you are using to go to your site? If you are using localhost, you will need to change that to the actual IP address of your development machine, as localhost on the Virtual PC image will be a different IP address than localhost on the development machine.