Re: REMOTE DESKTOP mmc snapin and non-standard port settings

From: Rob Jansen op de Haar (.)
Date: 08/30/04


Date: Mon, 30 Aug 2004 15:04:58 -0700

I ran into the same problem this weekend. I wanted to use the Remote
Desktops to give me access to the console session on a windows 2003 server
(which has a different default port configured).

I found that you can type MSTSC /console
from a command line to bring up the standard remote desktop window but with
the console "flag" set (even though it is not on the screen). You can then
specify whatever port you want.

Would be very nice though if MS could remove the check for ":" and allow for
a port number in Remote Desktops.

Rob

"Information Scavenger" <likeIwantspam@no-way.com> wrote in message
news:c547j0p4la4d6ibifc9engnrmp2vbbkjbn@4ax.com...
> I recently found the REMOTE DESKTOPS icon in my administrative tools
> via control panel after installing Windows 2003 Server Tools (or
> whatever they call it these days). This program seems awesome and for
> the type of work I do and the number of computers I am CONSTANTLY
> connecting to, this is a great program. However, the problem I am
> having is that about half the machines I connect to use non-standard
> port settings...the default port is 3389 and, for example, I want to
> connect to one with port 3390. In the MSTSC (terminal services
> connection that comes by default with all XP machines) if I wanted to
> connect to machine named machinea with a non standard port, I would
> simply type in "machinea:3390" as the destination and it would go.
> When I try to do the same in the REMOTE DESKTOPS it tells me I cannot
> use characters such as space or : or the brackets...and I have dug
> around all the options I can find and cannot find any port settings
> sections.
>
> Any help would be appreciated.
>
> Below is the online microsoft help article giving an overview of the
> program for those not yet familiar with it.
>
>
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/ts_tscmmc_overview.asp
>
>
> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> -----== Over 100,000 Newsgroups - 19 Different Servers! =-----



Relevant Pages

  • RE: Remote Web Workplace
    ... to all of the machines except ... Client that the port needed to be open, ... >allow port 4125 in from all remote ports. ... I am able to use Remote Desktop Connection to ...
    (microsoft.public.windows.server.sbs)
  • Re: ssh forwarding request denied
    ... | I have an ssh tunnel between two machines: ... | to port 1521 on the remote side. ...
    (comp.security.ssh)
  • RWW not working
    ... I cannot connect to client desktops or server desktops using Remote Web ... the computer might be too busy to accept new connections." ... they assure me it is setup like port 3389. ...
    (microsoft.public.windows.server.sbs)
  • ssh forwarding request denied
    ... I have an ssh tunnel between two machines: local port 5000 will be ... to port 1521 on the remote side. ...
    (comp.security.ssh)
  • Re: Remoting?
    ... you don't need to remote to the desktop to do that. ... some server 2003 /clients desktops remote ... Windows tools can be used to manage machines remotely directly (eg ... Steve Foster [SBS MVP] ...
    (microsoft.public.windows.server.sbs)