wpad...

[enbiggen]

Hi,

 

I tried enabling wpad to experiment with it for Smoothwall, but it was causing issues. I've disabled it (removed the entry in DNS and added it back to the blocklist) but it looks like it's cached (or something) as it's still stopping Teams (the app) from working. If I switch off "Automatically detect settings" then Teams starts working again. However, I've yet to find a way of doing this automatically at the group policy level, and normal users (understandably) can't access this setting to switch it off.

 

Has anyone any ideas?

 

Thanks,

Enbiggen

[tom_newton]

It's not usually cached. Make sure it' isn't still being served, and do an ipconfig /flushdns, see where you get from there.

[enbiggen]

It's not usually cached. Make sure it' isn't still being served, and do an ipconfig /flushdns, see where you get from there.

Hi,

I've re-tried using "ipconfig /flushdns" and rechecked "nslookup" and it can't find "wpad" or "wpad.mydomain", which I thought meant that it wouldn't be able to be redirected to the proxy.pad/wpad.dat?

When I have "Automatically detect settings" on (which is the default) the Teams app won't log in, and gives a "caa7000a" error.

When I set "Automatically detect settings" to off, the Teams app logs in without issue.

When I had wpad enabled I was getting failures because it said there was a problem with the certificate - this stopped happening when I removed it, so I'm assuming that that means that it's not getting wpad.dat from smoothwall otherwise it would still be occurring?

Thanks.

Edited December 9, 2021 by enbiggen

[ibpalle]

Lots of possible reasons and actions to look at here.

 

1: Ensure the Smoothwall certificate Authority is installed on your devices.

2: Use the KB here and add IPs to Guardian - web filter - exceptions and add domains to the pac file in web proxy - web proxy - automatic configuration. I assume you have added internal subnets and AD Domains here already.

3: Check your DHCP if option 252 has been added - that is a way of getting proxy settings using auto discovery as well as DNS.

[enbiggen]

Lots of possible reasons and actions to look at here.1: Ensure the Smoothwall certificate Authority is installed on your devices.

It is, it worked when we didn't have wpad enabled, and just had the manual proxy. When we disabled wpad, it went back to working.

2: Use the KB here and add IPs to Guardian - web filter - exceptions and add domains to the pac file in web proxy - web proxy - automatic configuration. I assume you have added internal subnets and AD Domains here already.

That's what I followed when I set it up for wpad. It was working before then (for a long time) without the proxy exceptions in our manual setup, but I thought it was probably inefficient and fixing this might also solve another problem I was seeing.

3: Check your DHCP if option 252 has been added - that is a way of getting proxy settings using auto discovery as well as DNS.

We only set 003 (router), 006 (dns servers) and 015 (dns domain name). That was something I hadn't checked (and I'd seen something online about 252) so I was briefly hopeful that if it were there, I could disable it to undo and get things working again :-(

 

Thanks.

[enbiggen]

I used this code from https://gist.github.com/ReubenBond/1387620 (without wrapping it in the function) and attached it to a login script and that disables the "automatically detect settings" in proxy settings - which seems to be working and letting Teams (and Internet Explorer where it's still in use) work again.

 

Thanks for the help - having things to try helped reduce the stress.