Re: RDP access to SBS 2003 - HELP please

Cris, Russ and Wench :) let me try to provide a fuller description of what
happens and what I have tried. Thanks for taking an interest.

I have not checked the event log and can't do so until tomorrow.

When I try to connect, it takes about 30 seconds to fail with the message:
"The connection was ended because of a network error.
Please try connecting to the remote computer again."

This occurs from home and also from within the LAN where the server is
located and where I have tried the external IP as well as the internal
address as well as the name.

I tried telnet and it hangs perhaps indefinitely, but certainly for more
than a minute.
That is with a "Telnet> o xxx.xxx.xxx.xxx 3389"
or a "Telnet > o xxx.xxx.xxx.xxx"
However, with "Telnet> o xxx.xxx.xxx.xxx:3389", I promptly get a message to
the effect that it can't connect to xxx.xxx.xxx.xxx port 23.

Because I have tried from outside the office as well as from inside the
office, I have discounted the firewall or the ISP as being the cause of the
problem.

I can't tell whether port 3389 is open, unless the telnet test is
definitive. Is there some way to get SBS to show me the status of any port
or range of ports?

Yes, I do mean RDC, not the other acronym. What are RWW and CEICW?

I had installed McAfee some weeks ago, but have since uninstalled it.

I have switched off the Windows firewall.

I am not using the server console as a desktop, but we have had to on a few
occasions. When I install the new .NET version of the application we should
be able to to avoid having to do so again.

Thank you all so very much.

Does "Leo iii" ring any bells for any of you :>) ?

Regards.

"Lanwench [MVP - Exchange]" wrote:

leo-iii <leoiii@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have had SBS 2003 for about a year. I did most of my work from
home using Remote Desktop to connect to the server. Recently this
feature stopped working. I have visited System > Remote tab and
checked the lower box. I have visited TODO list and executed item 3.
I have installed T/S licence manager even though it seemed unecessary.

Can you please suggest further avenues for investigation?

Many thanks.

Unless you have a terminal server, uninstall Terminal Service license
manager.
Can you telnet to your public IP on 3389? In a command prompt on your home
PC,

telnet xxx.xxx.xxx.xxx.3389

Does it fail, or give you a blank screen?

Check using RWW to see if you can get to any computer on the LAN. If you can
get to a desktop, try connecting to it, and then type this in a command
prompt:

telnet servername 3389 <enter>

If that works, it's a problem in your firewall, or your ISP could be
blocking ports.



.

Relevant Pages

  • CLOSING: Norton Personal Firewall 2003
    ... go back to NPF2002 because it detects port scans, ... wrong during uninstall, install or setup of rules and programs and what ... Just created a ghost from my present system on my "server" (which is ... I'll think i'll wait for Symantec to respond. ...
    (comp.security.firewalls)
  • Re: Installing WSS3 on remote SQL Server 2005 & Different Internet
    ... Well primarily DNN has been slow in its response time when I request a page. ... installing on should only be a front-end server. ... Not sure about the port. ... I'm attempting to install the recently released Windows Sharepoint Services ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: IIS and SBS 2003
    ... I have a new sbs2003 install and if I telnet to localhost ... port 80, and type hhh and hit enter it returns a HTTP/1.1 400 Bad ... "broken" sbs server, it connects but then dumps me. ... If I http to localhost, companyweb or anything I get Cannot Find ...
    (microsoft.public.windows.server.sbs)
  • Re: Suggestion for a lexical (login mode via TCPIP)
    ... Not sure of it is the right one to modify or to add another one, but it would be useful to be able to get information on whether the user us coming in via FTP, TELNET, etc. ... This would also allow a LOGIN.COM to check if someone is coming in through a secure/SSL port for instance. ... For the HP SSH server, it seems to be undefined. ... forget about the possibility of virtual terminals. ...
    (comp.os.vms)
  • Re: RDP access to SBS 2003 - HELP please
    ... Might I add that 'out of the box', when I first got the server it worked ... of it to the telnet prompt and quit. ... Try the remote desktop connection to see if it works. ... the effect that it can't connect to xxx.xxx.xxx.xxx port 23. ...
    (microsoft.public.windows.server.sbs)