Welcome to ISAserver.org

WHY ISA2004 BLOCKING MY INTERNAL CLIENT

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> Firewall Client >> WHY ISA2004 BLOCKING MY INTERNAL CLIENT

Page: [1]

Message

<< Older Topic Newer Topic >>

WHY ISA2004 BLOCKING MY INTERNAL CLIENT - 22.Sep.2005 10:35:00 AM

Guest

Hi all i have problem with isa 2004 right now we have isa 2000 with
FWC and win2003 AD all client need to auth. before get internet access.

we have 2 diff internal Segments one is 172.16 .1.0/24 and other is
128.127.1.0
128.127 is my unix subnet and which ever client need to access unix
have 2 diff ip address one 172.16.*.* and other is 128.127.1.* my unix
application client use telnet to connect to unix server till ISA2000
with isa2000 FWC it was working fine.
but when i configure isa2000 FWC to new ISA 2004 Server when FWC enable
user can not connect to unix i can ping frm client to unix server but
application (Telnet) is not working.

Any idea why this???

i have configure one more network in ISA 2004 with 128.127.1.0/24 and
make access rule to enable evveryone full access frm internal network
to unix network but no luck...

ISA 2004 with SP1 on win2003 SP1 and cleint is winxp sp2.

plz help to resolv this issue..

Post #: 1

Featured Links*

RE: WHY ISA2004 BLOCKING MY INTERNAL CLIENT - 25.Sep.2005 8:22:00 AM

rmccollum

Posts: 11
Joined: 10.Aug.2005
From: Tularosa, NM
Status: offline

Do you need to define a presistent route to the unix network at the ISA2004 server so the server's OS will know which NIC to go out on?
At cmd prompt type print for comman use info or
see technet.com and search for "add static route".
??

(in reply to Guest)