Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, July 15, 2010 3:14 AM
We have been using DHCP option 252 to provide details of the WPAD.DAT file for proxy auto config for the past 4 years and it has been working well. We recently upgraded (replaced) out DC from an old W2k3 server to a 2008 R2 server. The DHCP options were identical as we exported them from the one server and imported them to the new server, but since the change over we have not been able to go proxy auto config to work. The clients (combination of XP and Win7) don’t even seem to be trying to access the file. It appears that the DC is not providing the details to the clients.
Has anyone got proxy auto config working with a 2008 R2 DHCP server? I have been working on this for a couple of weeks and we know the web server side is working fine. I have tried removing option 252 and recreating it, but that does not help.
Any ideas?
Steve
All replies (4)
Friday, July 16, 2010 6:34 AM ✅Answered
Thanks for the help I found the answer whilst looking into what you detailed.
http://technet.microsoft.com/en-us/library/cc794902(WS.10).aspx
Microsoft has put a block in to stop wpad entries showing up in DNS. The link details why and how. I have turned off the block and now we are all working fine now.
Thanks again.
Stephen Bloomer
Thursday, July 15, 2010 8:57 AM
Hi Steve J B ,
Thanks for posting here
Please check if this issue could be resolve on XP client with the article below:
953761 Some DHCP Options are not recognized on a Windows XP SP3-based client computer when the DHCP server offer includes option 43
http://support.microsoft.com/default.aspx?scid=kb;EN-US;953761
If this problem continues , then please capture packet while the client requests an IP address from the DHCP server by Wireshark and filter the result with filter string “ bootp.options.type == 252 ”
Meanwhile, please following workaround to configure DNS to set the Proxy Autodiscovery information.
To implement web proxy auto-discovery in your environment, refer to the following steps:
1. Enable "Automatically detect settings" in IE.
a) In IE window, click "Tool"-->"Internet Options".
b) On "Connections" tab, click "LAN settings".
c) In "Local Area Network (LAN) Settings" window, ensure "Automatically detect settings" is checked.
2. Add "WPAD" record in DNS server:
a) Start the DNS snap-in.
b) In the console tree, click your server name, and then click Forward Lookup Zones.
c) Right-click the forward lookup zone that you want to support Web Proxy client Autoconfiguration, and then click New Alias.
d) Type wpad in the Alias name box.
e) Type in the Fully Qualified Domain Name(FQDN) of the proxy server computer's internal interface. Use the Browse button to minimize the chance of making an error.
NOTE : The proxy Server computer must already have a Host (A) address record before you create an Alias (CNAME) record.
f) Click OK.
And please post the result after following above settings.
The following are the details of how the Web Proxy Auto-Discovery (WPAD) works with DNS server for you reference:
1. With the auto detect setting enabled, when IE starts and tries to access a website, it will try to detect the proxy server.
2. The computer will send DNS name query for the name "WPAD". If a record called "wpad" is added to the DNS server, DNS server will respond with the IP address of that name and then client will try to access http://wpad/wpad.dat. If client locates the server through DNS, only the default port 80 will be used and we cannot specify any other ports.
3. Client will find the proxy server from the wpad.dat file after getting the file by accessing the URL: http://wpad/wpad.dat. At last, the client will send the request to the proxy server to access the website.
Thanks.
Tiger Li
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Friday, July 16, 2010 4:59 AM
Thanks for that information Tiger Li, option 1 looked like our problem, but did not seem to help. I ran the wireshark. This is what I got when I did an ipconfig /release and /renew
Note that the 3.119 address is the desktop being used for testing, the 3.1 address it the gateway to the main server vlan. Interesting that my DHCP options include option 43 and options 66 and 67, both of which are listed.
No. Time Source Destination Protocol Info
8 7.845406 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x50831157
Frame 8 (342 bytes on wire, 342 bytes captured)
Ethernet II, Src: Foxconn_a3:63:38 (00:15:58:a3:63:38), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
No. Time Source Destination Protocol Info
9 7.851372 172.16.3.1 172.16.3.119 DHCP DHCP Offer - Transaction ID 0x50831157
Frame 9 (364 bytes on wire, 364 bytes captured)
Ethernet II, Src: 3com_37:8e:81 (00:1c:c5:37:8e:81), Dst: Foxconn_a3:63:38 (00:15:58:a3:63:38)
Internet Protocol, Src: 172.16.3.1 (172.16.3.1), Dst: 172.16.3.119 (172.16.3.119)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol
No. Time Source Destination Protocol Info
10 7.851955 0.0.0.0 255.255.255.255 DHCP DHCP Request - Transaction ID 0x50831157
Frame 10 (367 bytes on wire, 367 bytes captured)
Ethernet II, Src: Foxconn_a3:63:38 (00:15:58:a3:63:38), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
No. Time Source Destination Protocol Info
11 7.863412 172.16.3.1 172.16.3.119 DHCP DHCP ACK - Transaction ID 0x50831157
Frame 11 (369 bytes on wire, 369 bytes captured)
Ethernet II, Src: 3com_37:8e:81 (00:1c:c5:37:8e:81), Dst: Foxconn_a3:63:38 (00:15:58:a3:63:38)
Internet Protocol, Src: 172.16.3.1 (172.16.3.1), Dst: 172.16.3.119 (172.16.3.119)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol
No. Time Source Destination Protocol Info
12 7.872661 Foxconn_a3:63:38 Broadcast ARP Gratuitous ARP for 172.16.3.119 (Request)
Frame 12 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: Foxconn_a3:63:38 (00:15:58:a3:63:38), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request/gratuitous ARP)
No. Time Source Destination Protocol Info
13 7.900898 Foxconn_a3:63:38 Broadcast ARP Gratuitous ARP for 172.16.3.119 (Request)
Frame 13 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: Foxconn_a3:63:38 (00:15:58:a3:63:38), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request/gratuitous ARP)
I have never used wireshark before, so I hope that this is the right information. Using bootp.options.type == 252 caused an error.
Thanks
Stephen Bloomer
Friday, May 2, 2014 8:46 AM | 1 vote
Run command prompt as an administrator.
Type
netsh dhcp server add optiondef 252 wpad string
Restart DHCP service, go back in to your server or scope options, option 252 is available again.