Problem with Terminal Services Client and Server 2003

From: Frank Rudolph (fjr_at_controlsmith.com)
Date: 03/27/04

  • Next message: Me: "Re: p2p security" 
    Date: Sat, 27 Mar 2004 08:58:55 -0800

    I have just recently installed a copy of Microsoft Small
    Business Server. We also have a Netgear firewall.

    I can connect to the server using Remote Desktop through
    the intranet address (192.168.2.16) wothout any problem.

    But when I use our symbolic internet name or even our
    fixed IP address I get a mysterious message that says:

    "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.

    It is also possible that network problems are preventing
    your connection. etc,..."

    I have searched newsgroups, ms knowledge bases and asked
    colleagues for help and have come up with a couple of
    rather tenuous near-fits for my problem description. But
    when I looked at the instructions for installing
    the "work-arounds" that involved lengthy registry edits
    and were really for similar-but-not-quite-small-business
    servers, I figured I'd better wait before risking such
    a "fix".

    Yes, I did activate port 3389 on the firewall to go to
    192.168.2.16

    Anyone ever had this particular problem?

    Sincerely,
    Frank Rudolph

  • Next message: Me: "Re: p2p security"

    Relevant Pages

    • Re: SBS LOGIN FREEZE, HELP!
      ... and access Computer Management, do it there. ... Now restart the server and see what happens. ... I was connected to the machine via remote ... It then says installing update 1 ...
      (microsoft.public.windows.server.sbs)
    • Re: SBS LOGIN FREEZE, HELP!
      ... and access Computer Management, do it there. ... Now restart the server and see what happens. ... I was connected to the machine via remote ... It then says installing update 1 ...
      (microsoft.public.windows.server.sbs)
    • Problem with Terminal Services Client and Server 2003
      ... We also have a Netgear firewall. ... I can connect to the server using Remote Desktop through ... "The client could not connect to the remote computer. ... when I looked at the instructions for installing ...
      (microsoft.public.exchange.admin)
    • Problem with Terminal Services Client
      ... We also have a Netgear firewall. ... I can connect to the server using Remote Desktop through ... "The client could not connect to the remote computer. ... when I looked at the instructions for installing ...
      (microsoft.public.windows.server.sbs)
    • Problem with Terminal Services Client
      ... We also have a Netgear firewall. ... I can connect to the server using Remote Desktop through ... "The client could not connect to the remote computer. ... when I looked at the instructions for installing ...
      (microsoft.public.windows.server.sbs)