<div>
Turns out I am mistaken I was told by my network admin that telnet will not work because the name we are using as the SMTP Service's fully qualified domain name is a local to the machine. &nbsp;<br />
<br />
BUT we are not using servername.domain.com we are using givenname.domain.com. &nbsp; I am able to do a nslookup from the machine.<br />

</div>


Turns out I am mistaken I was told by my network admin that telnet will not work because the name we are using as the SMTP Service's fully qualified domain name is a local to the machine.  

BUT we are not using servername.domain.com we are using givenname.domain.com.   I am able to do a nslookup from the machine.


<div>
<div class="content wysiwyg-content">
We recently changed the SMTP Service's fully qualified domain name from server.domain.com to a mailservername.domain.com for an offsite server. &nbsp; Now our ASPEmail gets connection timed out and with CDO.Message there is no error displayed, but the user never receives a message. &nbsp;Once we switched the fully qualified domain name, the email script returns an error of 'connection timed out'. &nbsp;<br />
<br />
In IIS it says the mailservername.domain.com was resolved successfully. &nbsp;What else could be my problem?<br />
<br />
Any help would be greatly appriciated.
</div>
</div>


We recently changed the SMTP Service's fully qualified domain name from server.domain.com to a mailservername.domain.com for an offsite server.   Now our ASPEmail gets connection timed out and with CDO.Message there is no error displayed, but the user never receives a message.  Once we switched the fully qualified domain name, the email script returns an error of 'connection timed out'.  

In IIS it says the mailservername.domain.com was resolved successfully.  What else could be my problem?

Any help would be greatly appriciated.

Email script connection timed out after switching SMTP server name

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.