Windows Remote Assistance won't allow new session after restart


  1. Posts : 4
    Win 7 Pro
       #1

    Windows Remote Assistance won't allow new session after restart


    Helping a friend remove a "conduit" trojan remnant remotely. His antivirus (MSE) caught it for the most part but there are still settings in browsers that i reset (search engine, home page) and found it on the startup menu in msconfig and disabled that listing etc etc etc, cleared registry, ipconfig- flushdns, release, renew...checked their router settings, firewall settings, ran antivirus multiple times.

    The problem here is that when the remote machine is restarted and a NEW invitation is sent to me and I enter the correct password, it will not reconnect.

    When the client runs the internet connection troubleshooter, they receive a message that "windows needs more information" to successfully fix/diagnose the problem.

    What called the client's attention to a problem was that when their computer starts, an error msg states that it can't find a rundll Bin file. Running regedit and chasing the path produces nothing in the registry. A registry search (Find) for "conduit" "Conduit, Inc" etc etc produces no new results as I cleared them all in the first session. I also uninstalled all the remnant programs that conduit had downloaded. So upon restart, I don't think the trojan is being reactivated, but some setting is being applied in the Firewall (have tried disabling firewall, and changing network connection types... Home, Work and Public with firewall off) or Network settings (or their router?).

    We have reset the router several times as well.

    Any input would be very greatly appreciated. It seems like there is a setting being applied that prevents new Windows Remote Assistance connections. Perhaps changing a port number in a place that is obscured to me. I just don't know at this point.

    The thing is that this is happening intermittently. One in five restarts will allow a successful Windows Remote Assistance connection. Easy connect is not available to us.

    The client system is Windows 7 Home Premium and mine is Win 7 Pro.

    For clarity, We are using Windows Remote Assistance, NOT Remote Desktop.
    Last edited by gtechl33; 16 Dec 2013 at 12:22. Reason: clarity
      My Computer


  2. Posts : 4
    Win 7 Pro
    Thread Starter
       #2

    I found this thread and it fixed the problem. Thanks anyway. Apparently upon reboot the service was not starting on the client computer.




    " Open an “elevated prompt” command window
    Click Start
    Selected Programs/Accessories
    Right click “Command Prompt” and select “run as administrator
    An “Elevated Command Prompt” windows now opens (which looks quite normal btw)
    - In the command windows type the following command to stop the Peer Networking Identity Manager:
    Net stop p2pimsvc /y <enter>
    The result will be something similar to:
    The Peer Networking Identity Manager service is stopping.
    The Peer Networking Identity Manager service was stopped successfully.
    - Next, delete (or rename) the following file:
    "C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\idstore.sst"
    To do this:
    Open Windows Explorer
    Browse step by step to the folder location of the file by browsing C: ą Windows ąServiceProfiles ą LocalService ą AppData ą Roaming ą PeerNetworking
    Note: the Appdata folder is a hidden folder so you will need to enable the viewing of hidden folders in Windows Explorer: F10 ą Tools ą Folder Options ą View and select “show hidden files, folders and drives”
    Locate the file idstore.sst and rename it to idsore.sst.OLD
    - Reboot your PC"
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:16.
Find Us