Users cannot connect to remote desktops by using the Windows Small Business Server 2003 Remote Web Workplace

FYI – I found this helpful with one customer.  Port 4125 usage battle between services.  This is always a pain when a user calls reporting this error.  To fix it I’ve been restarting the Microsoft Firewall service and/or the IIS Admin service; however, that didn’t address the root cause.

Article ID
:
886209

Last Review
:
December 3, 2007

Revision
:
4.3

SYMPTOMS

When users try to connect to a remote desktop on a Microsoft Windows Small Business Server 2003-based network by using a Remote Web Workplace connection, they receive the following error message:

Connectivity to the remote computer could not be established. Ensure that the remote computer is on and connected to the Windows Small Business Server network.

This issue occurs when users click Connect to Server Desktops or Connect to Client Desktops on the Remote Web Workplace site and then try to connect to one of the server desktops or client desktops in the list.

CAUSE

This issue may occur if a process that is running on the Windows Small Business Server-based computer is listening on Transmission Control Protocol (TCP) port 4125. On a Windows Small Business Server-based computer, the Remote Web Workplace uses TCP port 4125 for its remote desktop feature. Sometimes, another process may use TCP port 4125 before Remote Web Workplace can claim port 4125. If another process is listening on this port, Windows Small Business Server cannot respond to the remote computer’s connection request.

Users cannot connect to remote desktops by using the Windows Small Business Server 2003 Remote Web Workplace

Unintended consequences – Vista SP1 Gotcha – RDC 6.1

**edit just found a new gotcha – see PT. 2 GPMC poof - RSAT tada**

 OK you deployers (not ‘deplorers’ as spell-check comically insists) of Vista SP1, have you noticed that attempts to remotely manage your SBS server (or any Windows 2003 Server) is failing to reach the console despite your use of the /console switch?

The reason is that the Vista SP1 includes the latest RDC client version 6.1. It no longer uses the /console switch but instead uses the /admin as the replacement. If you change your switch syntax of your mstsc.exe shortcuts and scripts then it will return to completing the console connections.

Take note you users of RWW that the console checkbox might not give you what you thought it would.  Connecting via Vista SP1, Server 2008, or soon to come XP SP3 will give the gotcha.  So look out!.  **edit**  posted now on the Official SBS Blog:  http://blogs.technet.com/sbs/archive/2008/03/20/using-rww-to-access-console-session.aspx**

Why? You may ask. This is explained in very helpful detail here: http://support.microsoft.com/kb/947723

The short story is that in a Server 2008 scenario you now no longer require a console connection to do console type work. If you are connecting to the older Server 2003 though you will currently need the /admin switch. Perhaps Server 2003 will be updated to directly work with RDC 6.1 later.

More on the new RDC 6.1:

http://blogs.technet.com/askperf/archive/2008/01/04/mstsc-exe-no-more-console-switch-in-rdc-6-1.aspx

http://blogs.technet.com/askperf/archive/2008/02/20/ws2008-rdc-enhancements-and-administrative-sessions.aspx

**also see newly found gotcha - PT. 2 GPMC poof - RSAT tada**

RWW with your own logo

To add your own logo to the SBS Remote Web Workplace aka RWW you merely need to replace the file shown below, RwwOEMLogo.gif, with your own .gif formatted logo.   The default is a blank 135×20 pixel rectangle – whatever size you bring in that fits in the RWW form window should be good to go.  The size of the header logo at the top is 448 x 175 pixels and its name is login.gif in case you want to modify it to carry that same look for use on the bottom logo.

Now Windows Home Server integrates this same RWW feature.  I’ll bet Kevin a dip of Graeter’s black-rasberry-chip that this works exactly the same in WHS.

Here’s my site in action:

Here’s another way I found it useful.  To notify those on vacation on cruise ships, skiing, or otherwise impractical to call that their access is suspended due to password security breach of a dismissed employee.  Can’t say that many words so brevity has its limits.  **FYI – notice something else customized?**

***late breaking update***

If you want your logo centered rather than alligned to the right you can make this happen.  Edit and search through the logon.aspx for this picture file’s name – ‘RwwOEMlogo.gif’.  Preceding it is the HTML code align=right.  Change “right” to “center” and you are golden.

A special note to the Paint.NET tool at www.getpaint.net .  It rocks!

Companyweb & Sharepoint v3 – Part 5 – Aimless Ramblings from a Blithering Lunatic . . .

Oh if only we could have this as a supported solution.  Still this makes the side-by-side installation all the more practical.  What is the main gain from having “Companyweb” as the address that resolves to WSS v3 vs. the original v2?  You don’t gain any new WSS v3 functionality.  What you do get is that any of the SBS embedded links such as the main one in RWW now will take users into WSSv3.  This is the meat of the matter.

Chad, you are the man!

Companyweb & Sharepoint v3 – Part 5

a.k.a.  -  Living on the Edge.  Just remember, there’s a reason it’s called the bleeding edge . . .    Here’s your warning:  In this post I am going to explain configuration changes I made to my own internal production environment to get http://companyweb to point to a new WSS v3 site.  This configuration is not supported by Microsoft or myself.  If you decide to try to replicate these settings in your environment, you are doing so at your own risk.

OK, let’s recap.  We’ve talked about the benefits of Sharepoint v3? Check.  We’ve talked about planning what we’re going to move, how we’re going to move it, and what we’re going to have to clean up after the move?  Check.  We’ve talked about prepping our environment so that WSS v3 search works?  Check.  We’ve talked about installing WSS v3 and accessing it via a common name?  Check.  Chad has warned everyone that just because he’s crazy enough to implement a non-supported configuration doesn’t me he’s recommending it or supporting it?  Check. 

Companyweb & Sharepoint v3 – Part 5 – Aimless Ramblings from a Blithering Lunatic . . .