Remote Desktop Connection (RDC) - Network

Page 2 of 18 FirstFirst 123412 ... LastLast

  1. Posts : 2
    win7
       #10

    I have not tried it, but here is a link that describes how to enable it:
    Windows 7 : Enable Multiple User Access Login/Concurrent User Sessions
      My Computer


  2. Posts : 3
    Windows XP Pro SP 3
       #11

    Weird RperDC issue


    I'm running Win7 RC1 on one system in my home network. The rest of my systems are running XP Pro SP3. Yesterday, I setup the Win7 system as a Remote Desktop host. I was able to connect to it from both my desktop and laptop systems. After I tested the connection several times, I decided to setup my XP and Win7 desktops so that I could access them from outside my network (via the Internet) using RDC. I've done this for clients numerous times by changing the listening port on the individual systems from 3389 to a unique number (such as 4001, 4002, etc.). Then I created rules in my router to direct any requests to my Public IP that include one of the RDC port numbers to the specific system (by IP). For example, my main system has the static IP of 192.168.1.10 and had the listening port set to 4001. I created a rule in my router that any requests coming to <myPublicIP>:4001, should be redirected to 192.168.1.10, port 4001. This has always worked in the past. This time, as soon as I rebooted my systems to recognize the registry change for the port numbers, I could no longer access either system via RDC. I tried everything I could think of to access them with no success.

    I should tell you that all of this was on the local network, no outside access. So, technically, the router and rules shouldn't even come into play. After hours of trying and failing, I decided to try one last thing. I changed the listening ports back to the default 3389 on both systems, deleted the rules on the router, and rebooted both systems. I tried to access each via RDC after they'd rebooted... SUCCESS.

    I'm thrilled that it's fixed, but very perplexed as to why it didn't work the way I've always done it before. Anyone else have a similar experience? Any light shed on this would really be appreciated!

    Clem
      My Computer


  3. Posts : 1
    Windows 7
       #12

    I am not sure if this thread is still being monitored at all, but I ran into an issue with Remote Desktop that I have not been able to find an answer. When accessing my desktop system, using my home network, I click on Internet explorer and it flashes on the screen for a split second and then closes. No instances of it in the task manager. Cannot even open links from other programs (i.e. e-mails for Outlook). Any thoughts or suggestions would be appreciated. This used to work using RDC on XP and Vista; I am just wondering if there is a new setting that I am now missing somewhere. Thank you for your time and response.
      My Computer


  4. Posts : 12
    Windows 7
       #13

    Oh, thanks ...
      My Computer


  5. Posts : 3
    Windows XP Pro SP 3
       #14

    Whiskey,
    The answer is no. You can't run multiple concurrent RDC sessions on the same PC. You can only be logged on one at a time.

    Clem
      My Computer


  6. Posts : 4,573
       #15

    NOT SO FAST...

    There is a working method for using RDC to login to a machine concurrently and unseen. It is here in the forum. I will search for the thread.
      My Computer


  7. Posts : 3
    Windows XP Pro SP 3
       #16

    Nos,
    I've been using RDC with my clients that have XP for years. When I ran into this original issue with Win 7, after posting my problem on this forum, I did a ton of research and found an interesting item (can't remember where... :)). I've always changed the listening ports on systems behind the router then created specific rules to forward to the individual systems. The item I found indicated you don't have to do that. Everything is the same except for two steps:

    1. Leave the listening ports all set to default (3389)
    2. When a connection request comes in, it will have the "new" port attached to it (ex. 77.44.123.6:4001). The firewall rule you create will now forward the "new" port (in this case 4001) to port 3389 on the specific system you want the "new" port to access.

    Using the above example, if the system you want to access is 192.168.1.35, the rule would forward a request coming to 77.44.123.6:4001 to 192.168.1.35 port 3389. It actually makes perfect sense and doesn't require modifying the registry! I've tested it and it works perfectly each time.

    Clem
      My Computer

  8.   My Computer


  9. Posts : 1
    Windows 7 Home Premium x64
       #18

    When I try to set Remote settings in the Remote tab I've only see Allow remote assistance, but nothing to select users. Is that have something with the version of the OS, or administrative privileges?
    I'm using RTM Home Premium x64 and I do have Administrative account.
    Any suggestions? What I did wrong?
      My Computer


  10. Posts : 2
    Windows 7 RC 64 Bit
       #19

    I just installed Windows 7 RC 64 Bit. Everything so far has worked very well with the exception of RDP. I can connect from the Win 7 machine to several Vista Machines on the LAN. I cannot however connect from the Win 7 machine to any of the Vista machines. I have followed the instuction here but can't seem to get it to work. All of the other machines I have (a combination of XP & Vista) all connect to each other no problem. The only problem I have is connecting any of them to the Win 7 machine either on the LAN or WAN. I have even tried turning off the firewall to no avail. Ideas?
      My Computer


 
Page 2 of 18 FirstFirst 123412 ... LastLast

  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 13:30.
Find Us