asked on

Remote Web Workplace

Hi

I have just setup a remote connection for a client using windows small business server 2003.

I can connect remotely to the server with no problems, when I try to connect to a desktop pc I get

"Connectivity to the remote computer could not be established......"

The desktop PCs are on and connected to the network...

I tried this
http://support.microsoft.com/kb/886209

and I got

TCP [IP ADDRRESS]:4125 {IP ADDRESS]:4120 ESTABLISHED 1056

There were no processes running with PID 1056....

I dont think this is the issue anyway..

Even if I turn off the firewall/internet protection to a desktop PC I cannot connect....

In the router, I opened the ports necessary for the server... Do I really need to open them to each PC too?

I don't recall doing that before when I set it up before....

CHeers

Rob Williams

With remote web workplace you should only have to forward ports 443 and 4125 from the router to the workstations, and run the Configure E-mail and Internet Connection wizard. If you can access the server there should be nothing else to do......asuming you joined the machines to the domain using the http://SBSname/connectcomputer wizard, and created the user accounts using the Server management | users | add user wizard. The wizards set up routing, enable the service on PC's, group membership, permissions, firewall ports, and more. If you can manually turn of the firewall, which would normally be controlled by group policy it sounds like you may not have used the wizards.

cycledude

ASKER

Thanks RobWIll

Have done a little digging around and find that the Remote Access Control Manager was not started...

I tried to start this and got an error

"Error 1068: The dependency service or group failed to start"

I am guessing this is the problem?

cycledude

ASKER

OK, the telephony service was not starting correctly so got that going, then was able to startup

remote access auto connection manager
remote access control manager
Remote desktop help session manager
remote procedure call

but.... in 'routing and remote access' the server still has a little red dot by it, which should be green.... so I right clicked on it and selected 'start'

The icon is now green..... which should mean it's working.... however I still cannot connect to the desktop pc's .....

cycledude

ASKER

from 'server management' -> 'client computers'

if I try highlighting a pc, then click on 'connect to computer via terminal services' I get the following error

"The client could not connect to the remote computer

Remote connections might not be enabled or the computer may be too busy to accept new connections."

ASKER CERTIFIED SOLUTION

Rob Williams

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

cycledude

ASKER

@RobWill
After much messing about I have got to the root of the problem

and it was as you suggested... Remote access was not enabled on the desktop PC's!

Thanks

cycledude

ASKER

CHeers

Rob Williams

Thanks cycledude. Sorry I wasn't around earlier today to assist.
It sounds like the computers were not joined to the domain with the wizard. Just for reference in the future have a look at the following article and see how much the wizard does and how important it is:
http://msmvps.com/blogs/bradley/archive/2005/01/23/33632.aspx
Cheers!
--Rob