Rockem,
This problem/bug/issue has been discussed many times. If you need a fix, remove v6 of SME at one end, or downgrade it. This issue has been discussed since Dec or Jan, and it still exists.
I found a work around, but it requires 2 additional low end (PII or better & 128mb ram) PCs and 6 nic cards. Install IPCop on the two additional PCs and make use of green, orange, and red zones. IPCop will then be your connection to the internet connection (at both sites). I keep SME in server gateway mode and connect the external nic to the DMZ (orange lan) of IPCop Your SME external gateway is the orange IP address of the IPCop server. You can then port forward pptp from IPCop to your SME server to accept pptp connections from the internet. If you only need one way pptp, put a single IPCop at the site you connect pptp from. Adding IPCop as described will provide you with 2 gateways on the lan...simply use the IPCop gateway if your going to connect pptp to a remote SME 6 server. Or use server manager to define the static address in remote network and use the green IP address as the router...this will allow SME on either end to route traffic to your static IP through IPCop (by passing SME).
If you use SME for dhcp, your lan clients will use SME as the default gateway. Use IPCop for dhcp, they will use IPCop gateway. Or you can use group policy/MS dhcp to control proxy & router settings if you have a 2k or 2k3 AD server running.
Personally, I like IPCop as a router. It is very easy to use IPSEC vpn between sites and you can use cheap linksys vpn routers as an IPSEC vpn end point. I have several remote offices connected to a central IPCop server. These remote offices use either a linksys or IPCop server. It is very stable. IPCop is opensource...free!! I keep SME for services like proxy, pop, smtp, squidguard, sarge, ftp, ssh, etc....
Hope this helps you find a solution.
ryan