When I'm putting TMG proxy settings like http://proxy:8080/wpad.dat
in client IE no internet is available...
TMG log show that clients try to connect to http://
I have check NIC binding order and Internal is on top.. RRAS in bottom.
Any ideas on how to get the clients not to connect to TMG RRAS IP's ??
10.45.205.4 should be 10.45.205.4 ..
So I found this:
After doing a little digging, I've found that this is actually a known issue with TMG. If changing the binding order of the Network Interfaces doesn't help...either of the following can help with this issue.
1. Change to a static range of addresses for the VPN client.
2. Run the script found at the following link. The blog references ISA 2006, but the script does work on TMG as well. This script will force TMG to use it's fully qualified domain name in the autoconfig script (instead of IP).
Some things to note before trying this script.
-It will restart the Firewall service, so you may want to try it afterhours.
-It may take a few minutes for the change to apply.
-Verify TMG's FQDN and make sure that internal clients will resolve this name to 192.168.100.1 before running the script.
Richard Barker (MSFT)
Will it be "safe" to run this script on TMG?