On Tue, November 22, 2005 3:12 pm, Thane Sherrington (S) wrote: > At 03:45 PM 22/11/2005, Jamie Furtner wrote: > >> What do you mean by the 2K3 machine can't see the router? Can you ping >> it? Any connectivity to any devices on the 192.168.1.0/24 subnet? Is >> there a firewall blocking traffic - maybe the router itself? > > The 2K3 machine can't ping the router (or any other device on the > 192.168.1.x subnet. It's in the DMZ, so it should be able to ping the > router, shouldn't it? > > Other computers are using the router with no problems.
The router may be blocking its pings from the DMZ -- if it can't ping the router when it's not in the DMZ, then you have other issues. Can other nodes on the internal network ping the server? Maybe you have a connectivity issue here instead(cables, NIC, port?) > > >> Probably the best, easiest and most secure thing to do is to set up >> port forwarding on the router for port 80 (and maybe 443 if you need >> HTTPS). >> That reduces the amount of exposure of the 2K3 machine and should >> reduce the possibility of getting hacked. > > Yeah, that makes more sense than putting it in the DMZ. I put it there > to try to get around the connectivity problem I was having with the > router. > > T > > > -- Jamie Furtner [EMAIL PROTECTED] "The difference between intelligence and stupidity is that intelligence has its limits." --unknown
