Results 1 to 2 of 2

Thread: Windows Server 2003 Terminal Services and NTL broadband

  1. #1
    Senior Member
    Join Date
    Jul 2003
    Reading, Berkshire
    53 times in 34 posts
    • tfboy's system
      • Motherboard:
      • MSI X470 Gaming Plus
      • CPU:
      • AMD Ryzen 7 2700
      • Memory:
      • 2x8GB Corsair Vengeance LPX)
      • Storage:
      • 512GB Crucial SSD
      • Graphics card(s):
      • 560 Ti
      • PSU:
      • Corsair RM 650W
      • Case:
      • CM Silencio 550
      • Operating System:
      • W10 Pro
      • Monitor(s):
      • HP LP2475w + Dell 2001FP
      • Internet:
      • VM 350Mb

    Question Windows Server 2003 Terminal Services and NTL broadband

    Hello all.

    I'm in this scenario. I have recently setup a system for a client using Windows server 2003 and a bunch of workstations.

    They are all behind a NAT ADSL firewall / router.

    Now I'm thinking about enabling TS so that I can remote desktop in over the web to perform admin stuff.

    Reading up about TS, MS say it all runs on port 3389.

    So I have two questions:

    1) Is port 3389 the only port I need to enable for forwarding to the server ?
    2) Does NTL (my broadband service provider) block port 3389 as it's a "security" issue ? If they do, then I'll have to think of some other way of connecting (VNC, other suggestions?)


  2. #2
    Administrator Moby-Dick's Avatar
    Join Date
    Jul 2003
    There's no place like ::1 (IPv6 version)
    385 times in 314 posts
    RDP does run on TCP3389 - its the only port you need to be forwarded from your router to the server.

    I'm pretty sure NTL dont block 3389 so you shoudl be ok .
    my Virtualisation Blog Virtualisation Podcast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts