Re: Client port range
From: Dave Patrick (mail_at_NoSpam.DSPatrick.com)
Date: 05/06/04
- Next message: Mark: "RE: Locking Desktop"
- Previous message: Dan LeBaron: "RE: Urgent Terminal Server Printing"
- In reply to: pdx: "Client port range"
- Next in thread: pdx: "Re: Client port range"
- Reply: pdx: "Re: Client port range"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 6 May 2004 15:22:20 -0600
By default 3389
-- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "pdx" wrote: |I have a remote user (Windows 2k Pro with new RDP client connecting to Windows 2000 Terminal Services) who can't connect to one of our Terminal Services servers. No one else has a problem and I have tested connectivity with his account from outside our firewall and connected successfully. | I suspect that his firewall (which until recently he didn't know he had) is blocking the ports necessary for the Terminal Services machine to connect back to his client. Tests (netstat -na) on our three machines running Term Services showed the server connecting to the client on ports (3 different sessions) 1441, 1445 and 1447. | Does anyone know if there is a distinct, finite range of ports that the server uses to establish the session with the client or is it a random range > 1024? | | Thanks
- Next message: Mark: "RE: Locking Desktop"
- Previous message: Dan LeBaron: "RE: Urgent Terminal Server Printing"
- In reply to: pdx: "Client port range"
- Next in thread: pdx: "Re: Client port range"
- Reply: pdx: "Re: Client port range"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
