Skip to content

6 Comments

  1. Chris Thornton
    September 12, 2020 @ 10:47 pm

    Thanks for posting this. it was 100% the problem.

    Reply

  2. reuben
    November 4, 2020 @ 6:00 pm

    Thanks , great article

    Reply

  3. Michael
    December 16, 2020 @ 12:20 pm

    You life saver! I recently installed VMWare on the XP box (because my version no longer wants to run with the latest W10 updates). The XP box then disappeared from W10's view; attempts to access shares on it resulted in rejected login attempts, and RDP attempts produced the error you describe above. Meanwhile my other W10 boxes continued to have meaningful relationships with XP.

    Pinging the XP box, it reported to have the same IP address as my W10's VMWare host-only virtual network (192.168.37.xxx). I reconfigured the W10 VMWare network to 192.168.38.xxx and now all is good again – W10 and XP have happily reconciled.

    Interesting to note, the next time I pinged the XP box, it showed a new IP address in the 10.0.0.xx range, not the 192.168.x.x address it had previously. I wonder why that is.

    Thank you, and may you have a Merry Christmas. I know mine will be much merrier having resolved this!

    Reply

  4. Ian
    December 27, 2020 @ 10:12 am

    Thank you.
    Running VirtualBox on 2x PC's, couldn't RDP.
    Changed network address in VBox and working as expected.
    Very quick solution to unexpected issue.

    Reply

  5. Joe
    February 18, 2022 @ 7:27 pm

    Thank you! This was giving me fits. I set up a new laptop with a fixed IP address. My current laptop is 192.168.1.150. I gave the new laptop a permanent address of 192.168.1.151. I couldn't see any address on my current laptop that conflicted with the new laptop. But after I assigned the new laptop 192.168.1.168 the problem was resolved.

    Reply

  6. Steve Erbach
    April 17, 2022 @ 7:21 pm

    Worked for me! Thank you.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *