Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

SBS2003 Connect to desktops via RWW fails

Avatar of Nick Brown
Nick BrownFlag for United Kingdom of Great Britain and Northern Ireland asked on
SBSMicrosoft Server OS
15 Comments1 Solution928 ViewsLast Modified:
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.

Avatar of suppsaws
suppsawsFlag of Belgium image

Our community of experts have been thoroughly vetted for their expertise and industry experience.

This problem has been solved!
Unlock 1 Answer and 15 Comments.
See Answers