RE: Remote Web Workplace



Hi Colin,
We do not have a router. All we have are (2) NIC's and a DSL Modem....
"Colin" wrote:

Hi Craig,

Yes, the CEICW will configure remote access for you but your router will
need configuring manually. Which make/model do you have ? If OWA is working
OK then you must have forwarded port 443 to the server's external NIC right ?

Regards Colin.

"Craig Kalugin" wrote:

The remote computers were turned on, but not signed into. How do you enable
remote desktop connections on the computers?

"501c3help" wrote:

Well, I guess the simplest question to ask is if the remote computers are in
fact a) powered on b) not in a sleep mode, and c) remote desktop enabled. If
the power options are set to put the remote system in to a hibernating state,
you won't be able to connect while it's asleep. Somewhere in the bowels of
this or some other SBS forum there is a technique described somewhere that
will let you do a remote wakeup of a hibernating system in order to establish
a RDP connection. I don't remember where it is but if I recall, it's not a
very well documented or widely known method. Also, Remote Desktop
connections need to be enabled on the remote systems and each AD account that
will connect must have RDP access rights granted on that system.

"Craig Kalugin" wrote:

We have a SBS2003 server running ISA2004. I have configured OWA, which seems
to work fine for remote clients. I am having trouble with RWW. When a client
logs in and goes to select the computer to connect to , they get the
following message:
Connectivity to the remote computer could not be established. Ensure that
the remote computer is on and connecte dto the Windows Small Business Server
network. Any ideas?
.



Relevant Pages

  • Re: RWW Accessing desktops...
    ... > The Client could not connect to the remote computer. ... Remote connections ... > I ran CEICW, but when I came to the server certificate, I created a new ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW Accessing desktops...
    ... The Client could not connect to the remote computer. ... Remote connections ... I ran CEICW, but when I came to the server certificate, I created a new one. ...
    (microsoft.public.windows.server.sbs)
  • Re: Rmote Access problem
    ... The client could not connect to the remote computer. ... Remote connections ... Re-running CEICW on SBS server: ...
    (microsoft.public.windows.server.sbs)
  • UK T-Mobile 3G - no RWW/Remote Desktop?
    ... Been accessing Microsoft SBS servers via 3G card, then USB stick on T-Mobile ... The client could not connect to the remote computer. ... Remote connections ...
    (microsoft.public.windows.server.sbs)
  • Re: UK T-Mobile 3G - no RWW/Remote Desktop?
    ... The client could not connect to the remote computer. ... Remote connections might not be enabled or the computer might be too busy to accept new connections. ... Sounds like port 4125. ...
    (microsoft.public.windows.server.sbs)

Loading