From: Virginia Beach
I am using ISA in integrated mode. Each one of my clients has FWC installed. Every few minutes the FWC shows ISA Server Could Not Be Detected. When I hit the update button it will connect and then a few minutes later right back to the same message. The name resolves to the ip address easily. Pinging the ISA Server by FQDN comes back everytime correctly. I have installed the firewall client several times now with the same outcome. NE1 have any Ideas on what to try to get the client to connect, AND STAY CONNECTED. This is relly getting irratating.
From: South Wales, UK
I think that this is to do with the "Automatically detect ISA server" option in the firewall properties. If you haven't setup Friewall client automatic updating then this will happen. Deselect this option and choose "Update now" and your away.
I have the same problem, but the "automaticly detect ISA server" is not checked!
Any other suggestions?
I have 2 addmit that we have currently 2 ISA servers in the network. The first ISA, no problem. The 2nd ISA has this problem. Now the 2nd is a newly installed and faster machine that will replace the 1st one!
apply antivirus on server also force other computers to install antivirus and latest update of it.it could be Welchia worm.use your server ip to connect instead server name.update your window and upply security patches of windows.also install hotfix of Kb823980.hope it will work 110%.because i had this problem a weak ago and now its gone in this way .
I have installed patches, and have Norton Antivirus Corporate installed on the entire network. I also use ONLY IP addresses in my destination set. My ISA server is displaying the same symptoms of the people above. This problem is only happening on the set of users I have limited access to one subnet of IP Addresses. They can hit refresh and it will reconnect for a few minutes, then revert to disconnected. I've scanned all machines for viruses and spyware.
From: The Netherlands
Either disable the 'Autmatically detect ISA Server' on the clients OR use the auto detect feature completely. Meaning, add WPAD entry in your DNS and use Server Name in ISA Client. (see documentation on this site)
It should solve your problem. Atleast, it solved mine........
Are you sure there's no virus inside, flooding ISA ? Try to test it this way: - take one or two computers you're ABSOLUTELY sure are virus-free - open RRAS->IP routing->General - right click your _LAN_ interface, go to properties->Input filters - set up a filter to DROP everything except these testing computer(s) - check if testing computer(s) have problem with FWC
Above may not work if ISA uses internal DNSes or AD. In such a case, you have two options : - to add all DNSes and DCs to the filter to allow ISA to communicate with them (hovever, you have to be sure these servers are also virus-free) or - analyze the logs and try to isolate computers causing most of the traffic and create the opposite filter - to allow everything except suspicious machines
Hello, i have same problem with FWC. I have ISA 2000 server and 98 clients on LAN . i installed FWC on win 98 PC's but every time it shows the error "Isa server could not detected" despite of the fact that internet is running fine through proxy and there is no virus on them . plz tell me the solution ?? And wat abt the Mspclnt directory?
Also tell me how to block ports like 7,9,13,19,135,137 etc. with ISA or in win 2000. and is it necessary to open port 80 on ISA external NIC.?????
First thing did you checked the ISA Los files wat firewall logs says when the client cannot connect and 2ndly if you r using dns then chk your dns resolves the address or not otherwise ISA dont give any problems. check your conactivity to isa server ping -t
could not get the solution ! One another problem is that i am unable to view the .org websites on my clients despite of having right site and content filtering rules. it shows error HTTP proxy 502 ISA server 12202 error wat is the solution of this problem http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q317798