Thanks Policymap and Boss_Hog,
A). DLink gave me the same advice - but putting the SME server in the DMZ seems to defeat the whole purpose of putting the server behind a firewall. I suppose it's possible to set the SME server up to have the same protection as offered by the DSL-504T, but as I'm not SURE of the default security setup in server only mode I've rather shied away from this solution. On the other hand I suppose it's the Windoze boxes that need the protection

B). Yes Boss_hog, that's the 'web admin' page. The problem is not one of port forwarding but of protocol handling. It seems that some of the messages passing between VPN server and client use the GRE protocol as opposed to TCP or UDP. You'll see that the port forwarding administration only allows for either or both of TCP/UDP to be specified in the port forwarding rule. Hence, when a message arrives on port 1723 with the GRE protocol this seems to get stopped - despite the fact that the inbuilt PPTP rule specifies both port 1723 AND the GRE protocol (the only place I've seem the protocol mentioned in the DSL-504T)
I've come across another problem with this setup too. I allowed port forwarding of port 22 (UDP,TCP) so that I could use Putty to access the server when I got back to my office. Full of confidence I fired up Putty, entered the IP address, got the logon prompt, entered the username, entered the password and got logged on. However, I get no prompt - and then Putty dies with the message "Network error: software caused connection abort". I manage several SME servers all of which I can reach using this method - but not this one! (I use different modem/routers at the other locations - DSL-504's to be exact). Has anyone seem this problem before? - and if so, what needs to be done to fix it? The logged on process seems to be quite happy in the SME box, BTW, and so I guess it's another routing problem.
Regards,
Dave