Questions

How to fix remote desktop in windows xp

Tags:
+
0 Votes
Locked

How to fix remote desktop in windows xp

lm1917
I am using remote desktop Windows XP pro. Ver. PC1 and PC2 are alike.
When I use PC1 remote desktop go to PC2 and login PC2 reboots.
I tried from other PC???s I get the same PC2 reboots.
Went I go form PC2 to PC1 I can login OK.
Can you give me step-by-step instructions to resolve this issue
  • +
    0 Votes
    OH Smeg

    It sounds as if there is a corrupt User Profile involved here on the PC that is rebooting.

    Col

    +
    0 Votes
    lm1917

    Yes remote desktop works ok, I can go from PC2, to PC1 and PC3 and loogin with my user account and I see the desktop all PC's ok.
    We have installed remote desktop again with the some issue.
    I have new User Profile but I still get the rebooting issue.

    +
    1 Votes
    patdeutsch

    check the events viewer in the computer management. paste it here so we can help you.

    +
    0 Votes
    lm1917

    I will look in to this today. thanks

    +
    0 Votes
    lm1917

    Event Type: Warning
    Event Source: Microsoft Fax
    Event Category: Initialization/Termination
    Event ID: 32068
    Date: 11/3/2011
    Time: 9:21:06 AM
    User: N/A
    Computer: G000125804
    Description:
    The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*'

    Computer: G000125804
    Description:
    Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: Microsoft Fax
    Event Category: Initialization/Termination
    Event ID: 32068
    Date: 11/3/2011
    Time: 9:21:06 AM
    User: N/A
    Computer: G000125804
    Description:
    The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*'

    Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed.

    Event Type: Warning
    Event Source: EventSystem
    Event Category: (52)
    Event ID: 4356
    Date: 11/3/2011
    Time: 9:20:41 AM
    User: N/A
    Computer: G000125804
    Description:
    The COM+ Event System failed to create an instance of the subscriber partition:{41E90F3E-56C1-4633-81C3-6E8BAC8BDD70}!new:{7E89FF0B-F649-4F9A-A9C3-F05DFAAA3DA1}. CoGetObject returned HRESULT 80070005.

    Description:
    A listener has been started for entry number 7546 . Connections to this entry number will launch C:\win32app\ingr\FRMSHARE\bin\ftser.exe

    +
    1 Votes
    robo_dev

    The rebooting thing on PC2 sounds like a corrupt driver, service, or other Windows component.

    If system restore is enabled, go back to a restore point when it worked properly.

    +
    0 Votes
    lm1917

    I can fine a good system restore point the works properly. thanks

    +
    0 Votes
    lm1917

    Yes remote desktop works ok, I can go from PC2, to PC1 and PC3 and loogin with my user account and I see the desktop all PC's ok.
    We have installed remote desktop again with the some issue.
    I have new User Profile but I still get the rebooting issue.

    +
    0 Votes
    OH Smeg

    What's in the Event Viewer?

    If you've loaded a new user profile and gone to a earlier Restore Point it has to be a Windows Issue so we'll have to look at the Windows Logs.

    Post the Log here and we'll see what we can find if anything.

    Col

    +
    0 Votes
    techrepublic

    I have encountered this once before. To resolve the problem, I tried taking a laptop directly to the machine that was rebooting. When I started my remote session, the target machine threw out a BSOD and immediately rebooted. The video card was an older OEM ATI AGP card. Updating the drivers did not resolve the problem entirely, so I swapped cards with another machine (identical Optiplex GX620). That solved the remote desktop issue on the first PC, but the PC that received the suspect video card started having issues (including remote desktop issues), so the card was replaced entirely, which solved the problem.

    +
    0 Votes
    de.doughboy

    Did you set the windows boot recovery logs to minimal on the PC that keeps rebooting? I'd try this and check to see whats in the dmp.log after the computer restarts. Look for which driver is causing the system to reset. Chances are your hitting a firmware issue on the video card that forces an incompatible mode. Once you have ID which driver or .dll is causing it then you can upgrade that. Hint my video recorder card did this exact same thing until i found the correct patch for it. If you need help debugging using the dump command see tech republic guides on how to dedug restarts.

    +
    0 Votes
    lm1917

    I will do this on momday. thanks

    +
    1 Votes
    patdeutsch

    check the events viewer in the computer management. paste it here so we can help you.

    +
    1 Votes
    robo_dev

    The rebooting thing on PC2 sounds like a corrupt driver, service, or other Windows component.

    If system restore is enabled, go back to a restore point when it worked properly.

    +
    0 Votes
    lm1917

    Yes remote desktop works ok, I can go from PC2, to PC1 and PC3 and loogin with my user account and I see the desktop all PC's ok.
    We have installed remote desktop again with the some issue.
    I have new User Profile but I still get the rebooting issue.

    +
    0 Votes
    OH Smeg

    What's in the Event Viewer?

    If you've loaded a new user profile and gone to a earlier Restore Point it has to be a Windows Issue so we'll have to look at the Windows Logs.

    Post the Log here and we'll see what we can find if anything.

    Col

    +
    0 Votes
    techrepublic

    I have encountered this once before. To resolve the problem, I tried taking a laptop directly to the machine that was rebooting. When I started my remote session, the target machine threw out a BSOD and immediately rebooted. The video card was an older OEM ATI AGP card. Updating the drivers did not resolve the problem entirely, so I swapped cards with another machine (identical Optiplex GX620). That solved the remote desktop issue on the first PC, but the PC that received the suspect video card started having issues (including remote desktop issues), so the card was replaced entirely, which solved the problem.

    +
    0 Votes
    de.doughboy

    Did you set the windows boot recovery logs to minimal on the PC that keeps rebooting? I'd try this and check to see whats in the dmp.log after the computer restarts. Look for which driver is causing the system to reset. Chances are your hitting a firmware issue on the video card that forces an incompatible mode. Once you have ID which driver or .dll is causing it then you can upgrade that. Hint my video recorder card did this exact same thing until i found the correct patch for it. If you need help debugging using the dump command see tech republic guides on how to dedug restarts.

  • +
    0 Votes
    OH Smeg

    It sounds as if there is a corrupt User Profile involved here on the PC that is rebooting.

    Col

    +
    0 Votes
    lm1917

    Yes remote desktop works ok, I can go from PC2, to PC1 and PC3 and loogin with my user account and I see the desktop all PC's ok.
    We have installed remote desktop again with the some issue.
    I have new User Profile but I still get the rebooting issue.

    +
    1 Votes
    patdeutsch

    check the events viewer in the computer management. paste it here so we can help you.

    +
    0 Votes
    lm1917

    I will look in to this today. thanks

    +
    0 Votes
    lm1917

    Event Type: Warning
    Event Source: Microsoft Fax
    Event Category: Initialization/Termination
    Event ID: 32068
    Date: 11/3/2011
    Time: 9:21:06 AM
    User: N/A
    Computer: G000125804
    Description:
    The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*'

    Computer: G000125804
    Description:
    Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: Microsoft Fax
    Event Category: Initialization/Termination
    Event ID: 32068
    Date: 11/3/2011
    Time: 9:21:06 AM
    User: N/A
    Computer: G000125804
    Description:
    The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*'

    Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed.

    Event Type: Warning
    Event Source: EventSystem
    Event Category: (52)
    Event ID: 4356
    Date: 11/3/2011
    Time: 9:20:41 AM
    User: N/A
    Computer: G000125804
    Description:
    The COM+ Event System failed to create an instance of the subscriber partition:{41E90F3E-56C1-4633-81C3-6E8BAC8BDD70}!new:{7E89FF0B-F649-4F9A-A9C3-F05DFAAA3DA1}. CoGetObject returned HRESULT 80070005.

    Description:
    A listener has been started for entry number 7546 . Connections to this entry number will launch C:\win32app\ingr\FRMSHARE\bin\ftser.exe

    +
    1 Votes
    robo_dev

    The rebooting thing on PC2 sounds like a corrupt driver, service, or other Windows component.

    If system restore is enabled, go back to a restore point when it worked properly.

    +
    0 Votes
    lm1917

    I can fine a good system restore point the works properly. thanks

    +
    0 Votes
    lm1917

    Yes remote desktop works ok, I can go from PC2, to PC1 and PC3 and loogin with my user account and I see the desktop all PC's ok.
    We have installed remote desktop again with the some issue.
    I have new User Profile but I still get the rebooting issue.

    +
    0 Votes
    OH Smeg

    What's in the Event Viewer?

    If you've loaded a new user profile and gone to a earlier Restore Point it has to be a Windows Issue so we'll have to look at the Windows Logs.

    Post the Log here and we'll see what we can find if anything.

    Col

    +
    0 Votes
    techrepublic

    I have encountered this once before. To resolve the problem, I tried taking a laptop directly to the machine that was rebooting. When I started my remote session, the target machine threw out a BSOD and immediately rebooted. The video card was an older OEM ATI AGP card. Updating the drivers did not resolve the problem entirely, so I swapped cards with another machine (identical Optiplex GX620). That solved the remote desktop issue on the first PC, but the PC that received the suspect video card started having issues (including remote desktop issues), so the card was replaced entirely, which solved the problem.

    +
    0 Votes
    de.doughboy

    Did you set the windows boot recovery logs to minimal on the PC that keeps rebooting? I'd try this and check to see whats in the dmp.log after the computer restarts. Look for which driver is causing the system to reset. Chances are your hitting a firmware issue on the video card that forces an incompatible mode. Once you have ID which driver or .dll is causing it then you can upgrade that. Hint my video recorder card did this exact same thing until i found the correct patch for it. If you need help debugging using the dump command see tech republic guides on how to dedug restarts.

    +
    0 Votes
    lm1917

    I will do this on momday. thanks

    +
    1 Votes
    patdeutsch

    check the events viewer in the computer management. paste it here so we can help you.

    +
    1 Votes
    robo_dev

    The rebooting thing on PC2 sounds like a corrupt driver, service, or other Windows component.

    If system restore is enabled, go back to a restore point when it worked properly.

    +
    0 Votes
    lm1917

    Yes remote desktop works ok, I can go from PC2, to PC1 and PC3 and loogin with my user account and I see the desktop all PC's ok.
    We have installed remote desktop again with the some issue.
    I have new User Profile but I still get the rebooting issue.

    +
    0 Votes
    OH Smeg

    What's in the Event Viewer?

    If you've loaded a new user profile and gone to a earlier Restore Point it has to be a Windows Issue so we'll have to look at the Windows Logs.

    Post the Log here and we'll see what we can find if anything.

    Col

    +
    0 Votes
    techrepublic

    I have encountered this once before. To resolve the problem, I tried taking a laptop directly to the machine that was rebooting. When I started my remote session, the target machine threw out a BSOD and immediately rebooted. The video card was an older OEM ATI AGP card. Updating the drivers did not resolve the problem entirely, so I swapped cards with another machine (identical Optiplex GX620). That solved the remote desktop issue on the first PC, but the PC that received the suspect video card started having issues (including remote desktop issues), so the card was replaced entirely, which solved the problem.

    +
    0 Votes
    de.doughboy

    Did you set the windows boot recovery logs to minimal on the PC that keeps rebooting? I'd try this and check to see whats in the dmp.log after the computer restarts. Look for which driver is causing the system to reset. Chances are your hitting a firmware issue on the video card that forces an incompatible mode. Once you have ID which driver or .dll is causing it then you can upgrade that. Hint my video recorder card did this exact same thing until i found the correct patch for it. If you need help debugging using the dump command see tech republic guides on how to dedug restarts.