I could not find any log files affected by establishing a PPTP connection - even after running /sbin/e-smith/db configuration setprop masq Logging all.
I was able to generate comprehensive logs of the handshaking using "iptraf" (use Putty to connect, start "iptraf", select cOnfigure, press "L" to turn Logging ON if it is OFF, accept the default log file name - probably /var/log/iptraf/ip_traffic-1.log - then monitor all interfaces while you attempt to establish a connection)
I once heard that PPTP connections are supposed to have trouble if the MTU of any link between the two systems is too small - you might want to check your MTU. My system connects using PPPoE; I have the following MTUs:
eth0: 1500
eth1: 1500
ppp0: 1492
Is this a "virgin" system, or do you have other contribs loaded? I've used SMEs pretty extensively over the last 3 years or so - v6.01, v6.5, v7beta2 through 7.0rc3 - and haven't had any trouble making VPN connections out from my networks... (except for the OneCare issue I've already mentioned!)
If you want it I'll send you my "iptraf" log - but it's a bit messy to post here! I do notice that after I initiate the connection there is traffic flowing both ways on port 1723 - from my system to the remote PPTP server, and from the remote server back to my workstation.
I do *not* have any "port forwarding" rules for port 1723.
I *do* have my SME server setup as a VPN server (I like VPNs - I always set them up to support remote VPN connections).
Another possibility: is the *local network* number at the remote end the same as at the workstation end, or the same as the WAN IP on the SME server? That is - if you *could* connect, would the VPN IP address be in a subnet that already exists in the SME server's routing table? This could cause problems...
To be more concrete:
SME LAN: 192.168.200.x
SME WAN: 71.246.xxx.yyy
Remote Public IP: 72.244.ccc.ddd
Remote LAN: 192.168.123.x
If my "Remote LAN" was on the 71.246.xxx. network, or on the 192.168.200. network, PPTP would not work.
Good luck; keep us posted!