I am having a problem very similar to this abandoned question:-
We have implemented a proxy server but certain local web services are going via the proxy server when they should be classed as local and not even be hitting the proxy server in the first place.
The problem is most apparent on (though not limited to) a Windows Server 2008 Terminal Server (running IE11). I also have a server 2003 server that is doing the same kind of thing. (running IE8).
DC's are Server 2012 R2
We have implemented these registry keys - but the proxyoverride doesn't seem to be working for certain sites even though they are listed in the registry key.
This registry key was rolled out using a group policy - User Configuration, Preferences, Windows Settings, Registry. I can see that the registry settings are applied:-
Yes, I keep seeing these entries in the logs:-
CONNECT Jan 13 17:03:12 : Connect (file descriptor 6): 172.16.1.18 [172.16.X.XX]
CONNECT Jan 13 17:03:12 : Request (file descriptor 6): POST http://sXXXXXXXX3.domain.co.uk:8000/publish/apps
NOTICE Jan 13 17:03:12 : Proxying refused on filtered domain "sXXXXXXXX3.domain.co.uk"
CONNECT Jan 13 17:03:12 : Connect (file descriptor 6): 172.16.1.18 [172.16.1.18]
CONNECT Jan 13 17:03:12 : Request (file descriptor 6): POST http://dXXXXXXXXX/XXXXservices/Xdataaccess.asmx
NOTICE Jan 13 17:03:12 : Proxying refused on filtered domain "dXXXXXXXXX"
CONNECT Jan 13 18:29:44 : Connect (file descriptor 6): 10.254.254.11 [10.254.254.11]
CONNECT Jan 13 18:29:44 : Request (file descriptor 6): POST http://sXXXXXXX1/XXXXXXXXXXWebService/XXXXXXXXXX.asmx
NOTICE Jan 13 18:29:44 : Proxying refused on filtered domain "sXXXXXXX1"
Any ideas why this might be? The problem *might* be limited to NTLM names and services that use non-standard ports although that might not actually be the case. Just strikes me from the above.