TMG 2010 NLB - best practises

Hey,

I've been using TMG array for last 2-3 years and noticed few weird things. I see the more TMGs I add to the array, the more weird it becomes.. TMG is used mainly for Exchange publishing, therefore there any lots of connections and since TMG is handling the authentication, once in a while, during peak times, it fails to authenticate all requests. Probably due to LDAP limitations.

I had data center move recently and one TMG server failed. I had only four TMG server in the array and I noticed that it was performing much better, than before. Before it was Five TMG server in the arrays. Only few hundred auth errors happened during peak times.

I recovered 5th server and added it back to the array, and I see, old results. Up to the 1000 errors happened during first day.

It seems to me that TMG array of 4 members was working much better than TM away of 5 members..

Any ideas why?

December 23rd, 2013 11:24am

Hi

Thank you for your post here.

Do you use unicast or multicast mode? If is unicast mode, it may results in flood and performance may be reduced.

And you can carefully check the authentication failed errors, we can try to analyze the problem depend on these errors.

You also can go to run performance monitor to observe TMG.

Every TMG has updated to the latest version? And All TMG has the same version?

If the detailed information is not enough, it is hard to locate a performance issue.

Best Regards

Quan Gu

Free Windows Admin Tool Kit Click here and download it now
December 24th, 2013 10:10pm

Hello,

Thank you for response.

So far things are not that bad, but last week and this week are light. Many customers are out and do not care about the emails.

So far I've got only few errors during some peak times. Majority of errors are: 10013, 10048:

Log type: <id id="L_LogPane_WebProxyForward">Web Proxy
(Reverse)</id>
<id id="L_LogPane_Status">Status:
</id>10013 An attempt was made to access a socket in a way forbidden
by its access permissions.
<id id="L_LogPane_Rule">Rule: </id>Heplatform - Exchange 2013 OA
<id id="L_LogPane_Source">Source: </id>External (xxx.xxx.xxx.xxx:47848)
<id id="L_LogPane_Destination">Destination: </id>Local Host
(xxx.xxx.xxx.xxx:443)
<id id="L_LogPane_Request">Request: </id>POST
http://domain/ews/exchange.asmx
<id id="L_LogPane_FilterInfo">Filter information: </id>Req ID: 0c53bbc1; FBA
cookie: exists=yes, valid=yes, updated=yes, logged off=no, client type=public,
user activity=yes

-=-=-

It used to be thousands of those errors a day and many angry customers, but it is better now. I had case open with Microsoft and we did lots of tweaking at Windows Winsock level.

I wish to eliminate this error, but I can live with few hundred per day..

All TMG servers are power full servers, 4 core, enough memory, latest OS, TMG patches.

December 30th, 2013 9:37am

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

Other recent topics Other recent topics