I have recently deployed a Small Business Server 2003 Standard SP2 and a Server 2003 configured as a Terminal Services server (2 separate boxes). I have followed the advice given by Microsoft in this link:- http://technet.microsoft.com/en-us/library/cc747395.aspx
Everything is working as it should, except the facility to connect to server or client desktops via the Remote Web Workspace (from outside of the local area network). When I try, the error shown in the attached screen dump image, appears after about 10 seconds.
This is very puzzling, as I have about 15 SBS2003 machines at various locations, and I've never known this particular problem.
This installation is different, being the only one with a Terminal Services Server involved as well.
Internally (on the same LAN), using Remote Desktop directly, I can connect to any client and any server (assuming that I log on as an authorised user). Also, I can connect to either Server internally using the link on the default 'companyweb' Intranet site.
I have checked user permissions and group membership, but I don't think this is the problem area, because even as the administrator, connection via the RWW (from outside the local network) fails.
I think there must be an issue with routeing, because the other thing I noticed here, if I use the public name or IP address internally, I get a 404 error. Whereas on at least two other installations using the public name works even if you're actually internal (on the same LAN as the server).
This is a major issue for me with this customer, because remote access to the Terminal Services server is the main reason for moving from a simple peer to peer network.
Any help or guidance as usual will be greatly appreciated.