Re: Can RDP to One but not the other...

How to change the listening port for Remote Desktop
http://support.microsoft.com/default.aspx?scid=kb;en-us;306759

How to configure the Remote Desktop client to connect to a specific port
when you use Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;304304





--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com


"Andre" wrote:

> and for that matter, could you possibly post the link of the appropriate reg
> key to change, that would solve so many things for me :D .. I was told
> previously it wasn't possible to change the port.
>
>
> "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:F0D35161-1D78-4FBC-AD74-EEC33E6909E7@xxxxxxxxxxxxxxxx
> > Since the terminal server service can't be manually
> > started/restarted/stopped, you need to restart the server to get your new
> > port setting.
> > --
> > Patrick Rouse
> > Microsoft MVP - Terminal Server
> > http://www.workthin.com
> >
> >
> > "ola_atb" wrote:
> >
> > > Hello all,
> > >
> > > I have two 2003 servers, one is the AD and the other has exchange server
> > > 2003 on it. I only have a webserver running on the AD and it has very
> little
> > > load. I think I might have tried to fiddle with Terminal Services on the
> > > first server when I first installed the servers, but I am not quite
> sure.
> > > Right now, I am not at home base, and will not be for a while. So I
> walked my
> > > assistant through enabling remote desktop on both Servers. However,
> because I
> > > valued the exchange server more than the webserver, I decided to change
> the
> > > port on the webserver. So we changed the port from 3389 to 3390 on the
> > > webserver, using regedit.
> > >
> > > I then proceeded to forward the ports on my router. Now I can RDP to the
> > > Exchange server, but when I try to rdp to the webserver by using the Win
> XP
> > > RDP Client and typing webserver.mydomain.com:3390, I get an error
> message
> > >
> > > The specified remote computer could not be found. Verify that you have
> typed
> > > the correct computer name or IP address, and then try connecting again.
> > >
> > > Did we need to restart the server after changing the RDP port number
> before
> > > it works, or is there something I might have missed?
> > >
> > > Assuming I fiddled with Terminal Services because I thought I would need
> to
> > > remotely get to the server, and did not fully configure it, could that
> be the
> > > problem, and if so, how do I get terminal services to the default stage
> so
> > > that RDP can work?
> > >
> > > Thanks in advance
> > > --
> > > An Avvid Student
>
>
>
.

Relevant Pages

  • The local policy of this system does not allow you to log on inter
    ... I also checked "Deny Logon Locally" and nothing is configured. ... I am trying to logon to the Terminal Server ... I have added the group Domain Users to the Builtin Group Remote Desktop ...
    (microsoft.public.windows.terminal_services)
  • Re: SBS2003, Fully patched, and cannot RDP into machine
    ... I try to telnet to port 3389, ... Remote Desktop is enabled and the RDP-Tcp shows up in the Terminal Services ... you have port 3389 forwarded to the SBS NIC? ... Have you rebooted the server a couple of times after hte upgrades? ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Services over port 80 over HTTPS only
    ... firewall does not allow RDP protocol calls due to which Terminal services ... Secure Gateway and 2008 TS can connect over SSL on port 443, ... Microsoft MVP - Terminal Server ... being used by the clients over the internet using Remote Desktop client ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote Connection Issue
    ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
    (microsoft.public.windows.server.sbs)
  • Re: Ports and more
    ... Also, just to let you know, we just opened a support ticket with Microsoft ... KB938645 is about a situation where the COM port *is* succesfully ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)