Welcome to ISAserver.org

Firewall Client wont stay connected.

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 Firewall] >> Firewall Client >> Firewall Client wont stay connected.

Page: [1]

Message

<< Older Topic Newer Topic >>

Firewall Client wont stay connected. - 20.Nov.2003 2:02:00 AM

Cl33nSw33p

Posts: 14
Joined: 5.Nov.2003
From: Virginia Beach
Status: offline

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.

Post #: 1

Featured Links*

RE: Firewall Client wont stay connected. - 21.Nov.2003 8:08:00 PM

miles_kailburn

Posts: 69
Joined: 5.Nov.2002
From: New York
Status: offline

same issue but im still working with MS on mine.. try kb815051

(in reply to Cl33nSw33p)

Post #: 2

RE: Firewall Client wont stay connected. - 28.Nov.2003 12:40:00 PM

ptwilliams

Posts: 277
Joined: 3.Nov.2003
From: South Wales, UK
Status: offline

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.

Paul.

(in reply to Cl33nSw33p)

Post #: 3

RE: Firewall Client wont stay connected. - 28.Nov.2003 1:02:00 PM

dos-netres

Posts: 13
Joined: 27.Jun.2003
From: Belgium
Status: offline

Hi,

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!

Regards

Koen

(in reply to Cl33nSw33p)

Post #: 4

RE: Firewall Client wont stay connected. - 28.Nov.2003 5:06:00 PM

lemonwater925

Posts: 417
Joined: 22.Mar.2001
From: North of the 49th
Status: offline

Try using IP instead of DNS. Much more reliable.

[ November 28, 2003, 05:07 PM: Message edited by: lemonwater925 ]

(in reply to Cl33nSw33p)

Post #: 5

RE: Firewall Client wont stay connected. - 12.Dec.2003 2:01:00 AM

ismaster

Posts: 48
Joined: 9.Nov.2003
From: pakistan
Status: offline

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 .

(in reply to Cl33nSw33p)

Post #: 6

RE: Firewall Client wont stay connected. - 24.Dec.2003 3:56:00 PM

johnplayer

Posts: 2
Joined: 10.Oct.2003
Status: offline

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/b ulletin/MS03-012.asp

(in reply to Cl33nSw33p)

Post #: 7

RE: Firewall Client wont stay connected. - 5.Jan.2004 3:13:00 PM

dos-netres

Posts: 13
Joined: 27.Jun.2003
From: Belgium
Status: offline

johnplayer,

I did installed the suggested patch, but still the Fiewall Client won't stay connected.

I also use the IP adres in sterad of the DNS name.

Any other suggestions?

Many Thanks.

(in reply to Cl33nSw33p)

Post #: 8

RE: Firewall Client wont stay connected. - 9.Jan.2004 8:12:00 AM

skami

Posts: 54
Joined: 24.May2001
From: Australia
Status: offline

check for virus in your network.. which may b causing firewall service to go down

(in reply to Cl33nSw33p)

Post #: 9

RE: Firewall Client wont stay connected. - 9.Jan.2004 8:57:00 PM

Guest

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.

Please anyone help .. [Smile]

Customer is going nuts.. [Smile]

(in reply to Cl33nSw33p)

Post #: 10

RE: Firewall Client wont stay connected. - 12.Jan.2004 2:02:00 PM

dos-netres

Posts: 13
Joined: 27.Jun.2003
From: Belgium
Status: offline

HI,

Also no virus on the network here.

The only thing is that 2 ISA servers are running on the same segment. It is the old, and the new. But the new cannot be used since I have that problem with the proxy client.

The old one stays running very wel...

Any other suggestions?

TNX

Regards

Koen

(in reply to Cl33nSw33p)

Post #: 11

RE: Firewall Client wont stay connected. - 12.Jan.2004 4:44:00 PM

ppeetoom

Posts: 262
Joined: 22.Dec.2003
From: The Netherlands
Status: offline

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........

Good luck

(in reply to Cl33nSw33p)

Post #: 12

RE: Firewall Client wont stay connected. - 19.Jan.2004 6:04:00 PM

macrus

Posts: 58
Joined: 8.Feb.2002
From: Poland
Status: offline

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

regards

(in reply to Cl33nSw33p)

Post #: 13

RE: Firewall Client wont stay connected. - 22.Jan.2004 7:13:00 AM

antivirustaneja

Posts: 2
Joined: 22.Jan.2004
From: India
Status: offline

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.?????

(in reply to Cl33nSw33p)

Post #: 14

RE: Firewall Client wont stay connected. - 22.Jan.2004 12:47:00 PM

skami

Posts: 54
Joined: 24.May2001
From: Australia
Status: offline

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

(in reply to Cl33nSw33p)

Post #: 15

RE: Firewall Client wont stay connected. - 23.Jan.2004 10:38:00 AM

antivirustaneja

Posts: 2
Joined: 22.Jan.2004
From: India
Status: offline

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

(in reply to Cl33nSw33p)

Post #: 16

RE: Firewall Client wont stay connected. - 29.Jan.2004 1:58:00 AM

alfalfa6945

Posts: 12
Joined: 20.Dec.2003
Status: offline

quote:
Originally posted by lemonwater925:
Try using IP instead of DNS. Much more reliable.

What?? DNS is your friend! [Smile]

And, coincidently, the way to fix the problem in question.

If you've set everything you can think of for autodiscovery, try this, it's the last step to complete the process:

In DNS, add an alias name of WPAD and an FQN of your isa server (such as isaserver.domain.com)
Works every time.

(in reply to Cl33nSw33p)

Post #: 17