Well the issue with IPSEC is that 2003 doesn't support it for clients with dynamic public IP's, and no dial-on-demand. So when the nextG internet drops out and reconnects with a different IP it will need to be reconfigured.
PPTP has some security issues so is not an option - I don't think it would make much difference though anyway.
PIP's not really an option, don't think it can be configured on the windows end - besides this is only supposed to be a temporary solution, don't want to go to the effort of buying new equipment and setting that sort of thing up
I just tethered my iphone to my PC and found that the phone also gets a public IP address in the 10.0.0.0/8 range, then creates a 172.16.0.0/16 network, and the PC gets an IP in this range. I'd say that this NAT is why I can't connect to the VPN using the windows client when tethered to the phone but it works using the phone's own VPN client. Moreover it appears that my phone seems to be on the exact same network as the nextG dongles so I don't think there's anything funny going on regarding telstra's network.
not sure if you said it but can you ping the IP off the server's VPN connection? not the 3g.
which IP? The VPN clients get an address in our corp office's private network, (192.168.0.0/24) which I can ping from the firewall to the iphone but not to the windows box. (no other services can be reached on the windows box for that matter)
From the server it can ping the client address it gets at corp office and everything else on the corp network. (The local network at the remote site is a different subnet to corp office).