Proxy Settings

Kvad · Post by **Kvad** » Mon Jun 25, 2007 12:01 am

Hi all,

Ever since 2.0.0.3 FM FF CE has not been using the settings I specify for proxy settings using the firefox.adm (Iâ€™ve been setting the automatic proxy configuration url to point to a pac file (I am using ISA 2006 FYI)). I donâ€™t wish to set proxy settings per machine, rather per user so using the mozilla.adm wonâ€™t help.

This doesnâ€™t work in 2.0.0.4 either. Iâ€™ve updated the adm files and tried all this on a test OU with just Firefox and the GPO settings enabled.

Any help would be appreciated

Post by **DraconPern** » Sun Jul 08, 2007 7:23 am

Hum.. checking into it. There was some code clean up that must have changed the behavior.

Post by **DraconPern** » Fri Jul 13, 2007 3:27 am

Confirmed the bug(s). Accidently compiled in the old version of the firefox.adm code. Since there is a security annoucement for firefox. 2.0.0.5 should be out soon so the fix will be included in that.

DennisT · Post by **DennisT** » Mon Jul 30, 2007 3:58 pm

I'm trying to get the proxy settings (manual) under v2.0.0.5 to work. I've downloaded & installed the FrontMotion Firefox Community Edition for v 2.0.0.5. I then added the firefox.adm template and set all the manual proxy settings (I'm using 127.0.0.1 to block internet access). The GPO looks good but when I open Firefox with my test user account it's still using the original (direct connection) settings.

Could there be a problem using 127.0.0.1 or is there a bug?

Post by **DraconPern** » Tue Jul 31, 2007 7:27 pm

let me check on that.

savman · Post by **savman** » Sun Aug 12, 2007 8:59 pm

I'm also having this problem as well, FM Firefox doesn't seem to read the gpo. the last working version i had was 2.0.0.1, and then i went to 2.0.0.4 and it didn't work, and it still doesn't work in 2.0.0.5.

Post by **DraconPern** » Mon Aug 20, 2007 1:17 am

Do you have the updated version of firefox.adm? I just tested 2.0.0.5 and it does work.

While I was testing, I noticed something weird on AD. The proxy type wasn't set correctly on clients. To do so, change the proxy type to something, press ok, then change it back again. This will advance the setting number in AD so the clients will get the correct setting.

DennisT · Post by **DennisT** » Mon Aug 20, 2007 10:05 am

I'm running 2.0.0.5 and it isn't working. I tried changing to direct, run gpupdate, change back to manual, gpupdate, and it is still at direct.

Post by **DraconPern** » Mon Aug 20, 2007 10:30 am

I am guessing you have checked the registry entries also on the client? HKLM\Software\Policies\Mozilla\Firefox and about:config and they are not being set?

Anyway we can setup some kind of chat to get this resolved? May be MSN messenger and doing an application sharing?

DennisT · Post by **DennisT** » Mon Aug 20, 2007 11:38 am

I tried bumping to 2.0.0.6 but that didn't make a difference. When I run a GP results I show that the proxy sttings for Firefox are showing as I want them.

There isn't anything under HKLM\Software\Policies for Mozilla or Firefox. I'm defining the policy under User Config. and not Computer Config. so that may be ok.(?) about:config doesn't show any changes so it appears it's not making it to Firefox.

Sorry, no IM. We could do one of the desktop sharing services if you're set up with one of them or we could do a phone call (or even email).

Post by **DraconPern** » Mon Aug 20, 2007 2:12 pm

Is there settings under HKCU\Software\Policies\Mozilla? It seems like the settings are not making it from the controllers to the client. On my test install, doing a /force doesn't work either... I wonder if a MS update broke that functionality.

lol, nm, I am stupid, forgot to set the policy to apply to the user.

Post by **DraconPern** » Mon Aug 20, 2007 3:49 pm

For everyone: in about:config, is app.update.enabled locked to false?

savman · Post by **savman** » Mon Aug 20, 2007 6:37 pm

I just used the lastest build of 2.0.0.5 (got is yesterday before 2.0.0.6 was released) and that reads the gpo fine. My old 2.0.0.5 didn't have ce in the filename, but the working one did, so i'm assuming they were diferent builds. I'll test 2.0.0.6 today some time.

savman · Post by **savman** » Mon Aug 20, 2007 6:56 pm

DraconPern wrote:For everyone: in about:config, is app.update.enabled locked to false?

I just tested 2.0.0.6, and the gpo doesn't work again. 2.0.0.6 app.update.enabled is set to true and unlocked. And my working version of 2.0.0.5 is locked to false.

Post by **DraconPern** » Mon Aug 20, 2007 9:10 pm

Since app.update.enabled is unlocked, it seems firefox is not even attempting to run autoconfig/mission control.

After doing some troubleshooting over the phone, here's what we know
1) It's not a GPO/AD problem, the problem is entirely client side.
2) When it doesn't work, not even mission control works.
3) It is not a NTFS/registry permission problem

Some questions that will help to pin point this issue
1) It seems like various people are hitting this problem with different versions. Does installing an old known working version still work on the affected client?
2) Does mission control on a stock Mozilla firefox work? Test this by uninstalling the MSI and install the non-msi firefox. Then add the following to c:\program files\mozilla firefox\grepref\all.js

Code: Select all

pref("general.config.filename", "mozilla.cfg"); 
pref("general.config.obscure_value", 0);

and create a new file in c:\program files\mozilla firefox\ called mozilla.cfg with the following

Code: Select all

lockPref ("network.proxy.type", 4);

Run firefox, and go to about:config. Sort by status. Is network.proxy.type listed as locked?