Thank you for replying so promptly with this good information.
Unfortunately, I might not have made myself clear.  My terminal server is a
Cisco 2511 router, not a version of Windows.

""Farhan Ahmed""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> How to Change Terminal Server's Listening Port
>
> --------------------------------------------------------------------------
--
> ----
> The information in this article applies to:
>
> Microsoft Windows NT Server version 4.0, Terminal Server Edition
> Microsoft Windows 2000 Advanced Server
> Microsoft Windows 2000 Professional
> Microsoft Windows 2000 Server
>
> --------------------------------------------------------------------------
--
> ----
> IMPORTANT: This article contains information about editing the registry.
> Before you edit the registry, make sure you understand how to restore it
if
> a problem occurs. For information about how to do this, view the
"Restoring
> the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key"
> Help topic in Regedt32.exe.
>
>
> SUMMARY
> By default Terminal Server and Windows 2000 Terminal Services uses TCP
port
> 3389 for client connections. Microsoft does not recommend that this value
be
> changed. However, if it becomes necessary to change this port, follow
these
> instructions.
>
>
>
> MORE INFORMATION
> WARNING: Using Registry Editor incorrectly can cause serious problems that
> may require you to reinstall your operating system. Microsoft cannot
> guarantee that problems resulting from the incorrect use of Registry
Editor
> can be solved. Use Registry Editor at your own risk.
>
> For information about how to edit the registry, view the "Changing Keys
and
> Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
> Information in the Registry" and "Edit Registry Data" Help topics in
> Regedt32.exe. Note that you should back up the registry before you edit
it.
> If you are running Windows NT or Windows 2000, you should also update your
> Emergency Repair Disk (ERD).
>
> To change the default port for all new connections created on the Terminal
> Server:
>
> Run Regedt32 and go to this key:
>
>
>    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal
>    Server\Wds\Repwd\Tds\Tcp
> NOTE: The above registry key is one path; it has been wrapped for
> readability.
>
>
> Find the "PortNumber" subkey and notice the value of 00000D3D, hex for
> (3389). Modify the port number in Hex and save the new value.
>
> To change the port for a specific connection on the Terminal Server:
>
>
> Run Regedt32 and go to this key:
>       HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal
>       Server\WinStations\<connection>
> NOTE: The above registry key is one path; it has been wrapped for
> readability.
>
>
> Find the "PortNumber" subkey and notice the value of 00000D3D, hex for
> (3389). Modify the port number in Hex and save the new value.
>
> NOTE: Because the use of alternate ports has not been fully implemented
for
> Terminal Server 4.0, support will be provided as "reasonable effort" only,
> and Microsoft may require you to set the port back to 3389, if any
problems
> occur.
>
>
> To Alter the Port on the Client Side
> Open Client Connection Manager.
>
>
> On the File menu, click New Connection, and then create the new
connection.
> After running the wizard, you should have a new connection listed there.
>
>
> Making sure that the new connection is highlighted, on the File menu,
click
> Export. Save it as name.cns.
>
>
> Edit the .cns file using Notepad changing "Server Port=3389" to "Server
> Port=xxxx" where xxxx is the new port that you specified on Terminal
Server.
>
>
> Now import the file back into Client Connection Manager. You may be
prompted
> to overwrite the current one, if it has the same name. Go ahead and
> overwrite it. You now have a client that has the correct port settings to
> match your change Terminal Server settings.
>
>
> NOTE: The Terminal Server ActiveX client listens on TCP port 3389 and
cannot
> be changed.
>
> Additional query words:
>
>
> -----Original Message-----
> From: Lurker [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 17, 2001 11:56 PM
> To: [EMAIL PROTECTED]
> Subject: Need to bypass Firewall-Can the telnet port be changed?
> [7:12707]
>
>
> I need to use the VPN to get to my study lab in the office.
Unfortunately,
> telnet appears to be blocked.  Is it possible to change the terminal
server
> configuration so it answers on a different port such as port 80?




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=12725&t=12725
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to