Jump to content

grant_girdwood

Members
  • Posts

    101
  • Joined

  • Last visited

Reputation

145 Excellent

About grant_girdwood

Personal Information

  1. Indeed it is, yet surprising how many folk don’t do this
  2. When I last looked at this a couple of years ago Psiphon uses SSH to connect but will obfuscate this over ports you wouldn't expect, typically it was over DNS - blocking port 53 on the firewall and only allowing it out from your trusted servers typically done the trick - appreciate this may not be the case now but could be worth a punt. Good luck!
  3. If they have downloaded the PAC file on-network, it should cache the file locally, but this can depend on the settings on the local machine. You'll be able to craft your PAC file with the desired behaviour if your proxy is not reachable from their network location.
  4. You could set up a squid proxy and on that proxy box have the hosts file to point to the restricted youtube. Create 2 x pac files, one that points youtube traffic to the "restricted proxy" and the other to your existing proxy or however you access YouTube just now, then deploy the pac by group policy.... Of course you could flip the above about
  5. Hi Clare, Is it fine on other browsers? Give the team a call and we'll be able help you investigate further. Cheers, Grant p.s. down at BETT this week on stand F330 if you're around and want a chat.
  6. Wireshark could be your friend, or you should be able to setup a rule in Websense to allow the User-Agent string that Office products use.
  7. No worries - feel free to thank the posts
  8. Ah yes, caching of old proxy files can be a pain - especially in Windows. Have a look over at http://www.findproxyforurl.com - really useful resource for WPAD/PAC file information. Have a good weekend.
  9. They should do, are they within the 10.130.113.x range and is that how you're accessing them (e.g. http://10.130.113.50)?
  10. Also just looking at your original file I can see where you went wrong, WPAD/PAC files work in a top down manner and as soon as it matches a rule it won't look any further, so as you had specified the network first it meant that any rquest from the internal network would always hit the proxy regardless of what was being requested.
  11. Not a problem - here you go; function FindProxyForURL(url, host) { // Bypass proxy for local servers. if(isPlainHostName(host) || dnsDomainIs(host, ".internal.local") || isInNet(dnsResolve(host), "10.130.113.0", "255.255.255.0")) { return "DIRECT"; } if (isInNet(myIpAddress(), "10.130.113.0", "255.255.255.0")) return "PROXY sslfilter.proxy.swgfl.org.uk:8080"; else return "DIRECT"; } http://i.imgur.com/s888z0F.png At line 5 if you change internal.local to match the internal domain name e.g. bloxx.local whatever the set up, just means if someone attempts to get access to something via DNS and it's internal it won't hit the proxy. I've also set it up so that if there is a local DNS request (e.g. localhost) it won't hit the proxy
  12. P.s. let me know what you want from a PAC file and I'll throw one together for you. e.g. if you're in network X use proxy, or not, if you're making a request to a local domain (e.g. something.internal) not to use the proxy etc.
  13. It will just assume you have an IP that isn't listed in your PAC rules, so if it doesn't match else where it will hit your default/capture all rule at the end of your PAC file which bty the sounds of it is is direct.
  14. MathsNet: Java Technical Help
  15. Would be worthwhile running a Wireshark and inspecting it to see if anything is being dropped or what URL it is failing on... p.s. have you tried contacting mathsnet for support?
×
×
  • Create New...