Published SharePoint site login page taking time to load on Internet

Hi,

We have deployed TMG 2010 in our client environment. TMG is in Workgroup and is deployed with Single Network Topology. TMG version is 7.0.9193.540.

We have published an Internal SharePoint site on Internet with NO Authentication at TMG. the site is internally running in default zone with windows authentication. Users get the windows pop-up to authenticate themselves when they hit the URL on Internet and will be redirected to the homepage after providing the authentication credentials.

Next, client has extended the site in other zone with Form based authentication and we have published the site on Internet in a same way with NO Authentication at TMG level. The problem we are facing here is that the site login page loads in 2-3 seconds when accessed from the internal network but is taking a long time to load when somebody tries to access the same site on Internet.

Can anybody tell me what can be the issue for this? Is this a seen issue? We need a urgent fix for this.

Quick help will be appreciated.

Thanks,

Sanjog





November 13th, 2013 1:53am

Hi,

Thank you for your patience and support.

I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

Thank you for your understanding and support.

Best Regards

Quan Gu

Free Windows Admin Tool Kit Click here and download it now
November 13th, 2013 3:33am

Sanjog, I want you to try a couple of things for me. Put a client on the same subnet as TMG. Add a HOSTS file to it so that the name of your SharePoint site resolves to TMG. Try browsing it now. Is there a difference? If it is better then it is safe to say it is your edge device. If that doesn't improve the performance try browsing it from the TMG Server. Make sure that IE is set up to not use any proxies (including itself). Do you still see the issue? If you do, there is likely a problem between TMG and your SharePoint site. What devices reside in that data path? Simplify the path the data has to travel as much as you can and try to rule out certain devices.

SharePoint publishing is heavily reliant on your Alternative Access Mappings being set up correctly. Do you know if your SharePoint Administrator set these up? There are numerous articles available explaining these.

http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/25/alternate-access-mappings-explained.aspx

I have been supporting ISA/TMG/UAG for a number of years now and, in general, when we see these types of issues it is not a misconfiguration on ISA/TMG/UAG. In most of the cases there is some other network device causing the issue whether it be a Firewall, a load balancer, a WAN optimizer, whatever.

http://blogs.technet.com/b/keithab/archive/2012/02/15/top-troubleshooting-tips-to-try-before-calling-support-for-isa-tmg.aspx

Let me know if any of those suggestions help.

Keith

November 14th, 2013 1:43pm

Sanjog, I want you to try a couple of things for me. Put a client on the same subnet as TMG. Add a HOSTS file to it so that the name of your SharePoint site resolves to TMG. Try browsing it now. Is there a difference? If it is better then it is safe to say it is your edge device. If that doesn't improve the performance try browsing it from the TMG Server. Make sure that IE is set up to not use any proxies (including itself). Do you still see the issue? If you do, there is likely a problem between TMG and your SharePoint site. What devices reside in that data path? Simplify the path the data has to travel as much as you can and try to rule out certain devices.

SharePoint publishing is heavily reliant on your Alternative Access Mappings being set up correctly. Do you know if your SharePoint Administrator set these up? There are numerous articles available explaining these.

http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/25/alternate-access-mappings-explained.aspx

I have been supporting ISA/TMG/UAG for a number of years now and, in general, when we see these types of issues it is not a misconfiguration on ISA/TMG/UAG. In most of the cases there is some other network device causing the issue whether it be a Firewall, a load balancer, a WAN optimizer, whatever.

http://blogs.technet.com/b/keithab/archive/2012/02/15/top-troubleshooting-tips-to-try-before-calling-support-for-isa-tmg.aspx

Let me know if any of those suggestions help.

Keith

Free Windows Admin Tool Kit Click here and download it now
November 14th, 2013 9:41pm

Sanjog, I want you to try a couple of things for me. Put a client on the same subnet as TMG. Add a HOSTS file to it so that the name of your SharePoint site resolves to TMG. Try browsing it now. Is there a difference? If it is better then it is safe to say it is your edge device. If that doesn't improve the performance try browsing it from the TMG Server. Make sure that IE is set up to not use any proxies (including itself). Do you still see the issue? If you do, there is likely a problem between TMG and your SharePoint site. What devices reside in that data path? Simplify the path the data has to travel as much as you can and try to rule out certain devices.

SharePoint publishing is heavily reliant on your Alternative Access Mappings being set up correctly. Do you know if your SharePoint Administrator set these up? There are numerous articles available explaining these.

http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/25/alternate-access-mappings-explained.aspx

I have been supporting ISA/TMG/UAG for a number of years now and, in general, when we see these types of issues it is not a misconfiguration on ISA/TMG/UAG. In most of the cases there is some other network device causing the issue whether it be a Firewall, a load balancer, a WAN optimizer, whatever.

http://blogs.technet.com/b/keithab/archive/2012/02/15/top-troubleshooting-tips-to-try-before-calling-support-for-isa-tmg.aspx

Let me know if any of those suggestions help.

Keith

November 14th, 2013 9:41pm

Hi Keith,

Thanks for the reply.

It seem to be some network problem in the customer environment, due to which the page was taking long time to load on Internet.

The issue seems to be partially resolved. Now, we are able to see the login page quickly when accessing the site on Internet but the authentication is not happening. Even after providing the correct credentials, the user is unable to authenticate successfully and instead of going to the homepage, the user is redirected to the login page without giving any error.

The authentication is working fine in customer's internal network.

After analyzing the SharePoint and IIS logs, we have observed that the SharePoint server did not get the authentication request from the published site on Internet.

I am not sure if it is a problem at TMG or SharePoint. Is the issue familiar?

Quick help is really appreciated.

Thanks,

Sanjog


Free Windows Admin Tool Kit Click here and download it now
December 6th, 2013 1:14am

Sanjog,

What type of delegation method are you using on the rule? When you hit the "Test Rule" button on the publishing rule are you seeing any failures? If so, click on the red X and read the description.

Also, you can always test this using "passthrough" authentication and see if that works. Set the Web Listener to "No authentication", delegation to "No delegation but client may authenticate directly", and Users to "All Users". Does it work now?

What type of authentication is the Sharepoint set up for? Does the delegation method on the rule match what is expected?


December 19th, 2013 3:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics