TMG automatic discovery configures a normal client but does not detect a TMG server

A few days ago, colleagues and I said TMG automatic discovery function configuration is normal, but the client can not detect the TMG server, do not know what causes, after viewing and processing summed up:

You can use the TMG client's own tool Fwctool to reset the reset by using the following methods:

1, Fwctool Testautodetect

2, netsh winsock reset

3, the client set a static IP address to prevent the detection of related configuration information

4, ADOBE CS3 Bonjour service services affect DNS acquisition

Workaround:

Run "C:\Program Files\bonjour\mdnsresponder.exe"-remove

Open C:\Program Files\bonjour, rename MdnsNSP.dll to Mdnsnsp.old

Restart the computer

Delete Program Files\bonjour folder

The cleanup is complete.

Some users will encounter TMG client connection is normal, but a visit to the external network is disconnected, after viewing this reason generally for the use of local account login led to this phenomenon, because TMG is built in the domain, the user needs for the domain account.

This column more highlights: http://www.bianceng.cnhttp://www.bianceng.cn/Network/Firewall/