.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Sharepoint in DMZ and Windows Authentication problems

Posted By:      Posted Date: October 20, 2010    Points: 0   Category :SharePoint


i'm trying to set up Sharepoint in DMZ. the sql server is in corporate domain, the sharepoint farm in perimeter domain (dmz).

A trust relationship is established in which the perimeter domain trusts the corporate domain

the problem is this: when i run sharepoint configuration wizard i cannot connect to sql server using windows authentication- i get those error messages on sql server:

error1: Login failed for user '. The user is not associated with a trusted SQL Server connection. [CLIENT: xxx.xxx.xxx.xxx]

(please note the username does not show up, xxx - ip address )

error2: SPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed. [CLIENT:xxx.xxx.xxx.xxx]


so i run  "psconfig" per microsoft article   http://support.microsoft.com/kb/932376/en-us and used SQL authentication.


that worked fine. wizard completed, i'm able to conect to sharepoint configuration site, but when i want to create a new web application and use windows a

View Complete Post

More Related Resource Links

Integration of Windows live Id authentication with Sharepoint 2010?

Dear folks,   please give me some details about Integration of Windows Live Id authentication With SharePoint 2010? Thank you Regards Immanuel c

SharePoint crawling - Windows authentication failing for STS4?

In a Sharepoint 2010 installation, we are trying to crawl the content of a small, single-node SharePoint installation. The crawling is partially successful. We are able to retrieve data delivered from the web services (_vti_bin/sitedata.asmx), but when the crawler tries to access the full page contents, it fails. The error message shown in the Crawl Log is: The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. The error which is logged in the ULS is: 08/27/2010 01:52:02.92     mssdmn.exe (0x0A7C)                         0x03E4    SharePoint Server Search          HTTP Protocol Handler             du54    High        CHttpAccessorHelper::InitRequestInternal - unexpected status (500) on request for 'http://staging.dsr.dk/_layouts/error.aspx' Authentication 1.  [httpacchelper.cxx:657]  d:\office\source\search\native\gather\protocols\http\httpacchelper.cxx      08/27/2010 01:52:02.92     mssdmn.exe (0x0A7C)          &n

Problems with Windows Authentication

I have one webserver alone in the network and all the users authenticate in another server. I'm trying to implement windows authentication in a application in the webserver,  but every time that the page loads a login window appears exactly that the windows client was authenticated in the order server. Is It necessary both server stay in the same domain? Is there another way? Finally, I need to get the user id in the windows client, but webserver and domain server don't communicated between itself. []s Emerson Paz

need help with sharepoint (wss 3.0) with Windows authentication and Custom Role provider

I'm trying to setup sharepoint(wss 3.0) to use my custom role provider with Windows authentication. I've modified the web.config to enable role manager and I am able to select my custom roles when assigning permissions but it doesn't seem like sharepoint is check the permission again my custom roles. If I enable Forms authentication and use my custom membership provider it all works as expected but I do not want to use FBA because of the issues with Client Integration. Essentially I want all the features that comes with the default windows authentications but just have permission be control from my custom role provider. Can anyone offer any solution or suggestions?

Authorization Manager (AzMan) as role provider with Windows integrated authentication in SharePoint


Hi all,

First I will describe my environment: Windows Server 2008 R2 x64, IIS 7, SQL Server 2008 and MOSS 2007 Enterprise Edition SP2 x64.

I am trying to setup SharePoint 2007 portal to use Windows integrated authentication with Authorization Manager (AzMan) as role provider.

I have set up an authorization store and defined a set of roles in there. Further I configured the web.configs of my SharePoint environment to use AzMan as role provider.

In IIS I see the roles appearing, but unfortunately those roles are not available in my SharePoint portal. I also see notification in IIS stating that Forms authentication has to be used

What should I do to configure it correctly? Is it even possible to use AzMan with Windows authentication in SharePoint 2007?

Thanks in advance.

With kind regards,




ASP.net 3.5 Windows Authentication Problems


I'm new to ASP.net and trying to set up an Intranet site with Windows Authentication.   

I have configured the web.config as shown below.

<authentication mode="Windows">
<roleManager enabled="true" />

I wanted to do authorization by roles so

          <deny users ="?"/>
          <allow roles="D820\MySite_Developers, D820\MySite_Admins"/>

I'm in the D820\MySite_Developers group.

When I attempt to login, it wants my password.  I thought that with Windows Authentication it should not prompt for the password.

If is use <allow user="*"/> it does not.


1.  Is this the correct behavior?



Windows or SQL Authentication with SharePoint

Does anybody know where there is information on which SQL Authentication method is best to use with SharePoint? I need to know which is best, if I use SQL authentication what are the limitations etc. Any help would be appreciated.

SharePoint Farm - Claims Based Authentication Problems


Hello guys,

I have a SharePoint farm with 2 WFE servers(SH01 and SH02) and 1 Application server(SH03) where there's the Central Admin. When I create a WebApplication with Windows Authentication I can access it normally in both address http://SH01:10000 and http://SH02:10000. When I create a WebApplication with Claims Based Authentication enabling FBA when I try to access it with the address above occurs an error:

The WebApplication at http://SH01:10000/  could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

I have noticed that the difference between authentication is that FBA redirect to "_login/" when I can choose what type of authentication I want to login(In this case Windows or Forms).

Are there some extra configuration that I have to do to solve this problem?


André Rentes

Windows authentication issue - unable to run report from sharepoint library


I have an extended Sharepoint web application which allows windows authentication access and in the Reporting Services Integration section in Central admin i have selected windows authentication.  I have written a SQL report which uses an XML datasource and uses windows authentication to connect to the sharepoint lists. 

  • The datasource connection string is: http://<my windows authentication site>/_vti_bin/lists.asmx
  • The reportserver url i've given in my report solution is http://<my windows authentication site>/

I can preview the report from within Business Intelligence Studio and it returns the data correctly.  I created a document  library and set it up for reports, deployed my solution and tried to run the report but i get the error :

An error has occurred during report processing. (rsProcessingAborted)
Cannot impersonate user for data source 'MyDataSourceName'(rsErrorImpersonatingUser) .  This data source is configured to use Windows integrated security. Windows integrated security is either disabled for this report server or your report server is using Trusted Account mode. (rsWindowsIntegratedSecurityDisabled)

I can across this link (http://msdn.microsoft.com/en-us/librar

Getting Started with Windows SharePoint Services

Of all of the capabilities of SharePoint, I thought I would start with the most basic installation - as a corporate intranet. It is likely that we will need to discuss some of the elements of SharePoint as we go along, so this also gives us the opportunity to review these elements for future reference.

Before going into too much detail, I would like to point out that you can try the core SharePoint framework (known as Windows SharePoint Services or WSS) for free. On Microsoft's Web site you can download a trial version of Virtual PC 2004 (VPC). Using VPC, you can install the Windows 2003 Evaluation Kit and the WSS add-on. This combination will give you 45 days to evaluate the setup.

Building a Searchable Phone Directory with Windows SharePoint Services

I want to continue to build out the intranet site we've started in our previous articles. A standard item in every intranet is a staff/employee list. Most companies implementing Windows SharePoint Services (WSS) are large enough to have a database that contains all employees. We will use the aggregation features of SharePoint to include data from this database into our intranet.

New Features in Windows SharePoint Services 3.0

Windows SharePoint Services 3.0 (WSS 3.0) is the next version of WSS 2.0, released on 2007, and Microsoft Office SharePoint Server 2007 (MOSS 2007) is built on top of this. Windows SharePoint Services 3.0 takes full advantage of Microsoft ASP.NET 2.0 and the core Microsoft .NET 2.0 runtime. WSS 3.0 offers a lot of new features and programmability support. I have consolidated a list of new features and enhancements in the below section:

Web Matrix + Windows Authentication


I'm curious if its possible to get windows auth working with asp.net webpages/webmatrix.

I've got it published to IIS with windows auth turned on and anonymous/forms/basic turned off.

I'm guessing the WebSecurity Helper probably won't work here but can you access User.Identity.Name etc?

Sorry for the newbie questions, I've only just started working with asp.net ^^,

Problems with Forms Authentication in DD 4 site


Hello,  I am seeing a strange problem with Forms Authentication in my DD site.   A user logs into and can view/edit/delete data all day, but when they execute a Custom Filter against data (for example , a control DynamicData/Filters/CustomerLastNameSearch.ascx ) then the site auth fails, and redirects to the log in screen.

in web.config I have

     <authentication mode="Forms">
            <forms name=".Star" loginUrl="~/Login.aspx" protection="All" defaultUrl="~/Default.aspx" path="/" timeout="43200" cookieless="UseCookies" />     

Offhand, I am thinking two things : that DynamicData/Filters path requires some special handling for some reason, or the control extension ascx is causing auth to get confused.   Has anyone else experienced this or have any suggestions?  Thanks!

Windows Authentication for IIS in Windows 7 Home Premium Edition - for ASP Websites.


How to create a virtual directory and get benefit of the IIS. Is there a workaround to accomplish this without the Windows Authentication for Windows 7 Home Premium Edition?

Thanks in advance, 

Using windows authentication to access SQL when using ASP.NET 4.0 via COM+


I am using SQL Server 2008 under windows authentication, front end is ASP.NET which uses COM+ to access database.

COM+ components are configured to run as domain user.

When looking through the logs (SQL Profiler), I can see the login name as the configured identity instead of windows indentity.

I have got Website running under "Intergrated Windows Authentication" and database is running locally on webserver.

Web configure contains entry for <identity impersonate="true"/>.

My connection string is

connectionString="data source=db01\test01;initial catalog=test; integrated security=SSPI;persist security info=False; Trusted_Connection=Yes"

Any ideas?




Take Control: Use SharePoint to Manage Your Windows Services


In this article, we show you how to integrate a Windows Services-based solution with SharePoint. The results enable you to provision, start, stop, and remove service instances through SharePoint 3.0 Central Administration.

Pav Cherny

MSDN Magazine April 2009

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend