Jump to content

Recommended Posts

Posted

We have recently moved to our new ISP. On our MS Forefront Threat Management Gateway 2010 on Windows Server 2008 R2 Standard, we had a web chaining rule that was pointing to a proxy we used with our old ISP but don't any more. But with our new ISP, that proxy isn't needed so we removed the rule from MS TMG 2010.

 

But even after restarting, the sever keeps looking for it and we get this error:

 

Alert: Routing (chaining) Failure

Description: The Firewall service detected that the upstream proxy server proxy.addressgoeshere.com is not available. If the upstream proxy server proxy.addressgoeshere.com becomes available, you may proceed as usual. If it does not become available, check the status of the upstream proxy server. Verify that the Firewall service is up and running on the upstream server. Verify that Forefront TMG Clients are enabled on the network where the downstream server resides. Check for the absence of events indicating that Forefront TMG Client listeners failed to start on the upstream servers.

 

Why is it still looking for the old proxy? Where is it set?

Posted
Go into forefront TMG click network on the left hand pane, then in the right hand pane you'll get 7 option tabs one of those being web chaining. you'll need to edit your rule you had set up.
Posted
Thanks, but in Web Chaining I have only Default rule. The other one, the proxy one, we had already deleted. We even restarted after a few times. The default rule one has nothing in it regarding that proxy, or any other :(

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...