Reply to Thread

Post a reply to the thread: Remote Desktop Connection with Port #

Your Message

If you are already a member Click here to log in

What is 10 and 5 added together?

 

You may choose an icon for your message from this list

Additional Options

  • Will turn www.example.com into [URL]http://www.example.com[/URL].

Subscription

Topic Review (Newest First)

  • February 21st, 2011, 01:50 PM
    Nude_Lewd_Man
    They wouldn't need a "VPN router", a normal router would suffice...as long as you can forward traffic on the port required, and use the user's/users' credentials against the SBS server's VPN ability...

    With regards to DNS and/or DDNS, they just transfer the domain name to a WAN IP address, which would be your LAN's public facing IP address...
  • February 21st, 2011, 01:33 PM
    amahure
    Lewd Man, see my response in Red.

    Quote Originally Posted by Nude_Lewd_Man View Post
    The VPN option is marginally less secure, as the same user details would let you in to either option...but a VPN means that a user has the option to (should they so wish) copy company data off to their own computer - although the same could be done via RDP too, it would be slower..
    ok..
    VPN would also mean that more computers are available for connection remotely, and don't need to change the RDP listening port number, or add/amend the firewall exceptions on the PCs...
    this seems like a good option, especially if they had a VPN router, but they don't
    If you were really anxious about security and locking down ports/traffic etc, then you could just get everyone to use the https://wan_ip_or_dns_name/remote (or the new equivalent, if that's no longer used) and force everyone to use that instead...and they can access their webmail via that link too
    Are you talking about using a DNS name like through DynDNS? Can I not use the https://wan_ip_or_dns_name/remote feature right now? If not, any suggestions..
  • February 21st, 2011, 01:11 PM
    Nude_Lewd_Man
    Steve,
    OP states it was working when they had W2k3 server, so I would presume that the computer settings wouldn't have changed...unless it was something custom configured by GPO on the W2k3 that wasn't inherited by the W2k8 server...

    amahure
    The VPN option is marginally less secure, as the same user details would let you in to either option...but a VPN means that a user has the option to (should they so wish) copy company data off to their own computer - although the same could be done via RDP too, it would be slower..

    VPN would also mean that more computers are available for connection remotely, and don't need to change the RDP listening port number, or add/amend the firewall exceptions on the PCs...

    If you were really anxious about security and locking down ports/traffic etc, then you could just get everyone to use the https://WAN_IP_or_DNS_name/remote (or the new equivalent, if that's no longer used) and force everyone to use that instead...and they can access their webmail via that link too..
  • February 21st, 2011, 12:31 PM
    amahure
    {delete this post please. don't see the option}
  • February 21st, 2011, 12:29 PM
    amahure
    HI lewd man. How can I setup a VPN connection to do the same thing? VPN Router? Isn't VPN safer than the StaticIP:PortNumber type of RDP connection?

    Quote Originally Posted by Nude_Lewd_Man View Post
    Hi,

    There are only a couple or three things that are likely to cause any effect here: one is the WAN (external) IP or DNS/DDNS not pointing to the correct place; the second is the LAN IP of the machine/s having been changed - which may be relating to them having had a reserved [LAN] IP in the DHCP scope of the W2k3 server, but this might not have been replicated onto the W2k8 one; or the user/s are no longer in the RDP authorised group that they are supposed to be...

    If you're using VPN to get in, then we'd need to find out whether the VPN is connecting/connected, and whether you're using IP or DNS to get to the computer/s..but if you only have a few users you could just configure the firewall to port forward the RDP traffic if you want them to have direct access (without needing the VPN connection first) or you could get them to use the /remote option (or at least that's what it was on W2k3 SBS) and use the web-initiated RDP connection instead...



    Let us know.
  • February 21st, 2011, 12:25 PM
    amahure
    Hi Guys thank you very much for all your responses. Here is an update.

    I was able to get into their Router from Comcast which has the Port Forwarding capabilities. I have setup my Port Forwarding, assiging Static IP's to PC 1-10 along with a Different Port Number. Which now allows me to remotely access PC's 1-10 with the Public IP Address. ie: 172.168.1.1:3345
    This seems to work on SOME computers, but not OTHERS. I am now trying to figure out why on some NEW laptops I am unable to RDP, while on the OLDER laptops I am able to Remote in. Any suggestions?
    Newer Laptops are Windows 7 machines. While the Older ones are WinXP.
  • February 21st, 2011, 09:16 AM
    Steve R Jones
    Lets not forget that by default RDP is disabled in the Windows Firewall
  • February 21st, 2011, 08:45 AM
    Nude_Lewd_Man
    Hi,

    There are only a couple or three things that are likely to cause any effect here: one is the WAN (external) IP or DNS/DDNS not pointing to the correct place; the second is the LAN IP of the machine/s having been changed - which may be relating to them having had a reserved [LAN] IP in the DHCP scope of the W2k3 server, but this might not have been replicated onto the W2k8 one; or the user/s are no longer in the RDP authorised group that they are supposed to be...

    If you're using VPN to get in, then we'd need to find out whether the VPN is connecting/connected, and whether you're using IP or DNS to get to the computer/s..but if you only have a few users you could just configure the firewall to port forward the RDP traffic if you want them to have direct access (without needing the VPN connection first) or you could get them to use the /remote option (or at least that's what it was on W2k3 SBS) and use the web-initiated RDP connection instead...



    Let us know.
  • February 21st, 2011, 08:04 AM
    Steve R Jones
    Which error message are they getting when the connection fails?
  • February 20th, 2011, 09:30 PM
    hoemee
    THe RDP is simple....but I have a few questions.....when you said "swap out" the servers....do you mean a server migration/replacement? Also, has the IP address (outside) changed?
  • February 17th, 2011, 02:26 PM
    amahure

    Remote Desktop Connection with Port #

    HI I am trying to accomplish the following and would really appreciate any guidance in doing so.

    I have a 2008 Small Business Server and about 10 Client Machines that were originally setup to Remote Desktop in from their Home Laptops to their Work Desktops. We had to swap out the Server from 2003 to 2008. Now none of them are able to use RDP Remotely.
    Clients are Windows 7 Machines.

    Where can I look to configure them back to their old settings? Router Settings? SBS 2008 Settings? ALso if you have any other way besides VPN to do this please let me know. Thanks

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Copyright 2014 All Enthusiast, Inc