Re: Firewall session disconnects after 2 minutes of inactivity

That doesn't make sense. The app should work even without the firewall
client. Did you put the new rule (the one based on IP rather than username)
on top of the other? "Unauthenticated" rules should always come first.

Moreover, you can keep an eye on the ISA real-time log to see why the app
won't connect without the firewall client. And again, is your ISA server
machine the default gateway for the workstations on your network?

Virgil


"Pedro Lima" <PedroLima@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BB14A8EE-CAA3-416B-AA63-C8DEACAD9338@xxxxxxxxxxxxxxxx
> Some news on the issue:
>
> I have created an IP rule for the client in order to avoid the use of
> firewall client. I have also "openned" the rule that uses port 23000 to
> use
> any port (but just to the destination host 161.148.40.200).
>
> The effects:
> The session openned in ISA server now shows just the IP of the client (not
> the username). This was exactely what I expected to see. But the app
> doesn't
> work without the firewall client at all. It says "Cannot connect to host
> 161.148.40.200:23000". When I have enabled the firewall client, it could
> connect without any problem. But the 2 minute (or less) session idle time
> is
> still there...
>
> Anyway, thanks for the idea...


.

Relevant Pages
Loading