Systech Solutions LTD.

Issue:

 Resolution:

Hi,
I was facing the same problem and solved it like this: on the server (remote dektop) do the following
C:\Program Files\Microsoft Dynamics CRM\Tools >Microsoft.Crm.Tools.WRPCKeyRenewal.exe /R

This should be done by CRM on a scheduled base, but for some reason that was failing on my server. Executing it manually solved the issue. I hope this might help some other people.

How to change the listening port for Remote Desktop

View products that this article applies to.

This article was previously published under Q306759

INTRODUCTION

This article describes how to change the port that Remote Desktop listens on.

Note The Remote Desktop Connection Client for the Mac supports only port 3389. 3389 is the default port.

MORE INFORMATION

You can use the Remote Desktop feature in Microsoft Windows XP Professional to connect to your computer from another remote computer.

Warning The Remote Assistance feature in Microsoft Windows XP may not work correctly if you change the listening port.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

307711  Remote Assistance invitation file does not contain correct port number

To change the port that Remote Desktop listens on, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756  How to back up and restore the registry in Windows

1. Start Registry Editor.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
3. On the Edit menu, click Modify, and then click Decimal.
4. Type the new port number, and then click OK.
5. Quit Registry Editor.

Note When you try to connect to this computer by using the Remote Desktop connection, you must type the new port.

304304  How to configure the Remote Desktop client to connect to a specific port when you use Windows XP

APPLIES TO

• Microsoft Windows XP Professional
• Microsoft Windows XP Professional x64 Edition
• Microsoft Remote Desktop Connection Client for Windows 1.0
• Microsoft Windows Remote Desktop Connection for Macintosh

Back to the top

Pasted from <http://support.microsoft.com/kb/306759>

ASP.NET Configuration

How to: Install and Configure SMTP Virtual Servers in IIS 6.0

In order to send e-mail from an ASP.NET Web application, you must have the Simple Mail Transfer Protocol (SMTP) service of Internet Information Services (IIS) installed and configured on your server. The IIS SMTP service is a simple component for forwarding e-mail messages to an SMTP server for delivery.

 Installing the SMTP Service

The SMTP service is not installed by default with IIS. You must install the SMTP service using Control Panel. Installing the SMTP service creates a default SMTP configuration that you can then customize by using IIS Manager.

To install the SMTP service on IIS 6.0

1. On the Start menu, click Control Panel, double-click Add or Remove Programs, and then click Add/Remove Windows Components.
2. In the Components list, click Application Server, and then click Details.
3. In the Subcomponents of Application Server list, click Internet Information Services (IIS), and then click Details.
4. In the Subcomponents of Internet Information Services (IIS) list, select the SMTP Service check box, and then click OK.
5. Click Next. If you are prompted for the Windows CD or the network install path, follow the instructions.
6. Click Finish.

When you install the SMTP service, a default SMTP server configuration is created with a message store in C:\Inetpub\Mailroot.

When you are setting up the SMTP service, you can configure global settings for the SMTP service, as well as settings for individual components of the virtual server. The IIS SMTP service is a relay agent only. E-mail messages are forwarded to an SMTP server for delivery.

 Configuring the SMTP Virtual Server

Installing the SMTP service will create a new node in IIS Manager. In order to configure the SMTP virtual server, you must start IIS Manager. For more information, see the topic “SMTP Administration” in the IIS Operations Guide.

Important Note:
You must be logged on as a member of the Administrators group on the local computer to perform the following procedure (or procedures), or you must have been delegated the appropriate authority.

To start IIS Manager from the Run dialog box

1. On the Start menu, click Run.
2. In the Open box, type inetmgr and then click OK.

To start IIS Manager from the Administrative Services console

1. On the Start menu, click Run. In the Run text box, type control panel, and then click OK.
2. In the Control Panel window, click Administrative Tools.
3. In the Administrative Tools window, click Internet Information Services.

Default Settings

The default SMTP virtual server has the following default settings. If you create a new virtual server, you can configure default settings using the New Virtual Server Wizard.

• Name: The name of the virtual server that appears in IIS Manager.You can change the name of the virtual server in IIS Manager. Simply right-click the virtual server and then click Rename.
• IP address/TCP port: All unassigned/25.You can use the General tab in the SMTP virtual server properties dialog box to change this setting. If you change this setting, you must specify an IP address and TCP port combination that is not being used by another SMTP virtual server. TCP port 25 is both the default TCP port and the recommended TCP port. More than one virtual server can use the same TCP port, but they must be configured with different IP addresses. If you do not set a unique IP address and TCP port combination, the SMTP virtual server will not start.

Default domain: The domain name that is listed on the Computer Name tab in System Properties.The default domain is used to stamp messages from addresses that do not have a domain. An SMTP virtual server can have only one default domain, and it cannot be deleted. To change the name of the default domain in IIS Manager, double-click the virtual server, and then double-click Domains. Right-click the local (or default) domain, and then click Rename.

• Home directory: C:\Inetpub\Mailroot.The home directory is the root of your SMTP content directories, and it must be local to the computer on which the SMTP service runs.

 See Also

Tasks

How to: Create and Configure Local ASP.NET Web Sites in IIS 6.0

Troubleshooting email, the Telnet way

Email is used daily by everyone from the top executives to the 5 year olds sending messages to their friends.  But what about tools to test and resolve issues?  Email tends to be weaker when it comes to troubleshooting tools.

One tool I’ll briefly plug is SMTPDiag from Microsoft.  Released in the fall of 2004 it’s a great tool for any email troubleshooting.

Today I want to cover a more basic, yet in some ways, more powerful email troubleshooting tool.  Many people do not realize that you can easily and quickly send a test message using telnet, a tool available with most operating systems.

Using telnet, you can talk to a sending mail server directly as if you were an email program.  Don’t stop reading yet because it sounds difficult, it isn’t, and it can benefit you more than you realize!  Whether you’re an administrator that manages mail servers, a technical person that likes to keep up on cool things, or you’re a home user wanting to find out why your email message didn’t send, this simple walk-through is for you.

Now, why would you want to talk directly to the mail server?  The reasons are endless but let’s give an example.  Let’s say that all of a sudden your mail server stopped sending email and you’re not sure why.  Is it your sending mail server, your email program, your firewall, your ISP or what?  This test will give you some solid clues how to isolate the issue.

There is one thing to keep in mind when using telnet.  A backspace might appear to work in your telnet session but the mail server won’t accept it as a backspace.  So, if you type the email address or command wrong, don’t use the backspace to correct it.  You should press enter and try again.  You may need to quit and start again.  You can see the affect of a backspace by using the backspace key in the body of the email and seeing what it looks like when you receive the email.

Let’s dive in.  Note, if you want to skim and just use the actual commands, just type in the words in red. 

Open a blank telnet interface on your computer and connect to the mail server over port 25.  In Windows, you can do this from the command prompt by typing telnet smtp.mailserver.com 25

At this point you should see a small bit of information at the top of the telnet screen.  This is the mail server’s initial welcome.  If you get a timeout and you are not trying to use your ISP’s mail server, there is a chance that your ISP has blocked port 25.  Some mail servers also listen on alternate ports, for example 587, so you can try connecting using 587 instead of 25.  If neither work and you are sure your internet connection is working, you should contact your ISP to try to get the block removed.  Alternately you may be forced to use your ISP for all outgoing email.

Now, let’s start talking to the server.  Type helo me

Set the From and To:
Mail from: myaddress@orcsweb.com
Rcpt to: your...@orcsweb.com

At this point, the mail server should say if the recipient was approved or not.  Some mail servers know at this point if it will allow it, some will accept the message and reject it later if it is invalid.  For the most part you can tell already if there is an issue with the sending or receiving email address.

Now we are ready to start into the Data part.  Here we can keep it plain and simple and start typing the body, or we can add some friendly headers to make the email look better.  I will include the friendly part at the top, but during testing it is not required.

First type: Data and press enter

Next add the headers and body:

From: “Scott Forsyth” <myaddress@orcsweb.com>
To: “Your name” <youraddress@orcsweb.com>
Subject: This is a test message sent from telnet

Here is where the body goes.  Notice the one blank line between the headers and the body of the email. 

Again, the three headers aren’t required.  They can be in any order and they aren’t case sensitive either.  You can also get away without any headers or with just the email address there like so:

From: myaddress@orcsweb.com.

To end the Data / body, there needs to be a line with only a . (dot) on it, and then press enter.  Like so:

.

That’s it.  You should receive a brief status about the message and then you can exit by typing Quit.  Your message should be sent. 

This is surprisingly easy.  Just remember the key details.  Some mail servers don’t require the helo me but it is a good habit to always enter it.  For a quick test for troubleshooting, here is a bare bones example:

===========
telnet smtp.mailserver.com 25

helo me
mail from:myad...@orcsweb.com
rcpt to:your...@orcsweb.com
data
This is a test
.
===========

Here is yet another example with an image to show the whole process.

That is sufficient to send a test message on most mail servers.  Telnet is a powerful tool for testing email and really comes in handy for isolating mail related issues. 

Windows Server Hacks: Remotely Enable Remote Desktop by Mitch Tulloch, author of Windows Server Hacks 05/04/2004

Remote Desktop is a cool feature of Windows Server 2003 that lets you remotely log on to and work at a machine as if you were seated at the local console (in Windows 2000 Advanced Server, this feature was called Terminal Services in Remote Administration Mode). Remote Desktop can be a lifesaver for fixing problems on servers at remote sites, but what if you forgot to enable the feature before you shipped the server out to Kalamazoo? Enabling Remote Desktop is easy if the server is in front of you: just log on as an administrator, open System in Control Panel, select the Remote tab, and under Remote Desktop select the checkbox labeled “Allow users to connect remotely to this computer.” Unfortunately, you can’t use the System utility to enable Remote Desktop on a remote machine, though you can access some properties pages of System using Computer Management by first connecting the console to a remote computer, then right-clicking on the root node and selecting Properties. Unfortunately, as you can see in Figure 1 below, the Remote tab is not available when you access System properties this way on a remote machine (here named SRV220).

Figure 1. System properties for a remote machine does not have Remote tab.

Fortunately, there’s a workaround. Sit down at your desk and log on to your Windows XP workstation using your administrator credentials and start Registry Editor by Start –> Run –> regedit –> OK. Then select the Connect Network Registry option under the File menu (Figure 2).

Figure 2. Connecting to the Registry on a remote machine.

This opens the Select Computer search box. Either browse Active Directory to locate the remote server, or type its name in the textbox (Figure 3).

Figure 3. Connecting to the Registry on a remote server named SRV220.

Click OK and a node will be displayed in Registry Editor for the remote machine (Figure 4).

Figure 4. HKLM and HKU hives on SRV220.

Now browse HKLM on SRV to find the following Registry key (Figure 5).

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

Figure 5. Registry key for Terminal Server on remote machine.

Under the Terminal Server key, you’ll find a REG_DWORD value named fDenyTSConnection. Double-click on that value to open the Edit DWORD Value box and change the value data from 1 (Remote Desktop disabled) to 0 (Remote Desktop enabled), as in Figure 6 below.

Figure 6. Set fDenyTSConnections to 0 to enable Remote Desktop on SRV220.

The remote machine needs to be rebooted for the change to take effect, so open a command prompt and type the following command:

shutdown -m \\srv220 -r

After the remote machine reboots, Remote Desktop should be enabled on it. To test this from your workstation, open Start –> All Programs –> Accessories –> Communications –> Remote Desktop Connection, enter the name of the remote server in the Remote Desktop Connection logon box, supply your administrator password when prompted, and you’re in.

Mitch Tulloch is the author of Windows 2000 Administration in a Nutshell, Windows Server 2003 in a Nutshell, and Windows Server Hacks.