Remote Web Workplace Stops Working with “The Client Could Not Connect” Error

Here is the symptom:

Remote web workplace suddenly stops working, and when you try to connect, you get the following error:

“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.”

However, the computer is on, and when logged in locally, all network services work.

Chances are, some service other than RWW has grabbed onto port 4125.  Here is how you can find out the offending service and then fix it.  This comes from Microsoft’s support site.

1. Open up a command prompt.
2. Run this command:  netstat -ano | find “:4125″
3. You’ll see the following output:  TCP IP_Address:Port IP_Address:Port LISTENING Process_Identifier
4. Open up the Task Manager
5. Click View, Select Columns, PID (Process Identifier)
6. Locate the service that was listed in #3
7. Open up Services and restart that service.  You may need to look at the Service executable path to confirm you are restarting the correct one.
8. RWW should grab port 4125 again.  I leave it as an exercise to the reader to figure out how to get that service to stop grabbing the RWW port.

Good luck!