Sign in with
Sign up | Sign in
Your question

Remote Assistance w/ SP2

Last response: in Windows XP
Share
Anonymous
February 23, 2005 10:37:00 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I am having problems using remote assistance at an offsite location and I've
reached sort of a dead end. I am able to connect to and remotely control my
2 Windows Server 2003 domain controllers through remote assistance but all
of the Windows XP SP2 machines return a permission denied error when I
attempt to connect to them.

I've seen KB articles 301527 and 884910 which explain how to open the
apropriate ports and applications in the Windows Firewall and allow DCOM
objects to be run on a remote machine but I still am receiving the
"permission denied" error. I deployed those fixes through group policy and
made sure that remote offer remote assistance was turned on for all of the
machines in the domain and I gave those changes a day or two to propogate
but still no luck. So I guess what I'm looking for is a suggestion on how to
further troubleshoot this problem since I'm plum out of ideas. Any help
would be greatly appreciated. Thanks.

More about : remote assistance sp2

February 23, 2005 8:13:02 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Have you added the users to be allowed remote access and do those users have
passwords?

I just re-installed Windows XP and installed SP2 straight away, and I've had
no troubles with mstsc's connnecting.

"Thorin Rehkopf" wrote:

> I am having problems using remote assistance at an offsite location and I've
> reached sort of a dead end. I am able to connect to and remotely control my
> 2 Windows Server 2003 domain controllers through remote assistance but all
> of the Windows XP SP2 machines return a permission denied error when I
> attempt to connect to them.
>
> I've seen KB articles 301527 and 884910 which explain how to open the
> apropriate ports and applications in the Windows Firewall and allow DCOM
> objects to be run on a remote machine but I still am receiving the
> "permission denied" error. I deployed those fixes through group policy and
> made sure that remote offer remote assistance was turned on for all of the
> machines in the domain and I gave those changes a day or two to propogate
> but still no luck. So I guess what I'm looking for is a suggestion on how to
> further troubleshoot this problem since I'm plum out of ideas. Any help
> would be greatly appreciated. Thanks.
>
>
>
Anonymous
February 23, 2005 11:51:59 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Can you provide more information on this "permission denied" error?
---
Jeffrey Randow (Network MVP)

Remote Networking Technology FAQ -
http://www.remotenetworktechnology.com
My Networking Blog: http://www.networkblog.net
MS Network Community -
http://www.microsoft.com/windowsserver2003/community/ce...
MS Home Networking Community -
http://www.microsoft.com/windowsxp/expertzone/communiti...

On Wed, 23 Feb 2005 07:37:00 -0700, "Thorin Rehkopf"
<trehkopf@email.arizona.edu> wrote:

>I am having problems using remote assistance at an offsite location and I've
>reached sort of a dead end. I am able to connect to and remotely control my
>2 Windows Server 2003 domain controllers through remote assistance but all
>of the Windows XP SP2 machines return a permission denied error when I
>attempt to connect to them.
>
>I've seen KB articles 301527 and 884910 which explain how to open the
>apropriate ports and applications in the Windows Firewall and allow DCOM
>objects to be run on a remote machine but I still am receiving the
>"permission denied" error. I deployed those fixes through group policy and
>made sure that remote offer remote assistance was turned on for all of the
>machines in the domain and I gave those changes a day or two to propogate
>but still no luck. So I guess what I'm looking for is a suggestion on how to
>further troubleshoot this problem since I'm plum out of ideas. Any help
>would be greatly appreciated. Thanks.
>
!