We have 2 BorderManager 3.7 SP3 servers and about a year ago, I read
Shaun's article in Cool Solutions for Proxy Failover (without
clustering) using a custom PROXY.PAC. This was great and we
implemented with our 2 servers. What we are noticing though is that
there are certain websites where the proxy.pac is not working. But it
is a combination of certain websites with users who are restricted
with access rules in BorderManager. For example, User A and User B
both use the failover proxy.pac. User A has no browsing restrictions
but user B has limited restrictions. If both go to
http://www.wunderground.com/US/NV/Las_Vegas.html and click on the
radar picture, User A gets there fine, but User B gets a 404 error. If
I then modify User B's IE settings to go direct (not use PROXY.PAC)
and then he can also get to this site. Note: All users have rights to
get to this site). Any suggestions? Here is the contents of our

function FindProxyForURL(url, host)
// set bm2 and bm3 to the 2 proxies
var bm2=""
var bm3=""
//find the 4th octet - if even, is bm2/bm3 else bm3/bm2
var myip=myIpAddress()
var ipbits=myip.split(".")
var myseg=parseInt(ipbits[3])
if(myseg==Math.floor(myseg/2)*2) {
var proxone=bm2
var proxtwo=bm3
else {
var proxone=bm3
var proxtwo=bm2

//if name has no dots, or is our domain, or starts 192., or if my
//current address does not start 192. don't use proxy
if(isPlainHostName(host) ||
dnsDomainIs(host,".lvcva.int") ||
myip.substring(0,4)!=="192." ||
host.substring(0,4)=="192." )

// alert("direct")
return "DIRECT";
else {
// alert("proxy")
return "PROXY "+proxone+":8080; PROXY "+proxtwo+":8080" ;