Hi Mr. Tom, It gives me this: C:\>nslookup wpad *** Can't find server name for address 10.92.60.10: Non-existent domain *** Default servers are not available Server: UnKnown Address: 10.92.60.10 Name: 8000-srv.dac.edu Address: 10.92.60.20 Aliases: wpad.dac.edu 10.92.60.10 is our internal DNS, 10.92.60.20 is the ISA internal NIC, the client is on 10.80.60.0 subnet, we have no PTR in the reverse lookup zone. Thanx r. -----Original Message----- From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx] Sent: Tuesday, December 21, 2004 6:44 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: FW Client (ISA2004) http://www.ISAserver.org Hi Ruba, When you do an nslookup for wpad what do you see? If should look something like this (with different names, of course): F:\>nslookup wpad Server: marsoutpost.tacteam.net Address: 192.168.1.34 Name: celestix-h5l4cs.tacteam.net Address: 192.168.1.60 Aliases: wpad.tacteam.net F:\> Thanks! Tom www.isaserver.org/shinder <http://www.isaserver.org/shinder> Tom and Deb Shinder's Configuring ISA Server 2004 http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7> MVP -- ISA Firewalls ________________________________ From: Ruba Al Omari, Eng. [mailto:romari@xxxxxxxxxxxxxxxxx] Sent: Tuesday, December 21, 2004 8:05 AM To: ISA Mailing List Subject: [isalist] RE: FW Client (ISA2004) http://www.ISAserver.org Hi I hate to interrupt the very interesting discussion about ISA being part of the domain, but I added the wpad entry in the DNS server and put the FQDN of the isa for that alias as mentioned in the document, I enabled for the Internal network The Auto discovery option (default port 80 because of DNS) and enabled the FW Client support for the internal network, the FW client can't auto detect yet.(if I set the server name it works fine).If I browse to the http://wpad:80/wpad.dat <http://wpad/wpad.dat> at the isa it says page can't be displayed, and the same at the client. What could be the problem now? Also I have a group of users connecting through this ISA2004 and I have another group who connect through ISA2000, the auto detection is still not working now but if it works will it affect the other group of users? The other group have routes to both ISAs but access rules on both ISAs restrict the traffic. thnx r. ________________________________ From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx] Sent: Monday, December 20, 2004 3:00 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: FW Client (ISA2004) http://www.ISAserver.org Hi Ruba, Autodetection depends on wpad entries in DHCP and/or DNS. Check out the book or www.isaserver.org for deep details. HTH, Tom www.isaserver.org/shinder <http://www.isaserver.org/shinder> Tom and Deb Shinder's Configuring ISA Server 2004 http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7> MVP -- ISA Firewalls ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: romari@xxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx