RE: Remote Web Workplace

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Craig,

Well, although MS tell us it's safe to plug the external NIC straight into
an ADSL modem, many here recommend agains this. ISA is a good firewall but
there are arguments that as it's on a domain controller, it may not be doing
it's job as efficiently as if it were on a standalone box. Therefore I'd
strongly suggest you put a router or better still, a business class firewall
between your ADSL modem and external NIC.
There should be no need to enable Remote Desktop on the client PC's as if
they were joined with the 'connectcomputer wizard, this would have been
enabled automatically.
We've determined that the PC's are powered on (although have you confirmed
that they are not going into Standby, hibernation etc ?) and again, if joined
using the correct procedure, the Windows Firewall would have been
automatically configured to allow RDP connections. What AV are you running on
this network and does it have it's own personal firewall software installed
on the PC's ?

Regards Colin.

"Craig Kalugin" wrote:

Also, I am doing this testing from within our LAN. I just tried to connect to
the other computer using Remote Desktop Connection and was very successful. I
guess something is preventing using RWW. Does this tell us anything?

"501c3help" wrote:

On a target remote computer, right-click on My Computer and select
Properties. There is a Remote tab that is used to configure remote access
for that computer. This can probably also be set in Group Policy but I'm not
enough of a GP guru to be able to tell you exactly where or how to take that
route. I would suggest you check the Remote access properties on one target
machine, make sure it is enabled with the right access privileges, then try
connecting through RWW. If successful, then you can determine whether you
want to go desk to desk and configure each machine or research how to do it
through Group Policy.

You can also do a quick test to determine if ISA settings are causing
problems by doing a remote connection to one machine from another one inside
of the LAN. If you are on the local network on Workstation1 and can
establish a Remote Desktop Connection to Workstation2 on the local network,
but can't connect to Workstation2 from outside the external network, then you
know that the workstations are configured correctly but you have an issue at
the perimeter with ISA or a firewall. If you can't connect to Workstation2
while on the local network, then you know you have a client machine
configuration problem.

"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: is sbs2003 setting up my clients firewall, greyed out
    ... You could look there and see if remote access is enabled and if the user ... configures the Windows Firewall appropriately. ... the client could not connect to the remote computer. ... basically log onto the vpn connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Vista PC cannot rdp via RWW to Servers
    ... I wasn't sure if you uninstalled Sophos or just the firewall. ... MS-MVP - Windows Desktop Experience: ... > Type the remote site url ... a window from remote connection> desktop ...
    (microsoft.public.windows.server.sbs)
  • Sometimes it works sometimes it doesnt (VPN data issues)
    ... I am running a windows2k3 SBS server behind a linksys firewall. ... remote users having troubles connecting to our network. ... I figured this was a firewall issue blocking VPN data, ... the connection will stall and then starting the connection process ...
    (microsoft.public.windows.server.networking)
  • Re: More on Remote Desktop
    ... Also note that if you use the default listening port for Remote Desktop there is no need to append ... >> point it to the Static IP of the internal server. ... >> firewall to get between your clients and server on your own LAN. ... >> mine setup so that my firewall makes the PPPoE connection to my ADSL ISP. ...
    (microsoft.public.windowsxp.network_web)
  • RE: Cant logon to computer in SBS Domain..
    ... you can connect to the SBS 2003 Server. ... this pc from the SBS server via Remote Desktop. ... can sure that the pc is fine in the RDP connection. ... Group Policy settings for Windows Firewall, ...
    (microsoft.public.windows.server.sbs)