If you're comfortable with capturing packets and analyzing them (running with the "dissecting an http request" idea), you might want to capture traffic to/from the machine (or even promiscuous mode and filter by IP) and see what the difference between other servers and "that-one" is. If you can do the capture directly from the machine in question, it can often be more quickly revealing than sifting through the whole network's data. I like using Ethereal for capture and analysis, but you can pick your favourite data capture method.
Some quick questions that you've probably already thought of... Does the machine run a host-based firewall (iptables, et al.)? Is the network configuration correct for the LAN (subnet mask, default gateway, etc.)? Just a couple off the top of my head. HTH, Curtis -----Original Message----- From: J. Rafael S�nchez [mailto:[EMAIL PROTECTED] Sent: September 16, 2003 9:49 AM To: [EMAIL PROTECTED] Subject: (clug-talk) Not able to see apache server [INTRANET] from outside firewall... Here's a good one I hope... I have a vpn connection from the outside of our firewall into our corporate network. I can see all my servers, ping, ftp, ssh, telnet, even http:// into others apache servers, but not "this-one" I'm having challenges with. I just don't get it... I have even rebooted it... and nothing. I can see it from the inside, no problem... >From the outside I've tried by ip address, by name, ping... of course if I can't ping it, likely nothing else will respond... At first I thought it had to do with my nat router at home, but even when I plug right onto the internet, no joy. I was thinking about finding information about the actual http request from the outside to see what's happening behind the scenes - Jeffrey, maybe you can shed some light on this area - or may be it's not even necessary to do the disecting of the actual http request, is it?. I've tried everything I know so far. Any ideas? Thanks for your time. Rafael. -- J. Rafael S�nchez <[EMAIL PROTECTED]> Itres Research Limited
