Re: RDP not working

Tech-Archive recommends: Fix windows errors by optimizing your registry

Embarrased... I hadn't even thought of Windows firewall running on the
server. That seems to have resolved it. Thank you.

"Lanwench [MVP - Exchange]" wrote:

Ed <Ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
No problem running telnet via localhost.

Cool...then it's running, but something is blocking it.

Then do you have the Windows firewall enabled on the server? I don't use
that (and don't recommend it). If you don't use ISA on SBS Premium, I don't
see the point of using two NICs.

Or - any third party firewall app?



"Lanwench [MVP - Exchange]" wrote:

Ed <Ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I apologize for the mix-up.

Not running ISA nor am I able to telnet via port 3389.

Try this on the server itself in a command line:

telnet localhost 3389

If you can't do that, RD isn't running or the port has been changed.
Double check that all the requisite Windows services are started.



"Lanwench [MVP - Exchange]" wrote:

Ed <Ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
The port needs to be forwarded even if you are connecting on
internally on the same LAN?

No....but you didn't mention that (you said remote administration).
Are you running ISA?
Can you telnet to your server's LAN IP or NetBIOS name on port
3389?



I'll look into this. Our router is
managed externally.

"Lanwench [MVP - Exchange]" wrote:

Ed <Ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am attempting to do remote administration of our new SBC 2003
server and an unable to remote into the box. Remote desktop is
enabled, the server has a unique IP address. I am able to
access file services without any problems. Terminal Services
service is running. I've tried accessing via DNS and IP. None
of the 2 available RDP administation sessions are in use. Same
error when attempting to connect with remote desktop:

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

Any ideas?

If you're trying to connect using RD alone, is port 3389
opened/forwarded to your SBS server's LAN IP in your
router/firewall? If you're trying via RWW, is port 4125
open/forwarded to your SBS server's LAN IP?




.

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: XP Pro sp2 Firewall on Corporate domain
    ... >> I am aware of the port for Remote Desktop. ... but I suspect remote registry ... > Windows Firewall: Allow remote administration exception ... This policy setting also allows ...
    (microsoft.public.windowsxp.security_admin)