Hello Rafael, I don't know which VPN client you are using or the VPN gateway software however I can think of a scenario that might cause this .
I am asserting that when you mean that it works on the "inside" you mean that it works from a PC within the corporate intranet when connecting to this one apache server, however fails through a VPN tunnel. To trouble shoot this I need a couple pieces of information. The IP address on the intranet of this apache web server and the routing information on the PC you are connecting with (when the VPN tunnel is established). If you are on a windows system you can get routing information by doing rhis command from a dos box: route print Some VPN clients are given extra routing information (especially on window vpn clients like Nortel's) when the VPN is established. Its possible that there is routing information that is stopping packets from reaching the server in question. Secondly, its possible the problem is on the apache server. Ff apache is running on a Linux based server, and you have the ability to log into it, I'd like to know the output (on the apache server that is having problems) of the following command: iptables --list -t nat -v I am assuming it is iptables based. Its possible that the server is somehow configured to block access from certain ranges (or specific ip's etc). -- Mike Petch CApp::Sysware Consulting Ltd. Suite 1002,1140-15th Ave SW. Calgary, Alberta, Canada. T2R 1K6. (403)804-5700. On Tue, 2003-09-16 at 09:49, J. Rafael S�nchez wrote: > 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.
signature.asc
Description: This is a digitally signed message part
