Re: Remote Desktop Issue
- From: "Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 20 Nov 2007 18:05:00 -0500
I assume you're talking about Remote Web Workplace (RWW). Yes, not having
4125 open is most probably the problem. It's required for RWW.
--
Merv Porter [SBS-MVP]
============================
"storlogic" <storlogic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B703607A-2373-471A-B6ED-9BDC611193E0@xxxxxxxxxxxxxxxx
When I connect to my SBS 2003 (R2) server via ip/remote, I cannot connect
to
the server or client computers. I'm not worried about the server because
I
can connect to it via RDC. However, I would like to have some of the
employees in the company connect to their desktop when they are out of the
office.
When I first access the server through the ip/remote, I login as a user
(Administrator) and then I'm prompted if I want to connect to the server
or
client computers. When I select client computers, I see all of the client
computers listed in a dropdown listbox, but when I select one and then
click
"Connect" I get the following error:
"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. Please try connecting again later. If the problem continues
to
occur, contact your administrator."
I have a hardware firewall (Watchguard). I don't have port 4125 open. I
know I should, but haven't had a chance to do so yet. Is this the reason?
.
- Prev by Date: RE: Event ID 447
- Next by Date: Re: slow login to server
- Previous by thread: Exchange email problem for one client
- Next by thread: Re: Remote Desktop Issue
- Index(es):
Relevant Pages
|
Loading
