FOG Proxy Issues
We have been using FOG to deploy our images and all is great with that. We have just been told by our internet provider (BGFL) that our fog server is constantly sending data to the proxy server. The proxy server has had over 500,000 hits witin a couple of days. Aparently we are the second school in the list with such a high number from FOG so it seems others are affected.
After stripping out all of the proxy info on the server a couple of weeks ago we have been told that there are still around the same amount of hits going to the proxy from/because of the fog server. It seems after some testing that it is the client service that is causing this. It seems that the client is sending data to the proxy server which is then being redirected back into our network to the fog server.
What i want to know is, is there any proxy bypass information that i need to add to the client to stop it looking for the fog server through the internet and just going directly to the server.
Any help would be appreciated.
The Fog service just uses the settings in Internet Explorer I believe, so adding an exception for the address that the client uses to connect back to Fog in there should kill those requests.
I would have to ask also, is this an offsite proxy? If so, why not add your own proxy in between?
Thanks for your reply.
I will look at adding an exception into IE.
And no the proxy is in school managed by the lea.
The FOG client can run without a user logged in so I'm not sure that it would be using the IE settings. Take a look at the system-wide proxy settings and see what you have configured there.
netsh winhttp show proxy
Thanks will have a look at this and let you know of any outcome.
Originally Posted by morganw
We have done further testing on this. During our testing we put in a false proxy for IE and for winhttp. After doing this we found that the fog client service still communicates with the fog server. Does anyone know how this might work. Im getting confused now :-(
Are you using the hostname or the IP address to identify the server in the client configuration? If a hostname, can your local DNS resolve the name? You should be able to see in the Apache logs on the FOG sever where the connections are coming from, hopefully not all from your proxy.
I will check this today. Been busy and haven't had chance to investigate this more.
As a quick workaround we have currently disabled the service on the clients and after speaking to our ISP it seems that the issue is resolved but I want the serivce running and will look to fully resolve this.
I will let you know of any outcome.