Intra LAN Remote Desktop URL?

Page 2 of 2 FirstFirst 12

  1. Posts : 6,618
    W7x64 Pro, SuSe 12.1/** W7 x64 Pro, XP MCE
    Thread Starter
       #11

    acurasd said:
    You only need to put the IP address

    192.168.2.1

    or something like that.... that will be suffcient for Remote desktop.

    now for instance... if you have the 3389 blocked. You are going to have to manually change the port on each computer on a port that is open and of course use this:

    192.168.2.1:89

    if you changed the port to 89
    I understand what you are saying, but according to the people that I spoke with on the Outpost Forum, what I did was only to block 3389 to the outside world, not internal access. Here is a link to the thread in question, maybe I misunderstood something:

    Blocking Port 3389 - Outpost Users Support Forum
      My Computer


  2. Posts : 6,618
    W7x64 Pro, SuSe 12.1/** W7 x64 Pro, XP MCE
    Thread Starter
       #12

    Entering "remote" into the Start Menu's search window, I found a point in System Properties to enable RDP access, but when I tried to do so, it complained that without Windows Firewall being enabled, it couldn't enable RDP. I have it disabled, because I prefer using Outpost. Although I know that it had worked with both firewall enabled in the past, I didn't think it was a good idea to leave it that way, because that would actually make 3 firewalls when counting the one in my router. Is there a way to enable RDP without the firewall?
      My Computer


  3. Posts : 1,426
    7 Pro
       #13

    seekermeister said:
    brady said:
    Why block the internal use of RDP port? why not simply block the "incoming" connections to that port on the firewall thus removing the vulnerability that way, while maintaining your rdp access.
    I'm under the impression that the only thing that I have blocked is external access via RDP. If you believe otherwise, please elaborate.
    From what I've read in this forum and on outpost is that you're making mods to your windows firewall... Thus "outside" connections include your current network. I just double checked the default RDP rules and I don't see a way to exclude internal subnet but it may be possible.
      My Computer


  4. Posts : 6,618
    W7x64 Pro, SuSe 12.1/** W7 x64 Pro, XP MCE
    Thread Starter
       #14

    brady said:
    seekermeister said:
    brady said:
    Why block the internal use of RDP port? why not simply block the "incoming" connections to that port on the firewall thus removing the vulnerability that way, while maintaining your rdp access.
    I'm under the impression that the only thing that I have blocked is external access via RDP. If you believe otherwise, please elaborate.
    From what I've read in this forum and on outpost is that you're making mods to your windows firewall... Thus "outside" connections include your current network. I just double checked the default RDP rules and I don't see a way to exclude internal subnet but it may be possible.
    The only mods that I have made are those to the Outpost firewall, not Windows Firewall. As I mentioned in a post just above, the Windows Firewall is disabled entirely. I'm totally new to the entire concept of networks and RDP, outside of what has been said in this thread, and the Outpost thread, thus my confusion is growing larger and larger, rather than clearing. What may seem like a clear statement to you, means nothing to me, such as the one about excluding an internal subnet. If you want me to understand, put it in plain english, without making any assumption about my prior understanding.
      My Computer


 
Page 2 of 2 FirstFirst 12

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