Follow these steps to install telnet on Windows Vista:

By default, Vista doesn’t install the Telnet client. The client is for text-based communication with remote systems. You can install it by following these steps:

1. Open your Start menu and choose the Control Panel.

2. Choose “Programs and Features.”

3. Choose “Turn Windows features on or off.”

4. Select the Telnet Client option and click “OK.”

5. You’ll be prompted confirm the installation of the Telnet feature. You should now be able to run Telnet from the command prompt or a run dialog (I.E. Windows Key + R -> Cmd -> telnet / Windows Key + R -> Telnet).

SUMMARY

This article describes how to telnet to port 25 on a computer that runs Simple Mail Transfer Protocol (SMTP) services to troubleshoot SMTP communication problems. The information in this article, including error messages, only applies to issues when attempting to resolve SMTP communication issues with Microsoft Exchange-based servers and is not intended for general troubleshooting purposes.

You can use the following troubleshooting steps that are appropriate for the type of problem that you are experiencing. For example, if you are having problems sending over SMTP between two of your Microsoft Exchange 2000 Server servers, you can test the SMTP connectivity by using Telnet on the sending server to connect to port 25 on the destination server. By default, SMTP listens on port 25. Alternatively, if you are having problems receiving SMTP mail from the Internet, you can follow the steps that are listed in this article to test connectivity to your SMTP server from a host that resides on the Internet and that is not on your network.

NOTE: This article only outlines information for a connectivity test for messaging with Exchange Server, if you are not able to connect to the Exchange Server, please search the KB for other symptoms or error messages you are experiencing. For additional information on troubleshooting Exchange transport issues, please refer to the following article in the Microsoft knowledgebase:

257265 (http://support.microsoft.com/kb/257265/) General troubleshooting for transport issues in Exchange 2000 Server and in Exchange Server 2003

Back to the top

MORE INFORMATION

There are several different variations of SMTP in the Microsoft product line. The Microsoft Windows product line has an SMTP service that is included with Internet Information Services (IIS), and in Microsoft Windows NT Server 4.0, the SMTP service was included in the Option Pack. In more recent versions of Windows, IIS has been integrated in the operating system, and you can add IIS by using Add or Remove Programs in Control Panel. Additionally, Exchange 2000 and Microsoft Exchange Server 2003 use the existing SMTP service from IIS with additional features. Microsoft Exchange Server versions 4.0, 5.0, and 5.5 all come with their own versions of SMTP in the form of the Internet Mail Connector (IMC) or Internet Mail Service (IMS).

Note In Exchange 5.0 and later, the Internet Mail Connector (IMC) is renamed the Internet Mail Service.

Before you start the Telnet session, you must have the full SMTP e-mail address of the destination user who you want to send this test message to. This e-mail address must be in the following format:

User@Site.Domain.com

You must also have the fully qualified domain name (FQDN) or the IP address of the server computer that is running the SMTP services (for example, 10.120.159.1). If the servers are in your organization, you may already have this information. If the servers are external, the easiest way to find this information is to use Nslookup.exe to find the DNS records that contain this information. For additional information about NSlookup, click the following article number to view the article in the Microsoft Knowledge Base:

200525 (http://support.microsoft.com/kb/200525/) Using NSlookup.exe

For additional information about obtaining Internet Mail Exchanger records, click the following article number to view the article in the Microsoft Knowledge Base:

203204 (http://support.microsoft.com/kb/203204/) XFOR: How to Obtain Internet Mail Exchanger Records

Make sure that SMTP has started on the server that runs the SMTP service. To test if SMTP has started, you can run the basic tests that are listed in this article and verify that you receive the 220 response from the remote server. This also verifies that SMTP is running.

Notes

•	Some Telnet applications require you to turn on local echoing to see the commands that you are typing. To do this while in a Microsoft Telnet session, type set local_echo at the command prompt.
•	In Microsoft Windows XP, type set localecho instead of set local_echo.

Back to the top

Basic Testing

Follow these steps to make sure that the host computer and the remote SMTP server can communicate. If you receive the following error message after you type any one of the following commands, the SMTP server does not recognize what you typed because of a syntax error or an erroneous command:

500 Command not recognized

Check the command and type it again or verify that you are communicating directly to a Microsoft SMTP server.

Note Microsoft Telnet does not permit you to use the Backspace key. If you make a mistake when you type a command, you must press ENTER, and then start a new command.

In the following steps, you run Telnet from the command line. To open a command line, Click Start, click Run, type cmd in the Open box, and then click OK.

1.	You can start a Telnet session by using the Telnet command in the following format: Note Press ENTER after you type each line. telnet servername portnumber For example, type: telnet mail.contoso.com 25 Note You can replace servername with the IP address or the FQDN of the SMTP server that you want to connect to. Remember to press ENTER after each command. If the command works, you receive a response from the SMTP server that is similar to the following: 220 site.contoso.com Microsoft Exchange Internet Mail Connector <version number of the IMC> Note There are different versions of Microsoft SMTP or third party SMTP servers, and you may receive different responses from the receiving server. What is important is that you receive the 220 response with the FQDN of the server and the version of SMTP. Additionally, all versions of Microsoft SMTP include the term “Microsoft” in the 220 response.
2.	Start communication by typing the following command: EHLO test.com Note You can use the HELO command, but EHLO is a verb that exists in the Extended SMTP verb set that is supported in all current Microsoft implementations of SMTP. It is a good idea to use EHLO, unless you believe that there is a problem with the Extended SMTP Verbs. If the command is successful, you receive the following response: 250 OK
3.	Type the following command to tell the receiving SMTP server who the message is from: MAIL FROM:Admin@test.com Note This address can be any SMTP address that you want, but it is a good idea to consider the following issues: a. Some SMTP mail systems filter messages based on the MAIL FROM: address and may not permit certain IP addresses to connect or may not permit the IP address to send e-mail to the SMTP mail system if the connecting IP address does not match the domain where the SMTP mail system resides. In this example, that domain is test.com. b. If you do not use a valid e-mail address when you send a message, you cannot determine if the message had a delivery problem, because the non-delivery report (NDR) cannot reach an IP address that is not valid. If you use a valid e-mail address, you receive the following response from the SMTP server: 250 OK - MAIL FROM Admin@test.com
4.	Type the following command to tell the receiving SMTP server whom the message is to. Note It is a good idea to always use a valid recipient SMTP address in the domain that you are sending to. For example, if you are sending to john@domain.com, you must be certain that john@domain.com exists in the domain. Otherwise, you will receive an NDR. Type the following command with the SMTP address of the person you want to send to: RCPT TO: User@Domain.Com You receive the following response: 250 OK - Recipient User@ Domain.Com
5.	Type the following command to tell the SMTP server that you are ready to send data: DATA You receive the following response: 354 Send data. End with CRLF.CRLF
6.	You are now ready to start typing the 822/2822 section of the message. The user will see this part of the message in their inbox. Type the following command to add a subject line: Subject: test message Press ENTER two times. You do not receive a response from this command. Note The two ENTER commands comply with Request for Comments (RFC) 822 and 2822. 822 commands must be followed by a blank line.
7.	Type the following command to add message body text: This is a test message you will not see a response from this command.
8.	Type a period (.) at the next blank line, and then press ENTER. You receive the following response: 250 OK
9.	Close the connection by typing the following command: QUIT You receive the following response: 221 closing connection
10.	Verify that the recipient received the message that you sent. If any error event messages appear in the application event log, or if there are problems receiving the message, check the configuration or the communication to the host.

Back to the top

Advanced Testing

In addition to the basic testing steps that are listed in this article, you can use a delivery receipt to test mail in both directions. You can use this method to verify that the SMTP server can accept an inbound connection and generate a delivery receipt back to the sender to test outbound connectivity of the SMTP server.

To request a delivery receipt for the test message, see step 4 in the “Basic Testing” section of this article to make sure that the information provided is a valid e-mail address that can receive the delivery receipt. Then in step 5 in the “Basic Testing” section of this article, type the following command in the Telnet session:

RCPT TO:User@Site.Domain.Com notify=success,failure

Back to the top

---

APPLIES TO

•	Microsoft Exchange Server 2003 Standard Edition
•	Microsoft Exchange Server 2003 Enterprise Edition
•	Microsoft Exchange 2000 Server Standard Edition
•	Microsoft Exchange Server 5.5 Standard Edition
•	Microsoft Exchange Server 5.0 Standard Edition
•	Microsoft Exchange Server 4.0 Standard Edition
•	Microsoft Internet Information Services 6.0
•	Microsoft Internet Information Services 5.0
•	Microsoft Internet Information Server 4.0

Microsoft’s description:

The Display tab also lists your device’s available memory and can tell you if your video driver has passed Microsoft’s Windows Hardware Quality Labs (WHQL) testing regimen by checking whether the WHQL Logo’d is set to Yes or No.

Note Dxdiag.exe cannot report memory that is in use at the time that it starts. Therefore, it is not uncommon to see less memory reported than your video card actually has.

DxDiag description on Wikipedia:

DxDiag (“DirectX Diagnostics”) is a utility designed to display the specifications of the user’s hardware, as well as to test DirectX software, including sound and video. DxDiag was first released on August 7, 1998 as part of DirectX 6.0 and the successor to DXInfo. To open this program type dxdiag in the Windows Vista start menu search bar or the Run command (Start->Run…) in any other version of Microsoft Windows (see image).

DxDiag is a diagnostics tool used to test DirectX functionality and troubleshoot video- or sound-related hardware problems. DirectX Diagnostic can save text files with the scan results. These files are often posted in tech forums or attached to support emails in order to give support personnel a better idea of the PC the requester is using in case the error is due to a hardware failure or incompatibility.

DxDiag by default located in %SystemRoot%\System32.^[1] In Windows Vista, DxDiag only shows information; it is no longer possible to test the hardware and the various DirectX components. ^[2]

Functions

The System tab displays the current DirectX version, the computer’s hostname, the operating system’s version, information on the system BIOS, and other data. The DirectX Files tab displays information about the versions of specific DirectX system files, which are mostly portable executables or dynamic-link libraries (DLLs).

DxDiag displays information about the current display settings and the video hardware on the Display tab. If the computer has more than one monitor, then DxDiag will display a separate tab for each monitor. This tab can disable DirectDraw, Direct3D, and/or AGP Texture Acceleration for troubleshooting purposes. If the installed display driver has passed Windows Hardware Quality Labs testing, DxDiag will display this result on the right side of the window.

The Music tab displays information about the computer’s MIDI settings, and lists different music-related software and hardware on your computer. The Input tab, displays information about input devices installed in the computer such as keyboards and mice. It will also attempt to detect problems with these devices. DxDiag displays information about the installed DirectPlay Service Provider. It is possible to set up a very basic chat room using the network diagnostic and inputting various IP addresses.