I am reposting since I did not get a reply back after my last posting. Maybe I will have more luck this time.
My computers still won't detect ISA. I can ping ISA. My little icon still has a red X I also changed the 0 to a 1 in the registry hack according to MS instructions and have reloaded DHCP, etc... I followed the steps from an ISA book. 252 for DHCP and Cname entry in DNS. I tried fwctool testautodetect and it detected the ISA server and downloaded the wspad file successfully and all was successful. With fwctool pingserver, it tell me that the firewall client service is responsive, but firewall client is disabled which is not the case. I have toggle from disable to enable and it still shows a red x and just will not detect the server. Same thing happens in my laptop which I also have connected. All setting in IE are correct.
I really need help. Any input would be greatly appreciated.
Clients are running XP Pro SP2 and all users are local admins. We also use Vlans with Cisco switches, but I don't think that is causing the problem since I can ping the ISA server with no problem. Server is Windows 2003 Standard ed with all the latest patches and ISA SP2.
From: fort frances.on.ca
This may sound like a dumb question, but are you sure you enabled support for FWC in ISA? Configuration => Networks => Internal => Properties => Firewall Client => "Enable Firewall client support for this network"
The School of Hard Knocks is a mean teacher. She gives the exam before the lesson.
I am asssuming you are talking about the tab on the internal network (firewall client)
I had servername.ahm.avborne; have also tried servername.avborne.com; servername.avborne, etc... I just decided to finally put the IP address in the two fields so there is no confusion, but still can't find it.
I set up a pc with W2003 and ISA2004 (on its own domain) and connected to a laptop and the client did find the ISA server (not automaically) when I put the IP manually, but then the ISA is in the same box as the DNS and DC, so maybe that helps somehow. Soooo, there's got to be something preventing the clients from finding the ISA server. I can ping it with IP and DNS since I made a ping rule to ping it, so I know the clients know that it is there, but the FW just can't seen to find it.
I had a similar problem just the other day. I had one Windows XP SP2 client on a network of about 400 identical (or so I thought) clients where the Firewall Client simply would not detect the ISA Server. All the diagnostics worked flawlessly. I worked on it for hours and was about to just give up and reimage it.
As a last ditch effort, I went to http://update.microsoft.com and applied all the updates listed as "Software, Optional" (there were 11 of them).
Somewhere during the process of installing these updates, the Firewall Icon disappeared (since "Hide when connected.." option was checked) as it auto-detected the ISA Server. I have no idea which update actually solved the problem, but you may want to give it a try.