RE: RDC Problem Driving me Mental

Hi Chris,

Thank you for posting in SBS newsgroup.

Regarding the issue, do you try to Remote Desktop to the SBS server from an
external client or internal client? Here I would assume that you are trying
to connect using the RDP client directly and the issue happens from your
internal clients.

As I know, this error may occur if another process that is running on the
SBS 2003 computer starts using TCP port 3389 before the Terminal Services
service starts. By default, TCP port 3389 is the port that Terminal
Services uses for its connections. If another process is using this port,
terminal server connections may fail.

The process that most frequently causes this problem is the Microsoft
Exchange System Attendant service (Mad.exe). That is because Microsoft
Exchange uses remote procedure call (RPC) dynamic port allocation. During
RPC dynamic port allocation, the RPC service assigns an RPC program a
random port number that is more than 1024. Occasionally, RPC may assign TCP
port 3389 to a program such as the Microsoft Exchange System Attendant
service.

To resolve the issue, modify the registry to exclude TCP port 3389 from the
RPC port range. To do this, follow these steps:

1. Start Registry Editor (Regedt32.exe).

2. Locate and then click to select the following registry sukey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc

3. Right click the RPC key and choose New->Key, name it "Internet" (without
the quotation marks).

4. Right click the Internet subkey and choose New->Multi-String Value, type
"Ports Data" (without the quotation marks) as the name and then set its
data to 3389.

5. Using the same method at step #4 to create the following 2 values:

Value Name: PortsInternetAvailable
Value Type: String
Value Data: N

Value Name: UseInternetPorts
Value Type: String
Value Data: Y

6. Restart the server for these changes to take effect.

If the issue still occurs, let's try the following steps:

1. Download and install the fport program to determine the process that is
bound to TCP port 3389. For information about how to do this, visit the
following Foundstone Web site:

http://www.foundstone.com/knowledge/free_tools.html

NOTE: Microsoft provides third-party contact information to help you find
technical support. This contact information may change without notice.
Microsoft does not guarantee the accuracy of this third-party contact
information. The third-party products that this article discusses are
manufactured by companies that are independent of Microsoft. Microsoft
makes no warranty, implied or otherwise, regarding the performance or
reliability of these products.

2. After you determine the process that is bound to TCP port 3389, make
sure that the corresponding process is not started before the Terminal
Services service. To do this, follow these steps.

Note: The following steps assume that the service that is bound to TCP port
3389 is the Microsoft Exchange System Attendant service. If another service
is bound to TCP port 3389, you must modify the following steps in this
section accordingly.

a. Click "Start", click "Run", type "regedt32" (without the quotation
marks) in the "Open" box, and then click "OK".

b. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA

c. In the right pane, double-click "DependOnService".

d. In the "Data" box, position the pointer under any existing values.

e. Type "termservice" (without the quotation marks), and then click "OK".

3. Restart the corresponding service (here is the Microsoft Exchange System
Attendant service which is the example). To do this, follow these steps:

a. Click "Start", point to "Programs", point to "Administrative Tools", and
then click "Services".

b. Right-click "Microsoft Exchange System Attendant", and then click
"Restart".

c. Click "Yes" when you are prompted to restart other services.

4. Make sure that Terminal Services is added to the list of dependency
services for the process that is bound to TCP port 3389. To do this, follow
these steps:

a. In the Services snap-in, double-click the process that is bound to TCP
port 3389. For example, double-click "Microsoft Exchange System Attendant".

b. Click the "Dependencies" tab.

c. Make sure that Terminal Services is displayed in the ""Microsoft
Exchange System Attendant" depends on these services" area.

d. Quit the Services snap-in.

For a similar issue that the port 4125 used by RWW is taken by another
process, you can take a look at the following KB. Its method can also be
used in this scenario:

886209 Users cannot connect to remote desktops by using the Windows Small
http://support.microsoft.com/?id=886209

I appreciate your time and look forward to hearing from you.

Best regards,

Crina Li (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: RDC Problem Driving me Mental
| thread-index: AcbHV8Vr044NCbMLQqeaBuCdJRiFnQ==
| X-WBNR-Posting-Host: 81.137.39.206
| From: =?Utf-8?B?Y21qa2VlZ2Fu?= <cmjkeegan@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: RDC Problem Driving me Mental
| Date: Thu, 24 Aug 2006 01:32:01 -0700
| Lines: 42
| Message-ID: <5575F725-7340-49E1-96AB-BC7D7566CFCD@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:292537
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| - sorry for the dupe post, too trigger happy -
|
| I have a problem with RDC either on it's own or through RWW.
|
| When I run the CIECW wizard and configure the router etc etc. it works
fine.
| UNTIL some time in the early hours of the morning when I either get cut
off
| -or- it will not connect at all.
|
| - I get the message that the computer may not be setup to accept new
| connections or may be too busy -
|
| Anyway I have been researching the problem and found that it may have
| something to do with another process listening on port 4125, apparently
this
| can sometimes be mad.exe.
|
| I followed the instructions to stop this from happening by altering the
| registry exactly as it says in the article, however on reboot Exchange
| attendant / routing etc all will not start, so I removed the registry
entries
| and all is well again.
|
| When I run $:\netstat -aon | find ":4125" there seems to be nothing
listing.
|
| When I run $\:netstat -aon |find ":3389" I find svchost is listening, but
| still is after I run CIECW so I don't see how it can be this.
|
| Does anyone have any other ideas?
|
| Third party software that is running on the same box: (sbs 2003)
| # GFI Mailessentials V12
| # Symantec Mail Security for MS Exchange
| # Symantec Client Security & Antivirus
|
| Nothing else.
|
| Any help much appreciated, this problem has been anoying me for months
now!
|
| Cheers
|
| Chris
|
| --
| IT & Network Coordinator
|

.

Relevant Pages

  • Event 1097 and 1030 on boot..
    ... be sure to adjust your firewalls for TCP port ... Windows 2000 uses NTP via UDP on port 123. ... Microsoft states it both ways in their ... >server 2000 server network, ...
    (microsoft.public.windows.server.setup)
  • RE: RDC Problem Driving me Mental
    ... SBS 2003 computer starts using TCP port 3389 before the Terminal Services ... The process that most frequently causes this problem is the Microsoft ... Exchange System Attendant service. ...
    (microsoft.public.windows.server.sbs)
  • Re: XP printer port addition scripting
    ... Copyright Microsoft Corporation 1996-2001. ... -d - delete the specified port ... -g - get configuration for a TCP port ... >I am using a script found on the script center. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Adding a printer/port Commandline - Auto installing printers/portd
    ... the r parameter is only the port name and that does not have to be the same ... -g - get configuration for a TCP port ... Windows Printing Team ... Search the Microsoft Knowledge Base here: ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Seagate Barracuda 160 GB IDE becomes corrupted. RMA?
    ... Operating System Microsoft Windows 2000 Professional ... System Memory 512 MB ... Communication Port Communications Port ... Driver Download http://www.viaarena.com/?PageID=2 ...
    (comp.sys.ibm.pc.hardware.storage)