Poor performance on SharePoint site (IE6, Proxy, Windows Auth)

Jaap Vossers
  • Poor performance on SharePoint site (IE6, Proxy, Windows Auth) Jaap Vossers

    This is a very strange issue I am having.

    My client is experiencing poor performance (20 sec per page load or so) when accessing their SharePoint 2007 site that is hosted somewhere externally by a hosting provider. In fact it is not just that particular SharePoint site - we tried accessing another SharePoint site that is online and we were experiencing the same performance issues.

    Now it is ONLY slow if ALL of these conditions are true:

    1. User is using IE6
    2. User is using a machine connected to the client's company network (there's a proxy Configured)
    3. User is authenticated (Windows Authentication)

    So to back these theories up:

    1. We have tested with FireFox and IE 8 from within the company network and it's performing well (both authenticated as well as unauthenticated).
    2. We have tested with IE6 from a machine that's not on the client's company network and it's performing well (both authenticated as well as unauthenticated).
    3. We have connected to an online WSS team site (out of the box) that is open to anonymous users with IE6 using a machine that's connected to the client's company network and it's performing well.

    Some other interesting facts:

    1. Accessing over HTTPS or HTTP doesn't seem to make any difference
    2. The client has another SharePoint system (based on SP2003 and requiring Windows Auth) which is hosted internally (so not going through the proxy), which is performing just fine.
    3. Client's internet connection is just fine for all other sites
    4. To make it even weirder, the mobile view (add "/m" to subsite url) seems to be performing fine! Though I think it's just because these pages are just so tiny.

    I get the impression that is has something to do with the way IE6 handles Windows Authentication in combination with the proxy used in the client's company network. Does that make any sense? I'm a developer so it could well be that I am talking rubbish here :)

    Ideas anyone?

  • Your analysis was correct. There is a problem with IE6 and windows authentication against IIS 6.0.

    This problem occurs because the Internet Explorer 6 client regularly resets the TCP connections

    See http://support.microsoft.com/kb/922703 for how to get around it.

  • Network guys have resolved the problem; I have been told the following:

    It turned out to be a DNS problem.

    Apparently there was some legacy network configuration that would force clients to use an internal DNS for this particular domainname and this DNS was not capable of resolving the IP address for this web site properly (not sure exactly how/what/why).

    Additional problems noticed were centred around authentication requests and re-authentication requests from the site and the proxy server.

    To backup the above theory: the act of adding a hosts file entry on the client fixes the problem.

    I still don't understand why it's only IE6 though...

Tags
administration performance networking
Related questions and answers
  • We have an issue in accessing custom a DB from a SharePoint custom webpart. When we try to access the custom DB from SharePoint webpart we are getting the error "Login Failed for User NTAuthority..." and DB Server Instance has the same user "domain\someuser" and has permission to Custom DB. Web.config entries: <authentication mode="Windows" /> <identity impersonate="true" /> The connection string we are using is "Data Source=xxxx; Initial catalog=yyy; Integrated security=true;" We have tried with a small change in conneciontion string as well "Data Source=xxxx; Initial catalog

  • I am using SharePoint 2007 Enterprise + Publishing portal template + Windows Server 2008. I am developing using VSTS 2008 + C# + .Net 3.5. I need to implement SSO (Single Sign On feature) with another site. The SSO protocol is like this, The other site will send me information like http://mysitename/default.aspx?Identity=abc or like http://mysitename/default.aspx (mysitename is the site which I am developing); If the value Identity variable is null, it means anonymous user. And if the Identity value is not null (means an authenticated user), I will using a WCF interface to find user

  • is, when a user access a page for the first time in my SharePoint site which needs authentication, if there is a special URL variable in current http session called "Identity", I want to treat the user as authenticated user and using the value of the "Identity" URL variable to be the authenticated user name of SharePoint (for example, accessing my SharePoint site by URL http://mysite/default.aspx...I am using SharePoint 2007 Enterprise + Publishing portal template + Windows Server 2008. And I am developing using ASP.Net + C# + .Net 3.5 + VSTS 2008 on SharePoint Server 2007. I am developing

  • Using WSS 3.0 running on SBS2008. I have an Infopath form library, to which I have used SharePoint Designer 2007 to attach a custom workflow. It's a pretty normal workflow which updates a property in another list based on a lookup. I have two users, call them Jane and John. Jane is a member of several SP groups, one of which has Full Control permissions. John is a member of a couple of SP groups, one of which has Contribute permissions. I have 2 workstations, lets call them W1 and W2. Both are on the local area network and connect to the SP site via Internet Explorer 7 via http://example

  • Scenario: We have an internal application that ties Excel spreadsheets stored in a SharePoint doc lib with specific Opportunities in CRM. The user clicks on a button in the Opportunity and a Web...) { objExcel.ActiveWindow.Close(false); objExcel.Application.Quit(); alert("This workbook is opened for editing by another user. Try again later."); } Usually the above works just fine... to them by SharePoint as read-only (so they will get the above error message). However, often they are demonstrably the only user to have accessed the document - in fact, sometimes this will happen

  • be opened. For applications using SharePoint web services we will extend the web application and have an internal url with only Windows authentication enabled. ...We recently migrated some applications from SharePoint 2007 to SharePoint 2010. The application uses the SiteData.asmx web service. After the migration there are Access Denied errors, withtout any..., GetSiteAndWeb) The error happens when running as a farm administrator. The same error happens running on a local development machine, which makes me think it has nothing to do with user permissions

  • So I recently had a nice hitch in the SharePoint app I made for my client. We have a Document Library which is supposed to contain PDFs, converted from drawing files made in other programs. The test system has been deployed for public testing for his clients. This is real site usage, by the way, so real corporate data is being transfered. The site had been tested to be stable on the code side... situation. Because this is a real field test, I cannot simply upload the new PDF file and run it through the process, I need to maintain the field data from the original file, in all of its versions

  • only site collections/sites using non-publishing templates. All other content is availble e.g. documents, lists Has anyone else come across this? UPDATE 08/05/10: I have been doing some further...This is an old issue I thought this was a bug in an specific environment after reading a couple of blogs it has made me think again... The issue is that SharePoint site collections and sites... in the index under the contentclass:STS_Site and the sites (SPWeb's) are contentclass:STS_Web. The following people seem to have come across this issue and assumed it was just a limitation. I think

  • . Which one will make itpossible to create a rich user interface? Develop on Sharepoint Foundation 2010 or Sharepoint Server 2010? I've seen differences in services they support, but since I don't have...I'm about to start developing a custom business application on top of Sharepoint 2010. I haven't done anything on this product but client insists on it so I don't have a choice. Application info I..., but as this app will run under Sharepoint all this will be done by it. I won't have to handle authentication/authorisation. Application will run processor intensive business processes and it will support three

Data information