From: jason_tomasi@hotmail.com   
      
   Even if you change the port number; you will still need to have GRE   
   running over the border router.   
      
   Without it, PPTP won't work :-)   
      
      
   Tomás Ó hÉilidhe wrote:   
   >     I'm working on a network at the moment where there's a firewall in   
   > place that blocks outgoing TCP segments unless their destination port is   
   > 80 or 443 (the ports assigned to HTTP and HTTPS).   
   >   
   >     I want to access a VPN, and, so, obviously I'll have to access it   
   > over port 80 or 443 somehow.   
   >   
   >     The VPN I'm trying to access is a private network where all the   
   > machines have private addresses (e.g. 10.*), but the router that they're   
   > behind performs NAT in order to enable the machines to access the   
   > internet via TCP and UDP.   
   >   
   >    The router's NAT has an option whereby it can accept a TCP segment on   
   > the WAN on TCP port 80, and forward it to TCP port 1723 on the LAN,   
   > meaning I don't need a special VPN daemon that can listen on ports other   
   > than 1723. Hurray for that.   
   >   
   >    I'm running Windows XP on the VPN server, and also on the client that   
   > wants to connect. The problem, however, is that the built-in Windows XP   
   > VPN _client_ application won't let met specify a different port.   
   >   
   >    The list of possible solutions, I think, are:   
   >   
   > 1) Find the .exe/.dll for the Windows VPN client, go thru it with a   
   > HexEditor and replace 1723 with 443. So does anyone know what file this   
   > is. . ?   
   >   
   > 2) Use a different VPN client application (possibly in conjunction with   
   > a different VPN daemon application). Can anyone suggest a good one?   
   >   
   > Or if there's any other ideas, please throw them out there!   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)