Accessing TS network via the web nightmare, day 3

Ok its day 3 and I'm starting to get a bald spot from tearing my hair out.

Scenario
3 x Windows 2003 Servers, 1 as Domain Controller and 2 as Terminal Servers.

Up until recently we were able to happily connect from remote locations using Remote Desktop Connection and a dydns host name.

Then the router died.

Our friendly neighbourhood ISP tech came and swapped the router/gateway for a new one but alas did nothing more than copy accross the ISP account settings then promptly dissappeared with the old router.

Since then I have double, triple and quadrouple checked the dyndns settings. I get the correct IP to be pinged when I ping using the hostname so we know its resolving ok.

Alas our ISP uses a router that isnt listed on portforward.com so we haveto guestimate a little on the settings but directing HTTP through Port 80 to the static IP of either of the terminal servers isnt rocket science.

Have tried directing the dyndns hostname to the domain controller and both terminal servers at intervals throughout the last 3 days and never get a connection accepted, just a message saying cant connect to the remote computer.

We did install all the outstanding updates just before the router got swapped which seemed to reset some of the permissions set up in the GPO but cant find anything there that would prevent the connection from deing established, but I'm the first to admit that I could have missed something.

Actually I know I missed something otherwise this freakin thing would be working.

Its probably something real small and obvious too:cry

Somebody save my sanity and restore my sleep patterns by telling me what I'm missing. Pleeeeeaaaaaaaaaaassssssssseeeeeeee