RE: Cannot make either RWW or Remote Desktop Connection to server internally yet 3389 responds
- From: v-jaluo@xxxxxxxxxxxxxxxxxxxx ("Jacky Luo [MSFT]")
- Date: Thu, 01 Mar 2007 14:23:08 GMT
Hi Roger,
Thanks for posting here.
From the description, I understand the issue is that you can not RDP to theSBS server from internal and external network. If
I am off base, please don't hesitate to let me know.
Let us refer to the following steps to troubleshoot the issue:
Please try:
1. Open CMD prompt.
2. Key in the following command and hit Enter
telnet 127.0.0.1 3389
3. Let me know the outcome.
First of all, please make sure that the Remote Desktop has been configured
to listen on port 3389. You may refer to the
following Microsoft Knowledge Base article to check the port used by
terminal service:
How to change the listening port for Remote Desktop
http://support.microsoft.com/default.aspx?kbid=306759
After this, please use the utility TCPView to check whether terminal
service is listenting on this port:
http://www.sysinternals.com/ntw2k/source/tcpview.shtml
Meanwhile, you may also run "netstat -na|findstr 3389" on the server. Which
interfaces are 3389 port listening on?
Scenario 1
----------
If the 3389 port is occupied by another services or application, this
problem may occur. Based on my experience, 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. As the
server is running Exchange, this may be the root
cause for this issue.
To trouble shoot this problem efficiently, please refer to the following
Microsoft Knowledge Base article:
Users cannot connect to remote desktops by using the Windows Small Business
Server 2003 Remote Web Workplace
http://support.microsoft.com/default.aspx?scid=kb;EN-US;886209
Meanwhile, you can also refer to the above KB306759 to change the listening
port of the terminal service to and then refer to
the following Microsoft Knowledge Base article to see whether you can
remote desktop through this port:
http://support.microsoft.com/kb/304304/
Scenario 2
----------
If no services are listening on the 3389 port and you have not changed the
listening port, some components of terminal
services may be corrupt when you uninstalled the terminal services. Please
ensure that you have checked the "Enable Remote
Desktop on this computer" option in the System Properties dialog. In
addition, please check the "Device\Video0" registry key.
This problem may occur when the Device\Video0 registry key is missing. If
this registry value is corrupt, the RDP-Tcp will be
displayed as "Down" state.
Remote Desktop Protocol Clients Cannot Connect to Terminal Services Server
http://support.microsoft.com/?id=270588
If this problem continues, please help me collect some information so that
I can perform further research on this issue:
1. Is the server listening on the 3389 port?
2. Download the tstst.exe attachment to the c: drive and then run the
following command on the problematic server to check
and gather Terminal Services configuration information:
- Click Start -> Run, type "cmd" in the text box, and click OK.
- Type the following command to run the tool:
C:\tstst.exe > c:\tstst.txt
Please send the tstst.txt file to me. I will stand by for your update.
3.Perform the following steps to collect the MPSReport of the problematic
server:
Download the MPSRPT_NETWORK.EXE file from the following website:
http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en
2)Double-click to run the MPSRPT_NETWORK.EXE file and wait for it to
complete.
3)Send me the .cab file generated in the following folder:
systemroot%\MPSReports\Setup\<Report Type>\Cab
4.Please export the [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Control\Terminal
Server] registry key to a file and then send it to
me. As our email system blocks any attachments with .reg file extension,
please zip this file before you send it to me.
Please compress all the files and send to me at v-jaluo@xxxxxxxxxxxxx
I appreciate your time. I am happy to be of assistance and look forward to
your reply.
Best regards,
Jacky Luo (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================
.
- Prev by Date: Re: Can I log how long a client computer is locked?
- Next by Date: Re: Problem with Activesync by cable on WM5 device (wireless is fine)
- Previous by thread: Re: Cannot make either RWW or Remote Desktop Connection to server internally yet 3389 responds
- Next by thread: Re: Remote Web Workplace Issues-Please help!
- Index(es):
Relevant Pages
|
