Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We have several web apps that use Windows Authentication that worked fine on IIS6. After deploying them to IIS7, Windows Authentication no longer works (we get 401.2 errors) UNLESS we set the web app to use the "Classic Pipeline"
I realize that Forms auth and Windows Auth aren't simultaneously supported as mentioned here and here - but that is not my issue - I dont have Forms Authentication enabled. I only have Windows Authentication enabled - but I am always getting the 401.2
Has anyone run into this? Is there something else I need to do?
Thanks!
-Mike
There are two immediate thoughts: (1) is Integrated Windows enabled on the server as a feature in the role (2) is the authentication configured in the right part of web.config? IIS7 stores some of its configuration is web.config, and moving from IIS6 to IIS7 often involves adding extra information.
See also: http://forums.iis.net/t/1153827.aspx
A lot of the settings in the web.config move from system.web to system.webserver when changing from classic mode to integrated mode. For example custom httpmodules move into system.webserver. Do you have any httpmodules that are handling custom authentication?
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am trying to connect Via 2008 to a remote IIS 7 site on windows server 2008. I have installed the front page ext on my server and assigned users/roles to my various sites. When I try and connect via vs 2008 it prompts me for user name and password but will not connect. It seems like a simple issue but I cannot figure it out. What authentication modes must be enable on IIS. Anyone have any sugestions
I am not running ftp on the server in question. When the drive was shared VS could access the directory fine. IIS is running windows authenication mode.
Make sure the VS2008 user has windows permission to access the target folder(s).
Make sure the firewall (windows and external, if there is one) has the proper ports open.
If VS2008 is using FTP, try active instead of passive. If that makes a difference, there are some special things you can do to make passive FTP work.
Make sure IIS is set up properly for ftp and/or front page extensions, application pools, etc.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm setting up a .NET v4.0 web application on a Windows 2008 R2/IIS 7.5 server that uses a domain account for the application pool identity. When I access the site, I get the following error:
The current identity () does not have write access to 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files'
According to this: http://learn.iis.net/page.aspx/140/understanding-built-in-user-and-group-accounts-in-iis/ the identity of the worker process is added to the IIS_IUSRS group when the process starts. This seems to work fine for the existing .NET v2.0 applications I have running on the same server (I have not had to add their domain account application pool identities to IIS_IUSRS group). This does not seem to be the case for the first .NET v4.0 web application I'm setting up.
Once I add the identity to the group, everything works fine. I suspect something is not configured correctly that is forcing me to do this. I would like to understand this before rolling out more sites/servers.
Thanks in advance for your help...
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have installed Windows server 2008 r2 on a virtual machine, Can I install Active directory with domain controller + IIS + SQL server on the same machine? I want to make web application and this web application will authenticate users from Active Directory, the web application should be published on the server IIS and the users should access it remotely from their home using domain name of my machine, Someone tell me that its very wrong to have IIS and Active directory on the same machine.
You can't use ActiveDirectory over the internet. At least not without something like a VPN as a middle man. Their home computers will not be joined to the domain, so there is no pass-through authentication.
Yes, it's a bad idea to put AD on the web server. Why is too complex to get into in an answer here. Suffice it to say that even if you did do this, it's probably would not work the way you are thinking it should.
It's not impossible to do this. For instance, many of the Microsoft "Small Businesss" products put IIS, AD, and SQL Server on the same server. But, you kind of have to know what you're doing to configure it securely.
Can I install Active directory with domain controller + IIS + SQL
server on the same machine?
Yes. Not usually recommended, but certainly possible.
the web application should be published on the server IIS and the
users should access it remotely from their home using domain name of
my machine
If you intend to use Windows Authentication, it is challenging to get that to work correctly; you will probably need a VPN as a minimum. If you just want them to type in Windows credentials, then do you really need a domain? Could you just use regular Windows users?
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have an old asp.net web application based on .net framework 1.1, it has been deployed to live server for many years, right now I am having some issues with the live site only, the development version on my desktop works fine. So I am thinking about attach a remote debugger to the live site and monitor what happened exactly on live server, but I don't know how to do that.
I used remote debugger before, but that was used when I created new project on some development server in local LAN, and the source and project is actually on the remote server, I just attached remote debugger from my desktop to that server, it works fine. But I am not sure how to debug a application on live server.
Well yes it is possible, but is more involved. You would need to attach to the IIS worker process running the website( w3wp.exe). I haven't done it very often, and I usually try to avoid it, because while you are attached no one can access the website.
Here is an article that explains the process.
http://www.codeproject.com/KB/aspnet/ProcessAttache.aspx
The article is based on 2.0 not 1.1, but it should still give you an idea of how to do it. I suppose you will have to have visual studio on the production server.
If this is not feasible and you have access to the code, you could also try logging to a text file at certain points in the application. I have done this very effectively to find issues, which allows you to let the website run as normal and just check the log file after you know the problem has occurred.
You may want to check out log4net, which is a free logging application.
Good luck
Well, why don't you try to enable tracing on the server? Then you can see all of the information in a separate page? To enable in the web.config:
<configuration>
<system.web>
<trace enabled="true" pageOutput="false" requestLimit="40"
localOnly="false"/>
</system.web>
</configuration>
Then load the trace.axd page in your website to see the page level data.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
How can I get SMTP to work on a Windows 7 development box? I used to just be able to turn on the IIS SMTP server on Windows XP. Is SMTP not included with Windows 7? If so, what can I use instead as a free relay mechanism?
If you are developing in ASP.net using the built-in mail libraries, a lesser-known configuration setting is to use the following:
<configuration>
. . . more config stuff here . . .
<system.net>
<mailSettings>
<smtp deliveryMethod="SpecifiedPickupDirectory" from="noreply#testdomain.org">
<specifiedPickupDirectory pickupDirectoryLocation="c:\smtp\"/>
</smtp>
</mailSettings>
</system.net>
</configuration>
All your application generated emails will be dumped into this directory during development. No smtp server needed!
SMTP isn't included with Windows Vista, either - you'll have to download and install a free third-party SMTP server. There are a number available - http://www.softstack.com/freesmtp.html being one.
UPDATE: Some more options - Vista's IIS Instance doesn't have SMTP (Solutions?)
You can use Google's as a free relay, however you need to have a Google account.
smtp.gmail.com
Just make sure the ports are setup as defined for your account.
According to this post, the issue an SMTP server was included in IIS6, but has been removed in IIS7. This thread suggests the Remote Server Administration Tools (which include a SMTP server), as long as you don't have the Home edition of Windows.
I use "Free SMTP Server" from Softstack.
http://www.softstack.com/freesmtp.html
HTH
For those still coming across this, I've played with the two servers suggested above (freesmtp and hmailserver). Freesmtp is very quick and simple and worked out the box but only lets you send 10 emails a day without paying $69. hmailserver takes longer to set up (although still fairly painless) but has more features and hasn't asked me for money (yet).
I had the same problem, and I installed hMailServer.
http://hmailserver.com/