Hello folks, thanks for helping me.
I have this configuration file:
http://myserver.mydomain.loca/wpad.dat
And works great for IE but for FM is not working.
I have tried create a other file called wpad.pac but didnt work either.
I have tried put the server IP and server port and didnt work
In the proxy type I have changed for 2 and put the address above.
but still not working,
Guys do you any suggestion for me ?
Best Regards for All.
Robson
How to use a Proxy config .dat file?
-
DraconPern
- Site Admin
- Posts:1218
- Joined:Thu Oct 30, 2003 11:47 pm
- Location:Texas
- Contact:
Re: How to use a Proxy config .dat file?
You should use the .pac file. See http://forums.frontmotion.com/viewtopic.php?f=10&t=1057 on how to set it up.
FrontMotion Lead Developer
Re: How to use a Proxy config .dat file?
Hey robson-dasilva,
as it is not always possible or usable to use .pac files you should implement the WPAD deployment as it is standardized. Then Firefox (including FrontMotion) is dealing without problems with it.
I have this setting here too. I started with .pac and changed to WPAD as the more mobile users came into the company. pac caused huge delays in surfing while they were not in LAN.
You should read into the background of WPAD as it can open security holes and should be implemented correctly - but:
your DNS server should have a CNAME "wpad.mydomain.local" to myserver.mydomain.local
WPAD searches the DNS for a machine that's called wpad.
Also your DHCP should provide a WPAD flag.
Then Firefox, when set (via GPO or locally) will use the WPAD if set to "automatically detect".
On details... it's highly depending on your infrastructure, so refer to google
I just wanted to drop the lines, as I did this some weeks ago and learned the basics of WPAD to understand what I'm doing. Maybe the DNS CNAME points you to the right direction
Cheers
as it is not always possible or usable to use .pac files you should implement the WPAD deployment as it is standardized. Then Firefox (including FrontMotion) is dealing without problems with it.
I have this setting here too. I started with .pac and changed to WPAD as the more mobile users came into the company. pac caused huge delays in surfing while they were not in LAN.
You should read into the background of WPAD as it can open security holes and should be implemented correctly - but:
your DNS server should have a CNAME "wpad.mydomain.local" to myserver.mydomain.local
WPAD searches the DNS for a machine that's called wpad.
Also your DHCP should provide a WPAD flag.
Then Firefox, when set (via GPO or locally) will use the WPAD if set to "automatically detect".
On details... it's highly depending on your infrastructure, so refer to google
I just wanted to drop the lines, as I did this some weeks ago and learned the basics of WPAD to understand what I'm doing. Maybe the DNS CNAME points you to the right direction
Cheers