RE: Remote Assistance not working

Tech-Archive recommends: Speed Up your PC by fixing your registry

Jenny,

1. I re-ran the CEICW, with no change to my problem.

2. All computer have the remote box checked in system properties.

3. The shadow console session worked.

a. Yes, I can access the server box with RDC from any workstation.

b. Yes, remote assistance between XP workstations is successful.

c. When I try to initiate a remote assitance connection using the file
mode, the server does nothing, I double click on the file, and nothing
happens. I check the event log and I don't see anything.

Jenny, it seems as if the remote assistance "program" is just not working on
the server box. It's as if it is just missing.

Any suggestions?

""Jenny wu [MSFT]"" wrote:

> Hi Joe and Sean,
>
> Thanks for your update.
>
> Let's perform the following test to see if it helps.
>
> I. Please Re-run CEICW to refresh network connection. You can refer to the
> KB 825763 to configure the network connection:
>
> 825763 How to configure Internet access in Windows Small Business Server
> 2003
> http://support.microsoft.com/?id=825763
>
> II. Please check the following settings on the server box:
>
> Right click "My computer"-->Properties-->click "Remote" tab-->please ensure
> check the "Turn on Remote Assistance......" box.
>
> III. Please check if the SBS server box is using Shadow console session
> mode.
>
> a. Open the Group Policy snap-in (Gpedit.msc).
> b. In the left pane, under the Computer Configuration branch, expand the
> Administrative Templates branch.
> c. Expand the Windows Components branch.
> d. Click the Terminal Services folder.
> e. In the right pane, double-click Sets rules for remote control of
> Terminal Services user sessions.
> f. On the Setting tab, click Enabled.
> g. In the Options box, click Full Control with users'' permission, and
> then click OK.
>
> After verified above settings and then try to test the issue again. On your
> own XP computer:
> Start-->Run-->mstsc -v: <remote computer DNS name or IP address>
> Then you will get a remote desktop logon box. Input the user name and
> password, you will get a new terminal session as before.
>
> Just take it easy. Then in the desktop session, click Start-->Run-->input
> "shadow 0" (without the quotation mark) and then press enter.
>
> After a few seconds, you will see the shadow console session as you want.
> How about the result?
>
> If the issue persists, please help me collect some information to isolate
> the issue:
>
> 1. Can you access the server box using RDP connection from XP computers?
> 2. Please try to provide remote assistance between XP computers, how about
> the result?
> 3. Please try to initiate a remote assistance request from the server using
> file mode, how about the result? Please also check if the IP address is
> correct in the created invite file.
>
> I appreciate your time!
>
> Have a nice day!
>
> Sincerely,
>
> Jenny Wu
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> >Thread-Topic: Remote Assistance not working
> >thread-index: AcYWTQFP4xBDG22dRGefZl0J/nVCig==
> >X-WBNR-Posting-Host: 65.49.237.117
> >From: =?Utf-8?B?Sm9lLUFs?= <JoeAl@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <FF2A72BB-0044-4A48-89C5-EB2713F44819@xxxxxxxxxxxxx>
> <oHwmp8duFHA.768@xxxxxxxxxxxxxxxxxxxxx>
> <C29EBE61-6346-47AD-AC70-76A55FC5EBB7@xxxxxxxxxxxxx>
> <F87CB483-1D7A-4FD6-9AD7-F9FBFDF0954E@xxxxxxxxxxxxx>
> <E7679467-C703-4301-8ABB-134A5EAF6564@xxxxxxxxxxxxx>
> <DC8B0F35-BD91-4285-82C8-2BCF2938B91D@xxxxxxxxxxxxx>
> <EB5B999C-F73A-42D5-B4D4-DA5F1E17C05C@xxxxxxxxxxxxx>
> >Subject: RE: Remote Assistance not working
> >Date: Tue, 10 Jan 2006 17:19:01 -0800
> >Lines: 62
> >Message-ID: <EB3D6B8C-7C70-4524-BE3C-802A4B5DD049@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:235616
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >I am NOT using MS Mess. or IM for my remote assistance sessions. I seem to
> >remember suggestions NOT to run IM on the SBS server. IM workstation to
> >workstation is an option, but I tend to prefer to avoid promoting this
> >outside the internal network.
> >
> >There have been a couple times, including support sessions with Microsoft,
> >where rerunning the Internet connection wizard from the System Management
> >console on the SBS has resolved issues. Of course you should ALWAYS take
> care
> >if this is a production system!
> >
> >I have also renamed my admin account. This also may be a reason why I
> cannot
> >OFFER remote assistance from Server to workstation from the System
> Management
> >console. I have seen other instances where this has caused me pain.
> >
> >"Sean Vreeland" wrote:
> >
> >> Okay, I think I have gotten close to the problem. I can send and
> receive
> >> remote assistance requests to and from workstations ONLY. I cannot send
> or
> >> receive request from the SBS. I tried it in MSN messenger to and from
> the
> >> server and the remote assistance never launches. Could there be a
> problem
> >> with the actual program itself?
> >>
> >> "Sean Vreeland" wrote:
> >>
> >> > Well, I did everything Jenny had described and I still can't get the
> damn
> >> > thing to work in any meathod. I think it really is a problem with
> some
> >> > setting on my server.
> >> >
> >> > "Joe-Al" wrote:
> >> >
> >> > > Just to clarify, I removed all the suggested settings on MY
> WORKSTATION that
> >> > > had been recommended by Jenny because of their presence in the SBS
> Default
> >> > > Server Policy 'New Small Business Server Remote Assistance Policy'
> (already
> >> > > being applied)
> >> > >
> >> > > The method I described is:
> >> > > I create an invitation using: Start,, Help & Support,, Ask a
> friend,, Invite
> >> > > someone,, Save invitation to FILE,, 1hr,, Password,, SAVE file to
> Server
> >> > > Public directory.
> >> > >
> >> > > I then use my SBS Domain admin logon to run the invitation file, and
> walla
> >> > > walla washingtion, Im connected. That's it.
> >> > >
> >> > > The real question is why this cumbersome process does NOT work using
> the
> >> > > Server Management console as promised but does work via file
> invitation? It
> >> > > must be some wacky workstation policy on the server that is
> preventing
> >> > > access. This is will ALL my workstations who have been registered
> with SBS.
> >> > > Hmmm
> >> > >
> >> > >
> >> > >
> >> > > "Sean Vreeland" wrote:
> >> > >
> >> > > > Joe,
> >> > > >
> >> > > > How do you request from client to server? Using Windows Messenger
> or MSN
> >> > > > Messenger?
> >> > > >
> >> > > > ALso, I have tried to use the FILE meathod, but when I double
> click on the
> >> > > > file on the server, it does nothing. Nothing in the event logs.
> >> > > >
> >> > >
> >
>
>
.

Relevant Pages

  • Re: Remote Web Workplace Issue
    ... I had to "rebuild" my server. ... I could use RWW to a remote desktop on the ... I also am running a new workstation with Vista Ultimate that was never ... on that computer either but can use the remote desktop connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Web Workplace Issue
    ... RWW and Remote Desktop ... I had to "rebuild" my server. ... I also am running a new workstation with Vista Ultimate that was never ... on that computer either but can use the remote desktop connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Home Office wants a Remote Workstation to access resources
    ... > be remote controlled by the Location A workstation (via VPN/Remote Desktop ... >> to the Win2000 SBS server but it's not working out for us. ... >> domain (OLETANET) that is located at another home/residence. ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Port Forward
    ... And no I don't want to remote into both at the same time. ... remote into one of the computer workstations OR the Server. ... I don't log into my server with my user account. ... Right now my client Remotes into a workstation with default port ...
    (microsoft.public.windows.server.sbs)
  • RE: Cant remote access the server
    ... you have to make sure your SBS 2003 server have right network ... 328930 Cannot Reconnect to Remote Desktop After a Disconnection During ... | I can't use remote desktop from an XP workstation to access the SBS ...
    (microsoft.public.windows.server.sbs)