i created a site on my iis7 it's like http://localhost:88/my
i also can access it like this http://myip:88/my
but when a friend of mine from a remote computer tried to access it like this http://myip:88/my it gives him 404 not found
anybody can tell me what should i do to make it work from remote ?
Check your firewall. You will have to open TCP Port 88.
Part 4: Opening Up to the Outside
World
Windows Firewall blocks the World Wide
Web Services port by default (Port
80). With this port blocked, other
machines cannot connect to your web
server. This severely limits the
scope of potential web site viewers.
So, in order to show your new web site
and server to the outside world you
must add an exception to the Windows
Firewall.
Click Start and type firewall into the Search bar and press enter.
(Note: Make sure you select Windows
Firewall and not Windows Firewall with
Advanced Security)
Click Change Settings
Click the Exceptions Tab and Scroll to World Wide Web Services
(HTTP).
Click the check box and click OK.
Now your machine is accessible to the
outside world. You can connect to
your machine by typing in the IP
address of your server into another
machine’s web browser.
source
If firewall setting is not the issue (say it's turned off), find out public IP of your server (ex. 192.168.0.152), then add it to http listener on the server itself
Open cmd and type:
netsh http add iplisten 192.168.0.152
Go Control Panel>System and Security>Windows Firewall>Allowed Programs-> then check all " World Wide Web Services(Http) tab"
Its is worked for me
Related
Trying to host a web site on my local Win 10 Pro machine withing IIS, provided I share the IP to my friends. My host file contains something like:
127.0.0.1 site1.com
127.0.0.2 site2.com
127.0.0.3 site3.com
127.0.0.1:1 site4.com
127.0.0.1:2 site4.com
123.45.5.6 site5.com
123.45.5.6:33 site5.com
They all work as expected except for the imaginary external ip (only for example), and adding the port or not makes not difference. Seems i've tried what makes sense, say my external is '1.2" Creating a host entry like
1.2 # or
1.2:Port # the external IP with port
Also attempted adding an exclusion for he firewall to help ensure the traffic is allowed by doing:
netsh advfirewall firewall add rule name="Open Port" dir=in action=allow protocol=TCP localport=81
Kind of lost what might be missing, any suggestions?
Thanks for he help.
First. There is no need to add port after IP address in hosts file. Port can be configured on IIS by setting binding.
Second. If you want to allow any web client can access the site host on local WIN10 pro, you need to make sure WIN10 pro and web client are in the same LAN. Otherwise it is need to buy a public domain and bind to WIN10 pro device.
Using Ping command is a great way to test traffic between devices. It can help you make sure if web client can create connection with WIN10 pro.
I'm trying to install this software on my computer. http://remaddersoft.wixsite.com/remadder/download
It says:
"In order to be able to use ReMaDDer software, you must be able to establish connection with ReMaDDer server (matalab.hopto.org, port 5432) which is used for back-end fuzzy match processing. Contact your administrator to configure firewall to pass connections on matalab.hopto.org, port 5432."
How do I let the firewall connect to that software on windows 10?
Following below steps you can open the specific port on windows 10 -
Open firewall ports in Windows 10
You can manually permit a program to access the internet by opening a firewall port. You will need to know what port it uses and the protocol to make this work.
Navigate to Control Panel, System and Security and Windows Firewall.
Select Advanced settings and highlight Inbound Rules in the left pane.
Right click Inbound Rules and do the same for outbound rules and select New Rule.
Add the port you need to open and click Next.
Add the protocol (TCP or UDP) and the port number into the next window and click Next.
Select Allow the connection in the next window and hit Next.
Select the network type as you see fit and click Next.
Name the rule something meaningful and click Finish.
I couldn´t find a specific answer for my question so here it goes: We have a local network with 5 computers and a server running Windows Server 2003. The network was working properly but it seems that the server rebooted and we had to give a static DNS address to each workstation, otherwise they connect to the router 192.168.1.1 and are unable to access the local network or the Internet.
So my question is, how do you set up the server so that each workstation uses the server´s IP as primary DNS automatically? Or is it better to configure each client with a static DNS?
Thanks in advance.
First, open services (WIndows Key + R, services.msc, Hit enter) and check that 'DHCP Server' is running and set to automatic, if not, right click and select start. While your there restart the DNS Server service.
Secondly, if you are still getting your Router's DNS, log in to your router and ensure DHCP is disabled - you router may have been reset and this may have enabled DHCP which is causing all these problems.
Third, Open DHCP (Start > Administrative Tools > DHCP), Expand your server, you should then see a folder with 'scope' in the name, if not your DHCP needs to be configured (last resort), expand the scope, then select Scope options, it is in this that you will see the IP address of the '006 DNS server'. If it is missing, right click and select configure options, scoroll down to 006 DNS Servers and enter the name or (preferably) the IP address of your DNS server.
I'm 90% sure it'll be your router was reset.
I also thoroughly recommend you migrate from your Server 2003 machine to a new OS and new hardware if it is older than 4 years old as Server 2003 reached end of life on 08/04/2014 along with Windows XP and Office 2003.
Lastly, this may be more suited to ServerFault rather than StackOverflow (same family of websites)
I know it can be done for each of the site hosted but Can IIS's default port be set to a different one?
From the IIS management console, select Default Web Site. On the right-hand side, click the Edit Bindings link and in the subsequent dialog, change the default port binding as desired.
I found a different solution. My router was allowing traffic in correctly but Windows Firewall was not allowing traffic in on Port 80. I had to allow it by enabling the rule.
Prologue: I am running windows Server 2008 R2 on a Virtual Machine. This virtual machine image has been happily hosting TeamCity on port 80 for several weeks. This TeamCity server is accessed by others on the network by visiting a url (pcname.domain.com).
The Issue: It seems corporate decided to push some updates to my machine over the weekend. It seems this round of updates decided to install/update IIS. Low and behold, visiting the URL mapped to the TeamCity server actually takes me to the stock IIS7 page. Visiting url/login.html brings me to the TeamCity log-in page.
Attempts: First off, I changed the TeamCity port to 8080 and was able to access it at url:8080 (or localhost:8080). However, it is imperative to me that people can access the server without providing a port... so I change TeamCity server port back to 80 and set off to try and fix this IIS problem.
Since then I have uninstalled IIS7 by removing the role and services from Windows - I am now hosting "0 roles". I have removed every trace of IIS from my PC, but visiting localhost still gives me 404 not found (instead of server not found or just my TeamCity page).
My Question: How do I prevent Windows Server 2008 from trying to host some default crap on port 80 so that my TeamCity server can be seen again?
EDIT: After performing netstat -ano, the only PIDs associated with port 80 are '0' and '4' (system and svchost!)
In windows the usual suspects using port 80 are IIS itself, and maybe the Web Deploy Agent Service if installed (but it could have any other app bound to that port). The PIDs 0 and 4 just tell you that the applciation using that port is running as a service. If you do not need any of this (IIS, web deploy, etc), go to Services and disable them, the port should be free to bind after that.
You can use net sh http show servicestate | findstr HTTP to reach the address and port binding information.
A simple solution (one that I am also using in a production server with multiple apps) is to set up a proxy based on either the domain or the URL path itself (see here how to with nginx).
Hit command, netstat -ano in an elevated command prompt to see what applications are listening on which ports. This command will show you the PID of the process that is listening on port 80. Now, open the Task Manager -> Processes tab. From the View -> Select Columns menu, enable the PID column, and you will see the name of all the processes those are listening on port 80. You can kill the listed tasks. Mostly applications like, World Wide Web Publishing service, IIS Admin Service, Web Deployment Agent Service may use the port 80 in Windows Operating System.