Auto-Discovery of WPAD over VPN

  • Thread starter Thread starter Issproking
  • Start date Start date
I

Issproking

Guest
Hi All

Have a very strange and frustrating problem.

We have just changed our group policy away from telling client IE to use a "Automatic Configuration Script" to "Automatically Detect settings"

We have circa 2000 laptops in and desktops in our estate and for 95% of them everything works flawlessly. We do however have a handful of laptops that will not auto-discover the WPAD.dat file when they connect over VPN from home. These same users however detect the WPAD file when they are on the LAN no problem. To complicate matters further if we connect their laptops to a little router with a direct internet connection we have in the office and then make the VPN from there it also works fine.

When they are connected from home over VPN they can ping wpad and they get the correct answer, they can also browser to http://servername/wpad.dat and the wpad file opens with no issues but they cannot access the internet.

On the affected users machines we have been looking in the registry at the following key.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings

In here we have done the following.

1. Created the wpadoverride registry key on their machines and it must be stated that in some cases this has addressed the problem but there are some users who it doesnt have any affect on.

2. We have also deleted the DefaultConnectionSettings and SavedLegacySettings keys

3. Deleted the whole WPAD folder and let it re-create

In addition to the above we have also removed the users wireless network, wireless adapter and let windows re-connect and re-create as we believe the issue is related to something telling IE on that users machine not to use WPAD for that one network despite the registry keys above saying otherwise.

Has anyone came across this type of issue before?

Of course we can change the group policy to use the automatic configuration script and just to point out if we put http://servername/wpad.dat into that on the affected users machine it works perfectly. We are however trying to avoid that do it the way it is designed to.

Any advice gratefully received.

Continue reading...
 
Back
Top