Re: RDP access to SBS 2003 - HELP please

Merv, I do have a static IP at the office, but remember that RDP fails
whether I'm in the office on the same LAN as the server, or at home using
that IP address.



"Merv Porter [SBS-MVP]" wrote:

"the external fixed IP"... are you sure you have a static IP address from
your ISP? If not, your "external" IP may be dynamic and may have changed.
You can find out your external IP address by going to
http://www.whatismyipaddress.com/ (from the server).

--
Merv Porter [SBS-MVP]
============================
"leo-iii" <leoiii@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2F30EA4D-7303-4FDD-B357-ABBDB2261249@xxxxxxxxxxxxxxxx
Merv, I don't know the ISA version.
I have done nothing explicit with RWW or certificate.
I use the IP address in RDP and that will be the internal LAN IP or the
external fixed IP depending on whether I'm home or office.
Might I add that 'out of the box', when I first got the server it worked
fine from anywhere.
Something that I've done messed it up about a month ago perhaps.
I upgraded SQL server from 2000 to 2005.
I installed McAfee, but then uninstalled it.
I can't think what else I might have done.

Thanks.


"Merv Porter [SBS-MVP]" wrote:

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: Remote telnet through firewall failing
    ... >>LAN on which I am building this server, ... >>on the end user LAN. ... The telnet problem required a solution, ...
    (comp.unix.sco.misc)
  • Re: RDP access to SBS 2003 - HELP please
    ... Merv Porter [SBS-MVP] ... http://www.whatismyipaddress.com/ (from the server). ... When I telnet and specify port 3389 there is a delay ... the effect that it can't connect to xxx.xxx.xxx.xxx port 23. ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS Server Name
    ... You should NOT have port 80 forwarded to anything on your LAN. ... I would enable NetBIOS over TCP/IP since the single NIC should be your LAN ... When you run the CEICW, on the Web Server Certificate page, you should enter ... telnet SBSserverNetBIOSname 25 ...
    (microsoft.public.windows.server.sbs)
  • Re: Please help with ssh over internet to LAN server behind NAT
    ... can you telnet to the port and actually ... > see with tcpdump that the server is getting something. ... > The server and other computers on the LAN are behind a NAT. ... > The command and response looks like this: ...
    (comp.security.ssh)
  • Re: RDP access to SBS 2003 - HELP please
    ... Merv Porter [SBS-MVP] ... http://www.whatismyipaddress.com/ (from the server). ... When I telnet and specify port 3389 there is a delay ...
    (microsoft.public.windows.server.sbs)