Hi there,

I have this week installed SBS 2003 for a customer of mine and was
pleased to quickly find that I could connect using Remote Desktop
Connection and work on the server from the comfort of my desktop
machine.

Remote Desktop has been working perfectly for the last two or three
days but suddenly stopped doing so this morning, when I moved the
server from my office to the client's in order to do some initial
deployment testing. I was using it not 10 minutes before I left home
but less than an hour later and ever since I have been getting "The
client could not connect to the remote computer" messages when I try to
connect.

I'm connecting to the machine over the LAN and I can ping it, so the
problem's not with NAT or port-forwarding or anything like that. In
System Properties > Remote "Enable Remote Desktop on this computer" is
checked and Terminal Services & its dependency RPC are both showing as
started in Services [1] but Remote Desktop nevertheless seems not to be
running. A port scan from another machine
<http://rafb.net/paste/results/31nZOS31.nln.html> shows no response on
port 3389 and running `telnet localhost 3389` on the server also fails.

I don't believe that Windows firewall is running on this machine
(Windows Firewall / ICS is disabled in Services) and I don't believe
that ISA Server is installed, either - Start > All Programs does not
not show the entry for Microsoft ISA Server mentioned in KB 828053.

Can anyone advise the best way to trouble-shoot this further, please? I
am not experienced with Terminal Services / Remote Desktop and so I'm
consequently at my wits' end.

Stroller.










[1] I haven't deployed Windows server before and I find it curious that
- although I'm a member of the Administrators & Domain Administrators
groups - the "Start" and "Stop" buttons I've used in XP Home are
greyed-out on this system.

"Stroller" <stroller@bigfoot.com> wrote...
>I have this week installed SBS 2003 for a customer of mine and was pleased
>to quickly find that I could connect using Remote Desktop
>Connection and work on the server from the comfort of my desktop machine.
>
>Remote Desktop has been working perfectly for the last two or three days
>but suddenly stopped doing so this morning, when I moved the
>server from my office to the client's in order to do some initial
>deployment testing. I was using it not 10 minutes before I left home
>but less than an hour later and ever since I have been getting "The client
>could not connect to the remote computer" messages when I try to
>connect. <snipped>

If telnet localhost 3389 fails on the box itself have you checked for an
entry for localhost in your Hosts file? From another machine can you:

telnet IP.Address.Of.Server 3389

and tell us what happens? If it fails but you are sure Remote Desktop is
enabled then it sounds like a firewall issue. Perhaps you enabled RRAS
(which has a basic firewall built-in) on this box? Perhaps the RDP-tcp
connection under tscc.msc is disabled (it would have a red X on it)?

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Does your client have a router between you and them and is 4125
forwarded to the router?

If you didn't install ISA... then it's not installed.

There is no Windows firewall in SBS it's the RRAS firewall.

So ... I'm getting from your post that it 'was' working while at your
shop but when you moved it to the client's it stopped working?

My guess is there's a router blocking port 4125.

Stroller wrote:
> Hi there,
>
> I have this week installed SBS 2003 for a customer of mine and was
> pleased to quickly find that I could connect using Remote Desktop
> Connection and work on the server from the comfort of my desktop machine.
>
> Remote Desktop has been working perfectly for the last two or three days
> but suddenly stopped doing so this morning, when I moved the server from
> my office to the client's in order to do some initial deployment
> testing. I was using it not 10 minutes before I left home but less than
> an hour later and ever since I have been getting "The client could not
> connect to the remote computer" messages when I try to connect.
>
> I'm connecting to the machine over the LAN and I can ping it, so the
> problem's not with NAT or port-forwarding or anything like that. In
> System Properties > Remote "Enable Remote Desktop on this computer" is
> checked and Terminal Services & its dependency RPC are both showing as
> started in Services [1] but Remote Desktop nevertheless seems not to be
> running. A port scan from another machine
> <http://rafb.net/paste/results/31nZOS31.nln.html> shows no response on
> port 3389 and running `telnet localhost 3389` on the server also fails.
>
> I don't believe that Windows firewall is running on this machine
> (Windows Firewall / ICS is disabled in Services) and I don't believe
> that ISA Server is installed, either - Start > All Programs does not not
> show the entry for Microsoft ISA Server mentioned in KB 828053.
>
> Can anyone advise the best way to trouble-shoot this further, please? I
> am not experienced with Terminal Services / Remote Desktop and so I'm
> consequently at my wits' end.
>
> Stroller.
>
>
>
>
>
>
>
>
>
>
> [1] I haven't deployed Windows server before and I find it curious that
> - although I'm a member of the Administrators & Domain Administrators
> groups - the "Start" and "Stop" buttons I've used in XP Home are
> greyed-out on this system.
>

You are using RWW right? you ran the connect to internet wizard and set
this up?

I personally don't like a port 3389 straight out to the web, but that's
just me.

Stroller wrote:
> Hi there,
>
> I have this week installed SBS 2003 for a customer of mine and was
> pleased to quickly find that I could connect using Remote Desktop
> Connection and work on the server from the comfort of my desktop machine.
>
> Remote Desktop has been working perfectly for the last two or three days
> but suddenly stopped doing so this morning, when I moved the server from
> my office to the client's in order to do some initial deployment
> testing. I was using it not 10 minutes before I left home but less than
> an hour later and ever since I have been getting "The client could not
> connect to the remote computer" messages when I try to connect.
>
> I'm connecting to the machine over the LAN and I can ping it, so the
> problem's not with NAT or port-forwarding or anything like that. In
> System Properties > Remote "Enable Remote Desktop on this computer" is
> checked and Terminal Services & its dependency RPC are both showing as
> started in Services [1] but Remote Desktop nevertheless seems not to be
> running. A port scan from another machine
> <http://rafb.net/paste/results/31nZOS31.nln.html> shows no response on
> port 3389 and running `telnet localhost 3389` on the server also fails.
>
> I don't believe that Windows firewall is running on this machine
> (Windows Firewall / ICS is disabled in Services) and I don't believe
> that ISA Server is installed, either - Start > All Programs does not not
> show the entry for Microsoft ISA Server mentioned in KB 828053.
>
> Can anyone advise the best way to trouble-shoot this further, please? I
> am not experienced with Terminal Services / Remote Desktop and so I'm
> consequently at my wits' end.
>
> Stroller.
>
>
>
>
>
>
>
>
>
>
> [1] I haven't deployed Windows server before and I find it curious that
> - although I'm a member of the Administrators & Domain Administrators
> groups - the "Start" and "Stop" buttons I've used in XP Home are
> greyed-out on this system.
>

Stroller? I just read where you haven't installed Windows server
before, so I want to make sure you have some foundations in place.

Okay first off did you install SBS 2003 with all the wizards?

If this is a premium box you only have ISA installed if you installed it
and this is a SBS "premium" version.

Next, did you run the connect to Internet wizard and open up the
settings you want? It's in the to do list that you get in Server
Management.

next.. you say XPHomes. You do realize that while XP homes can do pass
through authentication [a funky way where you set up workgroup name to
match the server domain name] they really and truly cannot join a domain
and thus 'tis better to have XP pros [in case you were not aware of that]

Let's step back a bit... how many network cards, what's your IP
addresses and you might want to just work with the SBS newsgroup rather
than all the other threads.

There are wizards and things unique to SBS.

Stroller wrote:
> Hi there,
>
> I have this week installed SBS 2003 for a customer of mine and was
> pleased to quickly find that I could connect using Remote Desktop
> Connection and work on the server from the comfort of my desktop machine.
>
> Remote Desktop has been working perfectly for the last two or three days
> but suddenly stopped doing so this morning, when I moved the server from
> my office to the client's in order to do some initial deployment
> testing. I was using it not 10 minutes before I left home but less than
> an hour later and ever since I have been getting "The client could not
> connect to the remote computer" messages when I try to connect.
>
> I'm connecting to the machine over the LAN and I can ping it, so the
> problem's not with NAT or port-forwarding or anything like that. In
> System Properties > Remote "Enable Remote Desktop on this computer" is
> checked and Terminal Services & its dependency RPC are both showing as
> started in Services [1] but Remote Desktop nevertheless seems not to be
> running. A port scan from another machine
> <http://rafb.net/paste/results/31nZOS31.nln.html> shows no response on
> port 3389 and running `telnet localhost 3389` on the server also fails.
>
> I don't believe that Windows firewall is running on this machine
> (Windows Firewall / ICS is disabled in Services) and I don't believe
> that ISA Server is installed, either - Start > All Programs does not not
> show the entry for Microsoft ISA Server mentioned in KB 828053.
>
> Can anyone advise the best way to trouble-shoot this further, please? I
> am not experienced with Terminal Services / Remote Desktop and so I'm
> consequently at my wits' end.
>
> Stroller.
>
>
>
>
>
>
>
>
>
>
> [1] I haven't deployed Windows server before and I find it curious that
> - although I'm a member of the Administrators & Domain Administrators
> groups - the "Start" and "Stop" buttons I've used in XP Home are
> greyed-out on this system.
>

On 2005-11-26 01:48:30 +0000, "Todd J Heron"
<todd_heron(delete)@hotmail.com> said:

> "Stroller" <stroller@bigfoot.com> wrote...
>> I have this week installed SBS 2003 for a customer of mine and was
>> pleased to quickly find that I could connect using Remote Desktop
>> Connection and work on the server from the comfort of my desktop machine.
>>
>> Remote Desktop has been working perfectly for the last two or three
>> days but suddenly stopped doing so this morning, when I moved the
>> server from my office to the client's in order to do some initial
>> deployment testing. I was using it not 10 minutes before I left home
>> but less than an hour later and ever since I have been getting "The
>> client could not connect to the remote computer" messages when I try to
>> connect. <snipped>
>
> If telnet localhost 3389 fails on the box itself have you checked for
> an entry for localhost in your Hosts file?

I can ping locahost, so that's fine.

> From another machine can you:
>
> telnet IP.Address.Of.Server 3389
> and tell us what happens?
>
> Sorry... I thought that was obvious from the ping & post-scan that I gave
No, I can't - I just get "connection refused".

If it fails but you are sure Remote Desktop is enabled then it sounds
like a firewall issue.
>
> Well, I'm sure I have the checkbox ticked. That doesn't give me faith
> that the Remote Desktop server is running, tho' - I should find out the
> name of the process.

Perhaps you enabled RRAS (which has a basic firewall built-in) on this box?
>
> If I go into Administrative Tools > Routing & Remote Access it shows as
> "stopped".

Perhaps the RDP-tcp connection under tscc.msc is disabled (it would
have a red X on it)?
>
> Ah, I think you may have hit the nail on the head - screenshots at
> <http://stuff.stroller.uk.eu.org/Windows/>.

On this machine the Connections folder of that Window is empty -
clicking at the Wizard suggests that I have to make a connection before
any user that wants to Remote Desktop in. But how come I didn't have to
do that before?

If this is necessary then there can't possibly be no default Terminal
Services connection, as it would be far too obscure for users who would
otherwise just tick the "Enable Remote Desktop" box in Control Panel >
System. Yet I can see how could have deleted the default connection,
having been unaware of this panel.

A question: if I use the Terminal Services Connection Wizard I see that
there are options to specify whether a connection controls or only
observes the user's desktop. Is it possible to have both setup? So that
I can log in as myself to administer the machine & interact with my own
desktop but later just log in to observe a user's screen (to check that
they're not surfing the web or writing personal letters at work, for
instance). Do I have to have different instances set up on different
ports, or could one select "interactive or observe" from the RDC client?

Thanks for your help,

Stroller.

On 2005-11-26 02:13:03 +0000, "Susan Bradley, CPA aka Ebitz - SBS Rocks
[MVP]" <sbradcpa@pacbell.net> said:

> Does your client have a router between you and them and is 4125
> forwarded to the router?

No. As I said:

>> I'm connecting to the machine over the LAN and I can ping it, so the
>> problem's not with NAT or port-forwarding or anything like that.

In the port-scan which I posted a link to you'll see that I'm using a
private address range & I can ping the machine.

> There is no Windows firewall in SBS it's the RRAS firewall.

Ok, I don't really know the difference, but I appreciate the
information for future reference. I don't plan on messing with RRAS on
a production machine, but maybe I'll install the trial version of SBS
on a machine at home to mess with.

> So ... I'm getting from your post that it 'was' working while at your
> shop but when you moved it to the client's it stopped working?

Yes, but...

> My guess is there's a router blocking port 4125.

....it can't be that because I moved my laptop with the server! And then
I moved the server back home with me after the stuff we were doing on
site today - the server is back on my LAN & I'm trying to connect from
my desktop machine.

Stroller.

On 2005-11-26 02:14:01 +0000, "Susan Bradley, CPA aka Ebitz - SBS Rocks
[MVP]" <sbradcpa@pacbell.net> said:

> You are using RWW right? you ran the connect to internet wizard and set
> this up?
> I personally don't like a port 3389 straight out to the web, but that's
> just me.

I see that RWW stands for "Remote Web Workplace" but I wasn't even
aware this was available as part of SBS - I'd got the impression that
the version of SBS 2003 that my client has bought is only licensed for
two concurrent terminal services logins, intended for sys-admins to
manage the box.

I'm not trying to access via the web, only via the regular Remote
Desktop Client application. Right now I only really want to admin the
server - which doesn't have a monitor attached - when I'm at the same
site as it. I'll have to look into something for remote access but I am
aware that port-forwarding will be necessary & I'd want to consider
security & encryption, too.

Stroller.

If you have SBS you've got RWW.

From your server do an IPconfig/all

Now do this from your laptop.

If either one is in a 169.x.x.x range..they are not talking and you've
lost the DHCP server.

I'm wondering if you had a router/dhcp handerouter at the office and now
at the client you don't.

RRAS comes as the standard SBS firewall... you don't 'install it'...
it's just there.

Again, how 'exactly' did you install this system?

RWW allows anyone with an XP workstation to have remote access back to
their desktop.

Stroller wrote:
> On 2005-11-26 02:14:01 +0000, "Susan Bradley, CPA aka Ebitz - SBS Rocks
> [MVP]" <sbradcpa@pacbell.net> said:
>
>> You are using RWW right? you ran the connect to internet wizard and
>> set this up?
>> I personally don't like a port 3389 straight out to the web, but
>> that's just me.
>
>
> I see that RWW stands for "Remote Web Workplace" but I wasn't even aware
> this was available as part of SBS - I'd got the impression that the
> version of SBS 2003 that my client has bought is only licensed for two
> concurrent terminal services logins, intended for sys-admins to manage
> the box.
>
> I'm not trying to access via the web, only via the regular Remote
> Desktop Client application. Right now I only really want to admin the
> server - which doesn't have a monitor attached - when I'm at the same
> site as it. I'll have to look into something for remote access but I am
> aware that port-forwarding will be necessary & I'd want to consider
> security & encryption, too.
>
> Stroller.
>
>

On 2005-11-26 04:30:31 +0000, "Susan Bradley, CPA aka Ebitz - SBS Rocks
[MVP]" <sbradcpa@pacbell.net> said:

> If you have SBS you've got RWW.

I see. From what I'm reading of RWW it looks fairly cute but of no real
benefit to me (since the site isn't using Exchange & I can't run
ActiveX controls on my Powerbook). I'd just like Remote Desktop
Connection to work, thanks.

> From your server do an IPconfig/all
> Now do this from your laptop.
> If either one is in a 169.x.x.x range..they are not talking and you've
> lost the DHCP server.

I've already stated that I can ping between the two machines & that
other network applications are unaffected.

> I'm wondering if you had a router/dhcp handerouter at the office and
> now at the client you don't.

I can configure IP addresses by hand if necessary - I do have enough
experience to check TCP/IP configuration.

> RRAS comes as the standard SBS firewall... you don't 'install it'...
> it's just there.

I think the relevant thing is that it's switched off, tho'. As far as
I'm aware it has never been enabled on this server this week.

> Again, how 'exactly' did you install this system?

I inserted CDs & booted from them. Could you be a little more specific, please?

RWW allows anyone with an XP workstation to have remote access back to
their desktop.
>
It seems to use ActiveX, however, which would rule out other platforms.
Microsoft make a perfectly good Remote Desktop Connection client for
Macintosh OS X which was working fine earlier this week; since all I
need is remote desktop, and none of the other features of RWW, I would
much rather focus on getting that working.

Stroller.