Update:
I know that the Firewall does not know that the 10.25.192.0 /19 exists. I
tried to put in a route statement on the pix but it would not accept it.
This was the command: "route inside 10.25.192.0 255.255.224.0 10.25.223.2 1"
When I put in a route to the secondary Address of VLAN 1, it acce
ssage-
From: Darren Crawford [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 02, 2001 1211
To: Nabil Fares; Rob Cabeca; groupstudy
Subject: RE: Help!, because Cisco says they can't. Firewall & Vlan
problem.
You should be able to Ping the inside interface of your PIX. You can not
p
Sent: Friday, March 02, 2001 0043
To: Rob Cabeca; groupstudy
Subject: Re: Help!, because Cisco says they can't. Firewall & Vlan
problem.
Back to basics:
Check your subnet mask on the interfaces connecting
the MSFC and the PIX (on the 155.102/16 net) If you
can;t ping the inside address of the
.
Thanks
Rob
-Original Message-
From: Nabil Fares [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 02, 2001 0853
To: Rob Cabeca; groupstudy
Subject: RE: Help!, because Cisco says they can't. Firewall & Vlan
problem.
Rob,
By default PIX does not allow pings! You can have con
You guys have always been on target for me. I am hoping you give some
insight to this. (the following addresses have been slightly altered for
obvious reasons but they are true to the real ones).
Overview.
I am upgrading a network which has a 155.102.0.0 255.255.0.0 network. It is
flat. I have i
5 matches
Mail list logo
