Forefront TMG setups
Got a Forefront TMG running as a filter until our new broadband supplier comes in October (or possibly sooner).
I've tried to take out pretty much *everything* so it's running purely as cache and URL filtering. However, it appears to struggle every now and then (daily, unfortunately) with client authentication - we get errors in the TMG console saying that clients are slow to authenticate.
Anyone had this and managed to overcome it? Server isn't exactly a powerhorse, it's just a G4 HP ML110, 2008R2, Xeon 3040, 6gb ram and SATA disks (separate for boot and cache). Gigabit network connection, it's on the domain, authentication is "integrated" as we don't want to have to have people enter usernames and passwords again, but naturally when it is slow to auth, it does ask for this information.
CPU is barely being touched, ditto for network and disk.
Ive found it can be a pita like this... but in my case, was doing worse - not prompting and just saying "NO". Was one fix, a regfrag forcing Kerberos off so that it had to use NTLM. I will track it down from my GPOs and post it...
Ah great, cheers that'll be good.
Any joy with that fragment, @TheScarfedOne ?
Flip - completely forgot! Sorry....!
Here it is...
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Internet Settings\
EnableNegotiate (DWORD) - set it to 0
Cheers, will give that a go :)