Ruckus and WPAD

[Sheridan]

I've setup a guest WLAN for occasional use that I want to push out a wpad.dat file for the proxy. I've got the guest pass working nicely and seem to be stuck at the point where the clients don't get the wpad.dat file (which at the minute is a simple one line entry). The wpad file is on the ruckus controller itself.

 

I'm only using the DHCP option 252 (active on the scope) to push it out and not DNS, but the clients seem to ignore it, even with 'Automatically detect settings' ticked. if I manually specify the same wpad.dat pathname in the 'use automatic configuration script' then it works fine! (This is on Win8 IE11 test clients by the way)

 

So all seems to be working, just the clients are not automatically getting the wpad.dat pathname - our dhcp is still running on an old 2003 server but that shouldn't matter really?

Edited June 26, 2014 by Sheridan

[OverWorked]

I recently got wpad.dat auto configuration working with a bit of frustration.

 

I used DNS, not DHCP. Create a DNS entry WPAD, pointing to the WPAD.DAT server. (CNAME or A record will do).

 

In server 2008 and 2012, WDAD DNS lookups are refused as a security measure, so you'll need to enable them. See Removing WPAD from DNS block list(this bit was a lot of frustration).

 

(I spent ages trying to get proxy.pac to work, but got nowhere).

 

Let me know if you need more help.

[Sheridan]

I thought using dhcp would simplify this but maybe not! I'll have a crack at setting it up in DNS instead. DNS servers here are all 2008/12 so I'll have to unblock the wpad lookup as well.

[localzuk]

You should set up *both* DHCP and DNS wpad methods - some OS's only support one or the other... So, you are always going to have some issues if you've only got one of them and not both setup.