Re: Remote Desktop Connection

Ah, well that means it is enabled (forcibly) by group policy.

Check for running services, then proceed with Les's recommendations.

--
/kj
"Ralph" <Ralph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C4E9BB52-6E55-48C4-B0B3-CC614E6A7909@xxxxxxxxxxxxxxxx
Thanks KJ,

I have already checked that the "remote desktop" was enabled, however the
only weird thing is that the check is there, but the selection is grayed
out,
meaning you can't uncheck or check it???

Ralph


"kj" wrote:

I'd check that "remote desktop" was enabled under my computer |
properties |
Remote. It should be by default, but it may have been disabled by mistake
or
by an errant group policy.

Then I'd check to make sure the "Terminal Services" service was running
on
the server.

Then i'd jump into the process Les detailed.

--
/kj
"Ralph" <Ralph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1CF78380-01F0-448D-B1BB-78CE280ABDDE@xxxxxxxxxxxxxxxx
Thanks Les...I will try this on Saturday when I won't have to deal with
users. In the event that this is not the case any other suggestions?

Thanks,
Ralph R.

"Les Connor [SBS Community Member - SBS M" wrote:

Check to see what, if anything is listening on port 3389. On the SBS
server
......

Not commonly, Exchange can take port 3389 at the server, which is the
port
you need for TS (a.k.a RDP).


On the SBS 2003 server, run the netstat command below and notice the
output.


C:\>netstat -ano | find ":3389"


OUTPUT -> TCP 0.0.0.0:3389 0.0.0.0:0
LISTENING
612


The 612 at the end of the line is the PID of the process listening on
port
3389. This is the terminal services or RDP port.
Look it up in Task Manager to see which service is associated with it.
It
should be svchost.exe. If it is something else, stop that other
service
and then try to make an RDP connection to the server.


If it still doesn't work, you may have to set the offending service to
Manual and reboot again or add a dependency to the registry to prevent
it
from happening.


For example, let's say that I find that the MSExchangeSA service
(mad.exe)
has 3389.


To prevent the Exchange services from grabbing TCP Port 3389, add the
following
dependancy to the Exchange System Attendant service so that it will
start
after
terminal services starts


1. Start Regedt32


2. Go to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\DependOnS­­e
rvice
-- Double click and add TermService to the list of dependancy services


3. Exit Regedt32 and reboot the server - the Exchange System Attendant
service will
not start till the Terminal server service starts which should
eliminate
the problem.


Here's another method, for reserving a single port so it's not
dynamically
allocated. It might be a better solution:


1.. Start Registry Editor (Regedt32.exe).
2.. Locate the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters


3.. On the Edit menu, click Add Value, and then add the following
registry
value:
Value Name: ReservedPorts
Data Type: REG_MULTI_SZ
Value: xxxx-yyyy
The string uses the format xxxx-yyyy. It looks like this for just a
single
port: "3389-3389".


4.. Quit Registry Editor.






--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and
I'll
understand." - Confucius


"Ralph" <Ralph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4DA2CBF8-2B55-4403-AE40-0EA640A4E250@xxxxxxxxxxxxxxxx
Danny,

As I mentioned below I can RDP all the workstations both from RWW
and
from
the LAN. However, the problem is with the server, which for
whatever
reason
I cant RDP it from neither RWW or from the LAN. I receive the error
message
originaly posted.

Any Ideas???

"Danny" wrote:

Have you configure the Router?

Dann
"Ralph" <Ralph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AF0E279E-F370-43F1-B5F8-47DD352F707F@xxxxxxxxxxxxxxxx
Forgot to mention that I can RDP to any workstation from RWW.
This
is
only
happening when I attempt to RDP to the Server.

Thanks,
Ralph

"Ralph" wrote:

Hello,

I'm trying to establish a Remote Desktop Connection to my SBS
2003
server
and I'm getting the following error:

"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."

Any ideas???

Thanks,
Ralph











.

Relevant Pages

  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • RE: VBscript Error on SBS2k3
    ... DHCP Server turned of SonicWALL with VPN Pass through request for IP to ... the problem should be caused by the 4125 port. ... > | Accessories and Communications and Remote Desktop Connection? ... > | 2.In Internet Explorer on the workstation you are connecting from, ...
    (microsoft.public.windows.server.sbs)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Can not access Web and FTP sites from Internet
    ... your IP Configuration on the Server is correctly. ... Connecting To 12.208.215.87...Could not open connection to the host, ... 1> From the result, we can see the telnet failed, which means the router ... does not forward Port 443 to SBS Server. ...
    (microsoft.public.windows.server.sbs)
Loading