problem with remote assistance
I have two computers (A & B)that I am attempting to "assist" from the same
computer (C) (not simultaneously). I set up invitation files in a shared
folder on my server. When I attempt to connect to computer A from C
everything works fine. It used to work fine between computer C and B also.
Now when I attempt to connect to computer B I see (on C) a log in screen (for
computer B) that has a username shown and asking for a password. The
username is always the same no matter what username is logged onto computer
B. If I complete the login computer C automatically takes control and locks
out the user on computer B. I do not want control I just want to monitor
what is going on on computer B like I do for computer A. Any ideas what
changed and how to get it back? All computers are running XP Pro SP3. Thanks
.
Relevant Pages
- Re: Simple password Protect
... I also have a local user on the server ... I went to a workstation browsed ... There is nor reason to have the username or password ... >> give you access to that folder. ...
(microsoft.public.windows.server.networking) - Re: Locally stored profile does not load
... If your username is there with the letter "F" along with those other letters then yes you have full control on the folder. ... You can simply use the cacls command on your profile folder to ensure that you have the full control permissions on the folder: ...
(microsoft.public.windowsxp.help_and_support) - Re: View A Project details
... Everyone Full Control on the ViewDrop folder. ... We wrote the book on Project Server ... >>Notification Service is running under is failing. ... >>> - the above mentioned username has full permissions to ...
(microsoft.public.project.pro_and_server) - Re: Imac & PC Sharing
... has me stumped because never having set a username or password, ... I try to connect to server and share my MAc with the PC share folder. ...
(comp.sys.mac.system) - Re: View A Project details
... When I look at the event log I see the ... The server process could not be started because the ... the above mentioned username has full permissions to ... is set to: Administrators Full Control, ...
(microsoft.public.project.pro_and_server) |
|
