DMZ and Ping issue when changing ip address for a server

cargo

New Member
I have got a media server 2003 installed in DMZ zone (Cisco PIX 525) , with an ip address 192.168.101.204/24, it was able to ping other servers (sql server , help server, etc ) which are in DMZ zone as well. Basically all servers are in DMZ area

Recently this media server is not able to ping these servers (sql server , help server, etc) , I do not why, but if I changed the ip address (last octet only) for this media server to 192.168.101.222 , it would be able to ping other servers (sql server , help server, etc).

There is no firewall on the media server and there is no firewall on the other servers as well.

All servers have got win2003 OS.

The error message for ping is : timed out

This is no entry with our cisco PIX for both IP addresses 192.168.101.204 and 192.168.101.222
 
run a tracert instead of ping, see if your media server is even getting to your gateway or not, see where your ping is dying. When your server can't connect to anything, look at your ipconfig /all and compare to the other servers... I'm curious, because if your server has the same gateway, DNS, and is on the same subnet as the others.. you shouldn't really have a problem...
 
so you have servers set up with private class c ips (192.168.x.x) and in DMZ? Are these on the internet? Are you running win2k3 server OS?

Is there a specific reason there are DMZ? If you are DMZ and on the internet you are pretty much asking to get tons of viruses, spyware, malware, etc.
 
Back
Top