I'm trying to start the default website of IIS 8 on Windows Server 2012 R2 Essentials and I get a message with the error, "This website cannot be started. Another website may be using the same port."
The ports the website is trying to use is 80 and 443.
The other ports being used are 65520 and 65500.
When I look up the service which is using the port in Netstat (Command Prompt), it comes up with PID 4. In the task manager, it says that "SYSTEM" is using it. I can't end SYSTEM.
What's wrong?
Related
We have a VS project in this location:C:\inetpub\wwwroot:
project in VS
this project run perfectly,
we uploaded the IIS and it is run perfectly in the local computer that contain the IIS inside.
then we took the computer name and from another computer, in the same local network, we tried to put in the address line, on the browser, the name of the computer that the IIS is installed there and I got this error:
This site can’t be reached
laptop-******** took too long to respond.
my error
You can check these options:
If there is running firewall on the computer, where IIS is running, make an inbound rule for your port (in your case 11111).
On client PC, access IIS with "computer-name:port/webpage.html" (in your case "laptop-g3j5vgcc:11111/panel/login.html") .
You may also change the port of your web site (if you want to use port different from 11111).
Open IIS Manager.
Select your website and choose "Bindings ...".
Change port and confirm.
Restart your web site.
I'm using VS2015 Update 1 to try and debug my site which I've uploaded in Debug mode to an Azure web app (NOT a vm). I am working from my work domain.
I've been following instructions similar to found here https://samlman.wordpress.com/2015/02/27/another-cool-way-to-remotely-debug-azure-web-sites/
I have:
Published my website in Debug configuration
Enabled Remote Debugging from the management console
Made sure my VS edition is set to 2015
Enabled Websockets (from trying to connect via websockets)
Checked that the firewall allows VS remote debugger, remote debugger monitor and remote debugger discovery through.
Checked the website is up and running (set it to always on just in case)
I have tried right clicking my app service in Server Explorer and "Attach Debugger".
I then tried to connect using Debug > Attach to process and using the qualifier mysite.azurewebsites.net as instructed on various blogs. Even tried transport as Websocket, Remote as well as Default.
All methods get me the following:
I then used Fiddler to see if I could find the answer from web traffic but no joy with that.
Would appreciate any suggestions to get me around this problem!
Edit
Under scm -
There was another firewall I wasn't aware of on the domain that was blocking the debugger.
Edit:
Ports requested
outbound:
UDP 3702
TCP 4020
TCP 4021
Port assignments are given here on MSDN page
In Windows 10 IIS and Xampp use the same port (80), I've learned. I know how to change port in Xampp, but I'd prefere to stop IIS while using Xampp. On my old computer with Windows 10 I went to task manager > services and stopped World Wide Web Services by rightclicking. On my new computer with Windows 10, I can't seem to find World wide web services on that spot. Can it be named something else, according to language (swedish - though before on the old computer it was named as mentioned)? Any other way (in simple steps, please - beginner!) to stop IIS using the port, without disabling the IIS alltogether? (might want to learn how to use it later on)
Thanks in advance!
Port 80 is used by default with many web servers (here IIS and Apache which is bundled inside XAMPP).
The default web site created with IIS uses port 80. If you don't want to use this default web site (absolutely no harm and no data loss!), you can delete it by running the following command in inetsrv directory (path would generally be C:\Windows\System32\inetsrv).
appcmd delete site "Default Web Site"
Or you can change the port for the default web site in IIS, with:
appcmd set site /site.name: "Default Web Site" /+bindings.protocol='http',bindingInformation='*:8000:']
appcmd set site /site.name: "Default Web Site" /-bindings.protocol='http',bindingInformation='*:80:']
(8000) is for instance, use any high number you like.
I am using AWS EC2 instance on Windows Server 2008 R2, I deployed an application in IIS on port 80. I am able to access it anywhere. The security group is as follows:
HTTP TCP 80 0.0.0.0/0
Then, I installed NodeJS for windows and deployed a simple node application to the same port. When I browse to localhost on the server I see my application working, but when i browse from a different pc, I cannot access it. How is it accessible from IIS but not from NodeJS?
I've seen this question on stackoverflow and the answer is ussually to set the TCP port in security groups in AWS cosole but I've already done that and it doesn't work. Any other ideas?
For those who are having the same issue, if you install nodejs you will need to change some windows firewall settings to expose the port:
Open Start Menu -> Administrative Tools -> Windows Firewall with Advanced Security
Click "Inbound Rules" from the left window
Click "New Rule..." in the Actions window on the right side
follow the prompts to customize the rule and be sure to add the port that your nodejs application is using. Make sure to name the rule so that you recognize it later
In the Inbound Rules window find and double click the rule you just created. Under Programs and Services, select "This Program:" and browse to your node.exe file.
Last but not least make sure this port is open in AWS console security group inbound rules too.
I am completely new bie to IIS.
I have a very basic knowledge about how to configure IIS.
Today I have a requirement to access website Globally through WAN (through internet from any PC all over world) which I have deployed in my Local IIS.
The website=> SilverLightBusinessApplicationWeb
which you can see in my below screen shot can be open in LAN nicely.
so I only looking for how to open it in WAN?
So anybody please suggest me a simple steps or instruction for it.
You can see two screen shot of Internet Information Service (IIS) Manager.
NOTE: 1. I also have static IP 2. i am using IIS7.0 with Windows-7
Thank you so much…..
1. Screen Shot1
2. Screen Shot2
This question is probably better off on ServerFault. However, providing you have everything set up on your machine, you just need to open and forward port 80 to your host machine and set up a domain or access the site directly via external IP providing your bindings are set up correctly.
EDIT From a security point of view, it would be better practice to do as Germann said by having your public facing web server in its own DMZ.
Finally i have got it........
the steps i have followed are......
define port forwarding at router for that i have enter following values in my router's forwarding page.
--IP address of my PC
--port number which is open(you can see screen shot Brouse*:80(http) which shows port 80
is open for website on my IIS.
finally i have opened website on my IIS by : .http://mystaticip:port/xyzfolder/xyz.html.