keithab - All Comments

re: Creating a Rule to Bypass the Web Proxy Filter in ISA Server or Forefront TMG

lalajee — Thu, 16 May 2013 10:20:36 GMT

Your images are not very cleanr can you please re-upload your images.

re: Forefront TMG 2010 Service Pack, Rollup, and Version Number Reference

Ranjeet Padalkar — Wed, 15 May 2013 13:25:39 GMT

Nice Article...very useful...

re: Setting Up and Troubleshooting LDAPS Authentication in Forefront TMG 2010

yargray — Wed, 01 May 2013 08:27:25 GMT

Unfortunately I am having similar problems as described above. We get the " LDAP server not responding" alert quite regularly, but in our case all functionality appears to be fine and the LDP test described in this blog is fine too.

Any suggestions on finding the root cause for this would be much appreciated! Alternatively, if this is some kind of "false" alert, is it safe to override it in SCOM?

Many thanks,

re: Setting Up and Troubleshooting LDAPS Authentication in Forefront TMG 2010

Karsten Hedemann — Fri, 15 Mar 2013 13:59:53 GMT

As jr_suisse I'm experiencing exactly the same issue. I have found nothing wrong in the network and TMG is configured correctly. It's the same on two different domains.

I have been looking at timeout settings etc., but haven't had luck to figure out what was wrong.

And as the warnings comes in the Application Event Log, the user (if logged in) experience a timeout until the Event Log 'Description: The connection to the LDAP server x.domain.local was restored' is logged.

If a user is about to logon, they can also experience long login times and the same Event Log is logged, and Again when 'Description: The connection to the LDAP server x.domain.local was restored' is logged the session may even be signed in and the user can browse the SharePoint site, or the timeout was so long that the user need to login Again.

re: Forefront TMG 2010 Service Pack, Rollup, and Version Number Reference

eni — Wed, 06 Feb 2013 14:31:59 GMT

very helpfull page !!!!

thx!!!!

re: Web Publishing Quits Working or Not Working as Expected on ISA/TMG Server

Roman Krilov — Wed, 09 Jan 2013 19:44:05 GMT

When trying to publish HTTP websites (on port 80), the published websites aren't working. Published HTTPS websites (on port 443) are working normally.

The following error message is written to the eventlog:

The Web Proxy filter failed to bind its socket to A.B.C.D port 80. This may have been caused by another service that is already using the same port or by a network adapter that is not functional. To resolve this issue, restart the Microsoft Firewall service. The error code specified in the data area of the event properties indicates the cause of the failure.

A.B.C.D is the TMG's external IP address.

When trying to disable rules for this IP the following message is written to the eventlog:

"A problem preventing the Web Proxy filter from binding its sockets was resolved"

When checking the listeners with netstat -ano, you see PID 4 is listening on port 80 on all the IPs. PID 4 is a system process.

Solution

The problem is caused because the http service is listening to port 80 on all IPs.

Opening "Command Prompt" and running the following command:

netsh http add iplisten ipaddress=127.0.0.1

and restarting the TMG services (or rebooting the server) solves the problem.

re: Forefront TMG 2010 Service Pack, Rollup, and Version Number Reference

Nitin Pandey — Thu, 13 Dec 2012 01:14:33 GMT

Thanks Keith.. this makes the task lot easier to assist our customers.

re: Setting up an OWA Redirect in Forefront TMG 2010 - the Easy Way

intelitecpacific — Mon, 26 Nov 2012 01:45:53 GMT

Well done!

re: Setting up an OWA Redirect in Forefront TMG 2010 - the Easy Way

Mark C — Thu, 11 Oct 2012 02:46:11 GMT

A little more information, I have TMG deployed with a single NIC if that makes any difference.

re: Setting up an OWA Redirect in Forefront TMG 2010 - the Easy Way

Mark C — Thu, 11 Oct 2012 02:41:37 GMT

I keep on getting this problem when I attempt this. OWA works properly using https://<domain>/owa however when I attempt the normal http://<domain> I get this error both internally and externally:

Error Code: 502 Proxy Error. The Uniform Resource Locator (URL) does not use a recognized protocol. Either the protocol is not supported or the request was not typed correctly. Confirm that a valid protocol is in use (for example, HTTP for a Web request). (12006)