There's kind of a corner case that can cause this. There are two sets of
group policy settings for the Windows Firewall, domain and non-domain. This
is so that when your laptop is in the office it works as a local PC, while
when it's on the road its security is higher. The non-domain settings block
To diagnose this, when the computer is blocking the connection, have someone
go to CP -> Windows Firewall and see if, at the bottom of the first tab, it
says it's using the non-domain settings. If it's using non-domain, that's
the cause of the rejected connections. The fix is to simply set the Network
Location Awareness service to automatic startup instead of manual - it runs
all the time anyway, but in Automatic it starts faster, preventing this
problem. Reboot or gpupdate /force, and you'll never have the problem with
that workstation again.
This isn't a common problem but I've seen it maybe 10 times. When I have
users who frequently log in remotely, I routinely just set NLA to automatic
(only on XP - auto start is the default setting in Vista).
"Charlie Lewis" <charlie_c_lewis@newsgroup> wrote in message
> Not for the first time, I'm having trouble connecting to a client computer
> on the SBS network remotely via Remote Web Workplace.
> As far as I know, all the following are true:
> - The PC is in the SBS domain.
> - You can access the RWW login screen, and see the PC in the computer
> - All relevant ports are open in the routers and firewalls at the company
> site and remote locations.
> - No power-saving is enabled on the PC.
> - You can access the server via RWW.
> - IE8 is the browser used for access.
> However, when you click on the required computer, it says that it is
> unavailable or offline.
> Any ideas?