Re: Remote Administration

Tech-Archive recommends: Speed Up your PC by fixing your registry

Get LogMeIn IT Reach at www.logmein.com. It broadcasts via SSL and doesn't
require any ports to be opened on a physical hardware router or in ISA. I
highly recommend it.

Andrew

"Keith" wrote:

CY,

I am connecting to the server through the router using the static IP of the
server itself, so I don't think I can use port forwarding at the router. Any
other ideas?

Thanks,

Keith


"CY" wrote:

You would login to your router, and set port 3389 to forward to the server IP
address. I'd wait till Lanwench replies again, though, her answers are
always aces.

"Keith" wrote:

Thanks for the quick response!

Pardon my ignorance, but how do I check that port 3389 is open and forwarded
to the LAN IP? In ISA Management, the IP Packet filters "SBS TS 3389 In
CustomFilter" and "SBS TS 3389 Out CustomFilter" are set to allow. Is that
what you mean? I'm just not that familiar with this sort of thing.

Thanks,

Keith


"Lanwench [MVP - Exchange]" wrote:

Keith <Keith@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am trying to administer my SBS 2003 server from my home computer.
I have set up the Terminal Services configuration to allow this. I
am able to connect using Remote Desktop Connection on a client
computer within the local network with no problem. However, when
connecting from home, I get the following error message:

"The client could not connect to this computer. Remote connections
might not be enabled or the computer might be too busy to accept new
connections."

I've seen other posts saying to reconfigure the remote access using
CEICW, but this doesn't work on my SBS right now due to failures in
the SP1 updating. This will be corrected when I have time, but in
the meantime I would like to know how to manually configure the
server to enable the remote connection and therefore allow me to
remotely administer this machine.

Thanks,

Keith

If you're trying to use RD directly to the server, you need to ensure that
TCP port 3389 is open/forwarded to the LAN IP of the SBS box. Since it's
working internally, it can't be the server config itself.



.

Relevant Pages

  • Re: Cannot telnet some ports
    ... Some with remote administration feature I believe. ... >> From a Windows 2003 Server SP2 ... >> fromn the 2k3 serrver but can telnet into any other port. ... kerberos 750/udp kdc # Kerberos udp ...
    (microsoft.public.windows.server.general)
  • RE: Remote Web Workplace not completely working.
    ... In order to allow a remote desktop connection to a client computer through ... TS requests through a firewall on TCP port 4125, ... To open the port 4125 on ISA, we can re-run CEICW to confirm it. ... server certificate) and then click Next. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Rule for Remote Desktop?
    ... My server has a private IP address on the WAN NIC. ... I've just had an opportunity to try testing Remote Desktop through RWW from ... attempts being made from the logging interface in ISA to port 4125 when I ... There are three connection ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to Connect to Server/Client Desktop using RWW
    ... Please post the results of an ipconfig /all for the sbs server. ... I did another test after turning off the firewall on the remote. ... If port 4125 was not forwarded on the sbs machine, ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Kazzaa- spyware
    ... > server, then file retrievals from your machine must be done with the ... >>- Allow all UDP for both direction, for local port 123 and remote port ... > But unfortunately RR is changing the DNS addresses all the time. ...
    (comp.security.firewalls)