set proxy via dhcp ?

"Francis Walsh" <f_walsh009@hotmail.com> wrote in message
news:iLXSb.37752$Wa.15530@news-server.bigpond.net.au...

> If by that you mean correct DNS suffix - then yes.

No, the machine itself have to be assigned a domainname (maybe from DHCP).
So if the machine is ws.somedomain.tld it will query the primary nameserver
for wpad.somedomain.tld.

> 'wpad' resolves correctly to 192.168.0.200 - and
> http://192.168.0.200/wpad.dat returns the script.

This is correct...

> > I have tried to setup WPAD on numerous occassions - but the god damn
> > thing is so broken in the Microsoft Internet Explorers from different
> > releases of Windows and service packs that i finally gave up in
> > frustration. Save yourself much headache - do it manually or use a
> > proxy-script.

I agree with Andrey on this one...

> Cannot do it that way, as at one location I don't have control over
> things and it is WPAD or nothing there.

Is it not possible to use a local wpad.dat either? This way you don't need
access to at webserver at that site. As a workaround you could check out the
script the wpad.domain.dat delivers at that site, and than implement
something similar in your local wpad.dat, wrapped in a "if(IsInNet......)"

Carsten Keller

Carsten Keller wrote:

> Is it not possible to use a local wpad.dat either? This way you don't need
> access to at webserver at that site. As a workaround you could check out the
> script the wpad.domain.dat delivers at that site, and than implement
> something similar in your local wpad.dat, wrapped in a "if(IsInNet......)"

I already have a WPAD in both locations, the issue is that IE doesn't
ask for it in one location but does in the other.

e.g. location1:

wpad resolves to wpad.location1.test -> 192.168.0.200 ->
http://192.168.0.200/wpad.dat.

location2:

wpad resolves to wpad.location2.test -> 130.111.222.223 ->
http://130.111.222.223/wpad.dat.

At location2, I fire up IE, it finds the IP and wpad and works fine.

Same machine and IE at location1 - it doesn't even query the DNS server
for wpad's address.

Francis Walsh <f_walsh009@hotmail.com> wrote:
> On my home Linux based network (DNS, DHCPD, etc) IE doesn't even do DNS
> lookups on wpad.ANYTHING. I turn on query logging on BIND on the linux
> box and sure enough no wpad queries at all.

> The Wpad is waiting there to be used, but never gets asked for.
> Do you have any idea why this might be happening ?

Yes! It happens to me with my laptop, too. The reason as far as I can
tell is that my laptop knows it's in its corporate domain. The DHCP
domain setting on my home network is added as a supplementary name,
not a primary one. The result is that my laptop insists on searching
for wpad.CORPORATE.com instead of wpad.HOME.net.

Worse, it's cached the IP *address* of the last successful
wpad.CORPORATE.com (even after an IPCONFIG /FLUSHDNS), and so it "knows"
it doesn't need to do a DNS lookup. Arrgghh!

The solution in my case was to add the IP address (and name) of my
corporate wpad server as an alias to my local wpad server.

Another thing you may want to consider is making your corporate and/or
home proxy.pac file a CGI script that returns an appropriate proxy.pac
file dependent on the client's source IP address. Remember to look for web
proxy forwarding clues, too, though, and use the true client source IP!

Regards,
Chris

"Francis Walsh" <f_walsh009@hotmail.com> wrote in message
news:4TOTb.41070$Wa.18254@news-server.bigpond.net.au...
> I already have a WPAD in both locations, the issue is that IE doesn't
> ask for it in one location but does in the other.
>
> e.g. location1:
>
> wpad resolves to wpad.location1.test -> 192.168.0.200 ->
> http://192.168.0.200/wpad.dat.
>
> location2:
>
> wpad resolves to wpad.location2.test -> 130.111.222.223 ->
> http://130.111.222.223/wpad.dat.
>
> At location2, I fire up IE, it finds the IP and wpad and works fine.
>
> Same machine and IE at location1 - it doesn't even query the DNS server
> for wpad's address.

Yes, but do the laptop _know_ it's at location1. In other words, is the
machine named something.location1.test when you connect it there?
I had a similar problem, some machines were IP-configured manually, and thus
had no hostname in the form ws.mydomain.tld. In that scenario there's no way
for the machine to know it have to connect to wpad.mydomain.tld. The result
was the same, no connections or queries at all.

Keller

Carsten Keller wrote:
> Yes, but do the laptop _know_ it's at location1. In other words, is the
> machine named something.location1.test when you connect it there?
> I had a similar problem, some machines were IP-configured manually, and thus
> had no hostname in the form ws.mydomain.tld. In that scenario there's no way
> for the machine to know it have to connect to wpad.mydomain.tld. The result
> was the same, no connections or queries at all.

Hostname, domain, DNS, WINS, Gateway are all set OK at both ends. Both
locations WPAD resolves to wpad.locationX.test.

In Non-working it resolves to wpad.local.XXXX.com, in working it
resolves to wpad.AA.BBB.au (because it doesn't find wpad.XXX.AA.BB.au).

So in both cases they are absolutely sure of where they are.

***** Non-Working Location:

Connection-specific DNS Suffix . : local.XXXX.com
Description . . . . . . . . . . . : NETGEAR WG511 54 Mbps Wireless PC
Physical Address. . . . . . . . . : 00-AA-BB-CC-DD-EE
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.91
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.100
DNS Servers . . . . . . . . . . . : 192.168.0.100
192.168.0.1
Primary WINS Server . . . . . . . : 192.168.0.100
Lease Obtained. . . . . . . . . . : Thursday, 5 February 2004 5:28:21 AM
Lease Expires . . . . . . . . . . : Thursday, 5 February 2004 5:28:21 PM

***** Working location:

Connection-specific DNS Suffix . : XXX.AA.BBB.au
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Physical Address. . . . . . . . . : 00-11-22-33-44-55
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 130.XXX.152.110
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 130.XXX.152.30
DHCP Server . . . . . . . . . . . : 130.XXX.2.56
DNS Servers . . . . . . . . . . . : 130.XXX.128.43
130.XXX.2.15
Primary WINS Server . . . . . . . : 130.XXX.2.112
Secondary WINS Server . . . . . . : 130.XXX.5.110
Lease Obtained. . . . . . . . . . : Thursday, 5 February 2004 4:56:01 AM
Lease Expires . . . . . . . . . . : Friday, 6 February 2004 4:56:01 AM