PIX Blocking My Intranet Shoutcast Server

[galaxiedude]

I just recently added a PIX 501 to my network. I have been able to get the Internet to work on all the computers. The problem I have been having is with pinging devices within the intranet. All devices can be pinged from the PIX in the PDM. If I try to ping the same devices from any of the workstations, it just times out. Sometimes it will ping once, and the last 3 attempts will time out. The only device that consistently responds to all 4 pings is the firewall itself (192.168.123.1) Is there some kind of access list that I need to set or something? I'm pretty sure it is not a hardware problem as it worked fine with my old SMC 7004BR router/firewall.

Please tell me what could possible be wrong in my configuration.
Here is my current configuration-

interface ethernet0 100full
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxxxxxxxxxxxxx encrypted
passwd xxxxxxxxxxxxxxx encrypted
hostname thunderhome
domain-name thunderhome.com
clock timezone CST -6
clock summer-time CDT recurring
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
names
name 192.168.123.67 PDS266
pager lines 24
icmp deny any outside
mtu outside 1500
mtu inside 1500
ip address outside dhcp setroute retry 4
ip address inside 192.168.123.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location PDS266 255.255.255.255 inside
pdm history enable
arp timeout 14400
global (outside) 1 interface
global (inside) 2 192.168.123.2-192.168.123.254
nat (inside) 1 192.168.123.0 255.255.255.0 0 0
timeout xlate 3:00:00
timeout conn 0:00:00 half-closed 0:00:00 udp 0:00:00 rpc 0:00:00 h225 0:00:00
timeout h323 0:00:00 mgcp 0:00:00 sip 0:00:00 sip_media 0:00:00
timeout uauth 0:00:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http PDS266 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.123.2-192.168.123.31 inside
dhcpd dns 4.2.2.2 4.2.2.3
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80

Thank you for your time.

 

[LloydSev]

Is the PIX the default gateway on your workstations? Or the devices you are pinging?

Computer/Network Technician
CCNA

 

[themut]

Are all workstation withing the same subnet? Are you using the PIX as the default gateway? The PIX is not able to route packets back on the same iterface they arrived. Does the pinged devices have an internal firewall (say zonealarm)?

 

[galaxiedude]

That makes sense now. Yes, I do have the PIX as the default gateway. How would you recommend that I hook things up to eliminate this problem. If I remove the PIX as the default gateway, how can I reconfigure my network? (or the settings on my workstations). Thank you for your input.

 

[LloydSev]

The default gateway option should not be a problem..... do you have an internal dns server running?

Computer/Network Technician
CCNA

 

[galaxiedude]

No, I do not have an internal DNS server running. Would that solve my problems? It wouldn't be a problem to configure one. I have both a Windows 2000 Server configured already. I have not enabled DNS, however.