Re: RWW connect to my computer not working
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 21 Oct 2008 11:39:46 -0400
You can test RDP to the client PC by seeing if the administrator can log into the client PC from the SBS or another computer on the LAN. Then, see if the user involved can RDP into his/her PC from another computer on the LAN. If either or both fail, the problem is on the client PC. In that case, just check the settings in CP -> System -> Remote.
I've run into this: User has standard user rights plus remote access. I temporarily make them an administrator, which includes remote access rights. When I put the account back to standard user, I have to explicitly grant remote access, because it's lost in the change from admin to non-admin.
"Chuck" <Chuck@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F60A8E8B-763E-4509-80EB-1C4F221AC02C@xxxxxxxxxxxxxxxx
Hello Dave,
Thank you for the suggestions. The FW was set to use Domain settings. I did
set the NLA service to automatic and for good measure restarted it, I the did
a gpupdate/force.
Other than waiting until tonight to have the user check it from home is
there a good way for me to see if it worked.
Thank you again,
Chuck
"Dave Nickason [SBS MVP]" wrote:
On the workstation that's not letting you connect to it remotely.
What's happening is that for a client PC that's joined to the SBS domain,
the non-domain firewall settings block remote access to that PC. When
you're connected to the SBS LAN, the domain settings allow remote access to
the PC. When not connected, the non-domain settings apply, and they block
remote access.
With Network Location Awareness set to manual, if it doesn't start fast
enough, the PC will think it's not on the domain. It then incorrectly
applies the non-domain firewall settings and remote access is blocked.
Setting NLA to automatic makes it start sooner and avoids this problem. The
killer is that with NLA set to manual, the problem can be intermittent. I
spent two days troubleshooting this when a user would lose remote access to
her desktop after WSUS had rebooted it.
"Jim Graue" <JimGraue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0FE56864-414F-416C-8853-7CEB44467D68@xxxxxxxxxxxxxxxx
> Mr. Nickason:
>
> My replies/comments/questions are in-line, below:
>
> "Dave Nickason [SBS MVP]" wrote:
>
>> Look in CP -> Firewall at a time when you can not connect over RWW. >> At
>> the
>> bottom of the first tab, does it say it's using the non-domain >> settings?
>
> Should this step be performed on the server, or the workstation that is
> failing to allow connection through RWW? Sorry if this seems like a
> stupid
> question.
> --
> Best regards,
> Jim Graue
.
- References:
- RWW connect to my computer not working
- From: Chuck
- Re: RWW connect to my computer not working
- From: Dave Nickason [SBS MVP]
- Re: RWW connect to my computer not working
- From: Jim Graue
- Re: RWW connect to my computer not working
- From: Dave Nickason [SBS MVP]
- Re: RWW connect to my computer not working
- From: Chuck
- RWW connect to my computer not working
- Prev by Date: Re: Hardware spec for SBS 2003
- Next by Date: Re: May need to move from SBS because of connection issues
- Previous by thread: Re: RWW connect to my computer not working
- Next by thread: Re: RWW connect to my computer not working
- Index(es):
Relevant Pages
|