I have a win 2008r2 server. The default website has Enabled Protocols set to "http,net.tcp". When any new applications are created under the default website I would like then to default to having the same enabled protocols. Could anyone please advise how to do this? Currently when I Add Application one is created with an enabled protocol of only "http"
I found this was possible using the IIS provider for Powershell. The following line worked for me:
Set-ItemProperty IIS:\sites\$NetTcpWebsite -name EnabledProtocols -Value "http,net.Tcp"
In order to get the protocols to cascade from the website level down to the application level I had to do the following:
First I created the website and the applications.
Second I ran the following:
$iisAppName = %YourWebsiteName%
Set-ItemProperty IIS:\sites\$iisAppName -name applicationDefaults.enabledProtocols -Value "http,net.tcp"
That solved it for the original question. The answer from Rob will only set the Enabled Protocols profile at the website level which leaves your applications and virtual directories without the proper protocols enabled.
net and tcp protocols are used for WAS. They are disabled by default to minimize the surface for attacks.
Are you hosting WCF applications in order to need this?
http://technet.microsoft.com/en-us/library/cc735229(v=ws.10).aspx
Best regards.
I struggled with this for a while and looked at ways to include it in the MSI (WiX or other) or in the web.config file of each application or service. In the end the easiest solution was to change the Website default in IIS so that it applied to every application and service without needing to change the MSI or web.config. Basics steps are: In IIS Manager, click on the Sites node, then click "Set Website Defaults...", change the "Enabled Protocols" property to http,net.tcp
Related
It's in the title really....
I've got MSMQ receiving messages via HTTP on the DEFAULT web site. which is just assigned an IP Address.
I need to be able to push messages into the queue with a specific url (that won't be blocked by proxy etc. in production).
Problem is, MSMQ only installs to 'default web site'. And my feeble attempts to install it else where have failed.
Added Bindings to net.msmq and msmsq.formatname to the 'non-default web site', I used 'binding information' as 'localhost' since that works on the 'default web site'.
Created a web application on the non-default website; points to the same folder (inetpub\wwwrot\msmq). [I guess this is where it's not working, how's that supposed to 'magically' work??
I thin added the net.msmq and msmsq.formatname protocols to a 'web application' I called MSMQ on the 'non-default' web site.
The above steps are basically the same, and I've done this too, as runnig the variouse scripts found here: http://channel9.msdn.com/shows/Endpoint/endpointtv-Screencast-Configuring-WAS-for-TCP-Endpoints/ and http://geekswithblogs.net/sathya/archive/2011/08/17/the-protocol-net.msmq-is-not-supported.aspx
All with no joy.
I just need to use a specific domain to receive my msmq http messages, any help appreciated.
PS, in production it will also have SSL cert on the domain. (on win server 2008 r2)
I gave up in the end, achieved my goal by
Uninstall msmq with http
Stop Default and 'target' website (I actually didn't do this but should have!)
Go into advanced settings in IIS and change the Site Id of Default website to '99'
Go into advanced setting in IIS and change the Site Id of 'target' website to '1'
Restart IIS/Server up to you.
Check that websites still work!
Add MSMQ with http feature back.
Done, I have MSMQ installed where I wanted.
NOTE: I had to manually add the bindings for net.msmq and msmsq.formatname to the 'target' website. The installer didn't do that this time (nor did the uninstall remove them from 'default website').
hope someone can provide me some insight on this iss problem!
Th situation is this, i understand that upgrading to IIS7 is absolutely necessary for security but will do so in the future but now, i'm using IIS6 and would like to force IIS6 to display qualified hostname of the IP address.
So far my other websites had gone through and been changed to display the qualified hostname but my dotnetnuke server (version 4.08.04), i am unable to locate the file(dnn or iis6) to change this.
I've used this procedure below for changing
IIS < 7
Force IIS to Display Hostname
It is possible to force IIS to display the hostname of the server instead of the IP address via the following:
Open a command window
Select "Start"
Select "Run"
Type in "cmd" and press enter or select the "OK" button
Browse to the "C:\inetpub\adminscripts" directory (or wherever this directory is located on your server)
Run the following commands:
adsutil set w3svc/UseHostName True
net stop iisadmin /y
net start w3svc
The IIS web service will now return the qualified hostname instead of the IP address.
You can do this with a setting in DNN using the Ifinity Friendly URL provider http://www.ifinity.com.au/Products/Friendly_Url_Provider_For_DNN
Because you are on such an old version of DNN thought you might have to go back to a fairly old version of that provider to make it work. DNN 4.8.4 has quite a few security bugs, so upgrading to a later version of DNN (even on IIS 6) would be ideal.
I believe you could upgrade to DNN 6.2.8 (or whatever the last 6.* release was) without having to upgrade IIS, though you would need .NET 4.0 for any version of DNN after 5.1
I am new to the web world, so I apologize if this question is silly.
I have an ASP.NET web site I wish to deploy.
The server has IIS 7 deployed on it, and I've added the site
to that IIS server as a web site.
For the time being I don't have a domain mapped to the site,
I would like the users to browse for the site directly by using the server's IP.
Is that even possible? because I failed to do it.
The only option that worked so far is using the hosts file to declare
a fake domain.
It would be nice if someone could clarify that issue for me.
Thanks a lot,
Omer
If you set the site bindings to IP address: All Unassigned on port 80, and do not provide a host name, then any request that makes it through to IIS should be served by that site. Make sure you stop any other sites that might have that binding (e.g., "Default Web Site" is normally bound to this).
In order to access the site by IP, you can't have the host name populated in IIS. Your best bet would be to use the "Default Web Site" that's already in IIS, and point that to your application.
Using IP is possible, but you need to make sure your users can see this ip from their machines.
I've copied a whole folder which keeps a website inside from a web server to another computer.From the original server I can easily run the web application. Now I need to know what exactly I have to do in order to be able to run the application on the second computer too. I think there are some special considerations with IIS. What and how do I have to set up in IIS?
Follow these steps.
create a new site from left menu By right clicking and add new website.
Give physical path to that folder
Map with the site url
Give permissions to Directory as (like everyone)
Set up the default page if (index page is not present in the directory)
Set framework which ever you are using.
Install the IIS Windows component for whatever version of Windows you're using.
Create a new site in IIS
Point this new site to your web root
Configure DNS for the site (maybe using your hosts file)
There are some considerations to make depending on which version of IIS you are using. It would be helpful to know if you are using 6 or 7.
If you are under 7, you need to copy the site to your IIS directory (typically wwwroot) and then setup the basic settings in IIS by choosing your application pool and such. Application pools are typically (but not always) setup by .Net Framework. You may need to setup your default page and set it as an application. There are many blogs and sites out there that will tell you how to setup this basic functionality but are specific to your application.
For configuring IIS
1. Firstly, in Programs and features go to Turn on and off windows features...in that tick everything under IIS..go to sub folder and tick everything everywhere
Go to Internet Explorer> Setting> Internet Options> Advanced> untick Show friendly http error messages option
Go to IIS manager
a. In default application pool> advanced settings > Set true enable 32-bit program option
b. Go to Asp> setting> expand debugging properties> there will an option of error messages some 2nd last or last option that would be false...set it to true..apply changes
Run vbscript and asp only in Internet Explorer (edge 10 in developer options for pop ups)
I've created a copy of our legacy, (decrepit) homegrown Timesheet ASP application on to a different, newer workstation for backup purposes.
I've finally got it to the point where I can run it locally over http, using this address:
http://localhost/timesheet/Timesheet.asp
I would like to test it over the network with an address like this:
http://backupServerHostname/timesheet/Timesheet.asp
The live application uses a similar addressing scheme. I'm just not clear on what needs to be done to make this application available from the new server.
You'll want to ensure that backup server isn't using windows firewall or something to block port 80 access. Also you may run into permissions issues if your asp app isn't set to allow anonymous access (assuming you want that).
Goto the folder where the Timesheet web stuff lives (could be C:\Inetpub\wwwroot\TimeSheet, just a guess).
Then Right-Click on the folder, select "Properties", then click the "Web Sharing" tab, then select "Share This Folder" option, this should bring up an "Edit Alias" window. Change the alias to "backupServerHostName".
This is assuming all the machines on on the same LAN.
Nothing needs to be done. If it is serving localhost on Port 80, it should serve other computers on your local network using a name similar to the one you gave. It may literally be as easy as just trying it...
If you just need to browse to it from other machines at work, just replace the "localhost" part with your machine name.
If you need it accessible over the net, you need to install it with IIS on an outward-facing server, and then browse to it that way.