|
|
PIX 501 Problems - Help
I have a PIX 501 and tried to install it - I get a steady green blinking
LED
on port 0 LINK/ACT. I assume this is some kind of error message as I get
no
Internet connectivity. Any ideas what that state means its not in the
manual?
It's meant to replace a Debian firewall I have so I know all cables are
sound as is the cable modem (Com21).
I tried a really simple network with Com21 -> PIX 501 Port 0 -> PIX 501
Port 1 -> PC
I can ping the 501 from my PC and go to the startup.html page. I can
also see people trying to ping and connect from the Internet but nothing
ever seems to emanate out of port 0. i.e. if someone pings it from the
Internet the PIX sees the ping but the pinger times out
With a total cold reboot of the above configuration the the PIX 501 port
0 LINK/ACT LED is green until the PC initiates some network activity at
which time the steady slow blink starts.
Any ideas?
|
|
0
|
|
|
|
Reply
|
John
|
4/29/2004 10:18:37 AM |
|
Hi,
Ahum.. have you configured anything on the PIX ? :-)
Remco
John Fletcher wrote:
> I have a PIX 501 and tried to install it - I get a steady green blinking
> LED
> on port 0 LINK/ACT. I assume this is some kind of error message as I get
> no
> Internet connectivity. Any ideas what that state means its not in the
> manual?
>
>
>
> It's meant to replace a Debian firewall I have so I know all cables are
> sound as is the cable modem (Com21).
>
>
>
> I tried a really simple network with Com21 -> PIX 501 Port 0 -> PIX 501
> Port 1 -> PC
>
>
>
> I can ping the 501 from my PC and go to the startup.html page. I can
> also see people trying to ping and connect from the Internet but nothing
> ever seems to emanate out of port 0. i.e. if someone pings it from the
> Internet the PIX sees the ping but the pinger times out
>
>
>
> With a total cold reboot of the above configuration the the PIX 501 port
> 0 LINK/ACT LED is green until the PC initiates some network activity at
> which time the steady slow blink starts.
>
>
>
> Any ideas?
>
|
|
0
|
|
|
|
Reply
|
R
|
4/29/2004 10:59:41 AM
|
|
"R. Bressers" <nomail@thisaddress.com> wrote in message
news:4090e217$0$92969$6c56d894@diablo.nl.easynet.net...
> Hi,
>
> Ahum.. have you configured anything on the PIX ? :-)
Yeah got quite a complex configuration that a specialist network company
set up - unfortunately they are in the UK and I'm in NZ
All the best
John
|
|
0
|
|
|
|
Reply
|
John
|
4/29/2004 9:23:13 PM
|
|
connect to the console port and enter the command " show logging"
you should see something like this:
firewall# sh logging
Syslog logging: enabled
Facility: 23
Timestamp logging: enabled
Standby logging: disabled
Console logging: disabled
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 81388 messages logged
Trap logging: level debugging, 81388 messages logged
Logging to inside server
History logging: disabled
Device ID: disabled
check that buffer logging is enabled; it not configure it
conf t
logging buffered debugging
exit
wri mem
when a user tries to connect to the Internet, perform a "show log"
you should see messages like the following:
305011: Built dynamic TCP translation from inside:192.168.0.13/3143 to
outside:24.102.87.153/8593
302013: Built outbound TCP connection 8727 for
outside:216.239.37.122/80 (216.239.37.122/80) to
inside:192.168.0.13/3143 (24.102.87.153/8593)
show interface will let you know if packet are going thru outside
interface
check which version of software PIX is running using "show version"
command
|
|
0
|
|
|
|
Reply
|
merv
|
4/30/2004 11:16:27 AM
|
|
Just solved it.
The periodic flashing was a red herring.
The problem was that the PIX could not autonegotiate with the Com 21
cable modem correctly. Typing
interface ethernet0 10baset
did the trick as the Com21 can only communicate at that speed.
Cheers
John
|
|
0
|
|
|
|
Reply
|
John
|
4/30/2004 11:44:45 AM
|
|
|
4 Replies
132 Views
(page loaded in 0.087 seconds)
|
|
|
|
|
|
|
|
|