I have a web service hosted in IIS on port 87 (can't use default port for port forwarding with my ISP). I have it running under Default Web Site
I am able to access the web service on my local in IE without an issue, however, when I try to access it from other machines on my LAN, it does not resolve.
I edited the hosts file of my local to:
127.0.0.1 testsite.local
In my bindings I have:
http All Unassigned Port:87 Host Name: testsite.local
http 192.168.1.111 Port:87 Host Name: <blank>
I also have my firewall turned off on the machine hosting for testing, still nothing. Any ideas?
Figured it out, was because port 87 is considered unsafe. Switched it to 86 and it worked fine.
Related
I have a Windows Server 2012 virtual machine provisioned on Azure. I installed Neo4j server on this virtual machine and I'm accessing the Neo4j browser on localhost:7474.
However I cannot access the browser outside using my virtual machine's public IP e.g <machineIP:7474>
Here's what I have done so far:
In the Azure portal, I added inbound rules for the NSG to allow http and https ports 80 and 443 (I have done the same on a Linux virtual machine also hosted in Azure and I can access the browser just fine)
I also added an inbound rule in Windows Firewall to allow Port 80 and 443 as well
What possibly blocks me from accessing the virtual machine's IP from the outside?
You have to add TCP port 7474 to the firewall in the Azure portal:
change your neo4j-server.properties
set
org.neo4j.server.webserver.address=0.0.0.0
To remotely access Neo4j installed on a Windows VM in Azure, these are the changes you'll need to make:
In the Azure portal, add TCP port 7474 to the Endpoints of your Windows VM
On your Windows VM, in the Windows Firewall Advances Security, add a new Inbound Rule for port 7474
Change the conf/neo4j.conf and uncomment this line:
org.neo4j.server.webserver.address=0.0.0.0
Note: In case you also want full access to Neo4j's browse interface including Bolt, then also add port 7687 both in the Azure Endpoints and the Windows Firewall.
I have create new web site in IIS 8. I have configured my web site like this
http://ip:8080/
When I browse it from any public network it is not opening. But If I open is locally it works fine. http://localhost:8080 it is working fine. What I tried I stop all other sites, Default Web site and assign 80 port to my site then it is working fine in locally as well as publically. I don't know what is the issue.
Clearly you have a firewall or other network routing issue. Check all configured firewalls on your server/housing machine, as well as along your network path (router, or other perimeter network devices)
Also if trying to connect through your internet side IP you will want to check any port forward rules on your router (If behind NAT, like most connections are)
My problem is solved. I have opened a 8080 port on Azure management portal. And on VM I have create new rule which points to this port.
I have a problem with my windows azure virtual machine.
I need to open the Port 443 (HTTPS) on the VM.
In the Endpoint Config. of the virtual machine, I opened it and configure the ACL with the following parameters:
Permit
0.0.0.0/0
It's a Windows Server 2012 VM and I created the firewall rule for the public Connection.
A Port Check from ping.eu shows that the port 443 is closed.
The Location of the virtual machine is Western Europe.
I hope, you can help me.
Kind Regards
Sebastian
I also had this issue and it was very annoying! I thought at first I was not setting up the SSL bindings correctly or that it was a certificate issue, then moved on to firewall issues. In the end it was the Azure endpoint at fault.
I had added the 443 endpoint, disabled local firewall and got nothing nothing. I got suspicious when I added a new endpoint on 8080, bound to https and it worked fine.
I deleted the 443 endpoint, shut the Azure VM down from the webinterface after shutting down the client. Created a new 443 endpoint and restarted the VM (I had already tried restarting my win2012r2 vm). It worked.
It must be a glitch in the networking stack of azure endpoints. You are not going mad!!
Hope that helps!
P
Did you also configure the Endpoint Configuration through the web management portal to forward connections from the ext->int ports ?
Anything you change on the Win2k12 Virtual machine will just affect the VM itself. i.e. opening 443 in the firewall, or configuring routes etc...
But you also need to allow a connection forward from the cloudapp.net public IP address to the internal IP of the box. See the below screenshot.
Another gotcha. In addition to setting up the Endpoint configuration, you need to enable IP Forwarding. This is disabled by default.
IP Forwarding can be found in the IP Configuration settings of the network interface.
how can I expose my Website to other PC's in my local network? Say I my computer name is CompTest and I can access my websites deployed in IIS in my own machine in http://Comptest/ and http://localhost/. Is there anything I need to set so other computers in my local network can access http://CompTest/? Just within local network.
You need to enable HTTP (port 80) over TCP through the Windows Firewall (in the Control Panel).
try using your ip address rather the your host name. like http://[ip address]:[port no]/[site name]. for your info http port is 80. also do
disable firewall
use static ip
i hope this will help you
I can't connect to the default web site in IIS 6.0 using localhost or 127.0.0.1 or by server name. When I telnet to port 80 with one of these names, there's no connection.
However other web sites are running and I can telnet using any of the ip addresses.
I can ping to localhost where 127.0.0.1 is responding.
The default web site is running. It's not stopped.
check the windows firewall, that has a habit of blocking IIS on a local machine
Is the default site bound to a specific IP address? By default it would display "all unassigned" for the IP, but if you've linked all sites to a specific IP address, then the local IP would no longer be configured on the server and would not answer.
httpcfg.exe did it.
Stop all the sites under IIS, restart IIS and start the one you're interested in.
If this fails delete all the sites under IIS and create from scratch. If this fails, the problem is not with IIS and you'll need to look at what other services are running and start turning them off.
A firewall may prevent some content of your website/website itself from being accessible, so if you have problems with accessing content then check that your firewall is not rejecting content from your site.
The easiest way to ensure that your firewall is not blocking your access to your site services is to use your firewall control panel to allow data from *.(your site url).