Re: RDP access to SBS 2003 - HELP please

And what are you using for the RWW certificate (an ip address or a domain
name)?
And what are you using for the RDP address to connect to the server (an ip
address or a domain name)?

--
Merv Porter [SBS-MVP]
============================

"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:O5BO7UzyHHA.3768@xxxxxxxxxxxxxxxxxxxxxxx
Do you have a static or dynamic public IP address from your ISP?

--
Merv Porter [SBS-MVP]
============================

"leo-iii" <leoiii@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6E509DCD-925E-49BD-858E-5C5FFF347767@xxxxxxxxxxxxxxxx
I neglected to include the answer to your other question: SBS Premium.



"Merv Porter [SBS-MVP]" wrote:

How about posting an ipconfig /all for the server?

SBS Standard or Premium? (ISA 2000 or 2004)?

--
Merv Porter [SBS-MVP]
============================

"leo-iii" <leoiii@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:280A00EE-774E-421E-A22B-01968A800AD5@xxxxxxxxxxxxxxxx
Merv(yn),

Thanks for the reply and the suggestion. I deleted the key and
rebooted.
The key was recreated, but the problem was not solved. I still got a
network
error when I tried connecting with Remote Desktop from within the LAN
and
from home. When I telnet and specify port 3389 there is a delay of
about
20
seconds, then the command window clears and I eventually have to
escape
out
of it to the telnet prompt and quit.

I would greatly appreciate any further suggestions.

Thanks.



"Merv Porter [SBS-MVP]" wrote:

Cannot connect to server remotely or locally
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/1ca5c0c747f3a48a/66aab776f3b4a240?lnk=st&q=sbs+remote+desktop+The+connection+was+ended+because+of+a+network+error&rnum=4&hl=en#66aab776f3b4a240

On the SBS server...

1. Open Registry Editor (regedit.exe), locate the following registry
key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters

2. Click Parameters, click File menu>Export, backup the Parameters
key.

3. Delete the "Certificate" REG_BINARY value under the Parameters
key.

4. Reboot, the value will be recreated again.

Try the remote desktop connection to see if it works.
-------------------------------------

--
Merv Porter [SBS-MVP]
============================

"leo-iii" <leoiii@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE0F6192-3690-485F-879C-645986C96D01@xxxxxxxxxxxxxxxx
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

  • 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: 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: 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)
  • Re: IP Blocker in SBS2003 exchange
    ... > What I was trying to explain in the telnet section was that I realise ... > the server is listening for connections on ports 110 and 25. ... > but he can connect to port 110. ... > well as another wireless broadband connection. ...
    (microsoft.public.windows.server.sbs)
Loading