From: Cape Town
Hi, Got your mail I'm taking a guess here that it may be due to your dns settings on your nics registering the host name name in DNS.I would uncheck these options and possibly create a second host record or cname for your isa box.DHCP is probably getting confused due to that. Good Luck, ISA_baby
I've started the testing of a simular configuration (internal and perimeter). The DNS autodetect works for me but the content of the wpad.dat file is wrong. It points to the web proxy listener on the internal interface instead of pointing to the web proxy listener on the perimeter interface.
Got the answer. You have to create a 2nd A record for your ISA server. Then, make sure Netmask Ordering is enabled in your AD DNS. Based on this, the clients on the other segment will get the correct address when they resolve the wpad record.
yep, that's a good *workaround*. However, it doesn't solve the fundamental problem itself.
Because ISA supports multinetworking and the UI does give a strong indication that you can create autoconfig information on a per network basis, I consider this a bug. Therefore, I made a support call to Microsoft. Here is the answer from Microsoft PSS:
I have been discussing this issue with the ISA product team and the WPAD Proxy server listed is based on the machine's domain association, regardless of the network where this data is sent. This is by design with no plans to change this for the current version but will be considered in future releases.
Thanks, Tom Sampson Microsoft EMEA GTSC - DSI - Specialist Support Engineer Microsoft Product Support Services