1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved vista remote desktop will not connect to desktop XP pro

Discussion in 'Networking (Hardware & Software)' started by r0b, 2010/03/09.

  1. 2010/03/09
    r0b

    r0b Well-Known Member Thread Starter

    Joined:
    2010/01/19
    Messages:
    10
    Likes Received:
    0
    Lenovo laptop Vista Ultimate formally Premium successfully remotely connected wirelessly via a Z100G router to a Dell Desktop machine with Windows XP Pro using IP address. Computer name did not want to work. Did not bother to connect the other way.

    I recently had to relocate my desktop computer slightly which required me to disconnect and reconnect all connections and reset my router as well

    Laptop will no longer connect to desktop remotely but desktop will connect to laptop using IP address.

    Laptop cannot ping desktop.

    Desktop can ping laptop.

    The only error message I get is : Can’t connect to remote computer etc.

    Norton 360 is on the laptop and Zone Alarm is on the desktop. Neither have any special rules.

    Any suggestions would be appreciated.
     
    r0b,
    #1
  2. 2010/03/13
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    I'd start by disconnecting the router from the internet and then turn off the firewalls on both PCs and see if you can get remote desktop to work then. Then turn both firewall back on, reconnect to the internet and post back with how that worked.
     

  3. to hide this advert.

  4. 2010/03/14
    r0b

    r0b Well-Known Member Thread Starter

    Joined:
    2010/01/19
    Messages:
    10
    Likes Received:
    0
    No change in behavior what so ever.
     
    r0b,
    #3
  5. 2010/03/17
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    I know this is very basic, but have you checked that the desktop IP address hasn't changed in the move. Enter ipconfig at a command prompt to see the current IP address.
     
  6. 2010/03/23
    r0b

    r0b Well-Known Member Thread Starter

    Joined:
    2010/01/19
    Messages:
    10
    Likes Received:
    0
    Ipconfig on desktop provides 192.168.2.100

    router software tells me desktop is 192.168.10.13

    neither ip allows me to connect.

    Sorry for the delay in replying. Unless you have any other suggestions I think I will reset the router and start from scratch.

    Thanks for your help.
     
    r0b,
    #5
  7. 2010/03/25
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    Those two IP addresses are on different subnets (unless you are using not using the standard 192.168.0.0 mask of 255.255.255.0). For that to work, your router would need two different internal IP addresses - one for each subnet.

    Try manually setting the IP address of the desktop PC to 192.168.10.213, mask 255.255.255.0, with gateway and DNS set as the internal IP address of the router.
     
  8. 2010/03/31
    r0b

    r0b Well-Known Member Thread Starter

    Joined:
    2010/01/19
    Messages:
    10
    Likes Received:
    0
    The culprit may be the VOIP module which has the 192.168.2.xI am working with the VOIP provider. Will keep you advised.

    Thanks
     
    r0b,
    #7
  9. 2010/04/01
    r0b

    r0b Well-Known Member Thread Starter

    Joined:
    2010/01/19
    Messages:
    10
    Likes Received:
    0
    The modem for my telephone service was blocking the computer. Taking the modem out of the loop and attaching it directly to the router solved the problem. Thanks for your assistance. The good news is that I certainly learned more about TCP/IP and networking that I never thought I would.

    Robert
     
    r0b,
    #8

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.