Exchange 2003 Unreachable Destination

I have an exchange 2003 server that i need to run for a few more days.  I have SBS2008 that I have just put on my network and have it running DHCP/DNS.  The new Exchange server seems to be working OK, but I haven't moved anyone over to it yet.

Seems like about the time I told SBS2008 to start handling DHCP that this problem started.  Could be unrelated, I dont know.  Right now I'm looking at 44 messages in the "unreachable" queue.

looked at several of them and tried NSlookup on the domains, i'm getting an answer just fine.  

Tried stopping/restarting all the exchange services, all that did was double the number of messages I had in the queue, the new ones now have no sender (I'm guessing they are copies of what was in there originally)

Oh, and I'm remoted into the 2003 server.  Every minute or so the interface is freezing, I'm getting some type of "disconnected" message, then it comes back on.  This is driving me crazy.


Who is Participating?
Glen KnightConnect With a Mentor Commented:
AHh OK, I didn't realise that.

Can you add the 2003 server in as a source server on the Send Connector in SBS2008 please?
Do you have a SMTP Connector configured on the 2003 server?

Can you also telnet from the SBS2008 server to the 2003 server on port 25?
Glen KnightCommented:
Is it an SBS2003 server? Did you configure it for a single NIC before you started migrating?

Can  you also check the Default SMTP Virtual Server configuration as per my article here:
chrisrbloomAuthor Commented:
No, old server is Windows 2003 standard with exchange on it.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Glen KnightCommented:
OK, can you check the Default SMTP Virtual Server as per my article.
chrisrbloomAuthor Commented:
dematzer - yes, that was a great article, but I checked everything and it seems to be OK.

We are receiving email fine.  Just can't send (all goes to the unreachable queue).
Glen KnightCommented:
can't send external or cannot send in between servers or both?
chrisrbloomAuthor Commented:
external only.  intra-office works fine.
Glen KnightCommented:
Ahh OK, that's OK then.

So on the SBS2008 server you have run the Internet Address and the Smart Host wizards in the SBS console?

can you telnet to on port 25
chrisrbloomAuthor Commented:
yes, I can telnet and connect on both servers.

Glen KnightCommented:
from the Exchange Management Shell on the SBS2008 server can you run the following:

Get-SendConnector | fl

Please post the results.
chrisrbloomAuthor Commented:
NOTE:  The server that i'm getting the halted queue is the SBS2003 machine.

here's the log of what I got from the SBS2008 machine:

         Welcome to the Exchange Management Shell!

 Full list of cmdlets:          get-command
 Only Exchange cmdlets:         get-excommand
 Cmdlets for a specific role:   get-help -role *UM* or *Mailbox*
 Get general help:              help
 Get help for a cmdlet:         help <cmdlet-name> or <cmdlet-name> -?
 Show quick reference guide:    quickref
 Exchange team blog:            get-exblog
 Show full output for a cmd:    <cmd> | format-list

Tip of the day #49:

Here's a handy tip for repeating a command a given number of times. Instead of w
riting a For loop, use the following syntax:

 1..10 | ForEach { "do something here" }

For example, the following command creates 10 new storage groups that have the n
ames sg1 through sg10 on the server TestServer:

 1..10 | ForEach { New-StorageGroup -Name "sg$_" -server TestServer }

[PS] C:\Windows\System32>get-sendconnector | fl

AddressSpaces                : {smtp:*;1}
AuthenticationCredential     :
Comment                      :
ConnectedDomains             : {}
ConnectionInactivityTimeOut  : 00:10:00
DNSRoutingEnabled            : True
DomainSecureEnabled          : False
Enabled                      : True
ForceHELO                    : False
Fqdn                         :
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : SERENITY
Identity                     : Windows SBS Internet Send SERENITY
IgnoreSTARTTLS               : False
IsScopedConnector            : False
IsSmtpConnector              : True
LinkedReceiveConnector       :
MaxMessageSize               : 10MB
Name                         : Windows SBS Internet Send SERENITY
Port                         : 25
ProtocolLoggingLevel         : None
RequireTLS                   : False
SmartHostAuthMechanism       : None
SmartHosts                   : {}
SmartHostsString             :
SourceIPAddress              :
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {SERENITY}
UseExternalDNSServersEnabled : False

[PS] C:\Windows\System32>
chrisrbloomAuthor Commented:
OK - I'm not exactly sure how to add the 2003 server into the 2008 server on the Send Connector (didn't see that anywhere).

Yes, I can telnet into the 2003 server from the 2008 server.

I dont have an SMTP connector on 2003 server, just a Default SMTP server.
Glen KnightCommented:
>>Yes, I can telnet into the 2003 server from the 2008 server.

Can you do the oposite?

In the Exchange Management Console under Organisation Configuration > Hub Transport under Send Connector you will find the Internet Send Connector, under the properties of this connector can you add the Exchange 2003 server.
chrisrbloomAuthor Commented:
I can't get the 2003 server added to the hub transport send connector in 2008.  I have to search for it and it doesn't come up.

I unfortunately attempted a reboot of the 2003 server and now I'm stuck in the update process before it reboots.

one thing to note, and I dont know if this makes any difference.  I have a cname in my dns "server" that points to my old 2003 server in the zone "tdc.local" - which is my domain.

Today when I did my internet connection wizard in 2008, I also called that one "server" and it set up a new forward lookup zone with server.tdc.local and added itself and the 2003 server as nameservers, and itself as a host.

could this be causing the problem?

Glen KnightCommented:
Sorry, my mistake, you won't be able to add the 2003 server.

It is more than likely DNS has a part to play in this.

When you telnet from the 2003 server to the 2008 server can you use the fully qualified domain name instead of just the hostname or IP.

And delete the CNAME record, that will just cause a loop.
chrisrbloomAuthor Commented:
I tried the following:

mail.tdc.local 25 - result - could not connect
server.tdc.local 25 - result - could not connect
serenity 25 - result - success
serenity.tdc.local - result - success.

Glen KnightCommented:
What is the actual name of the SBS2008 server?
chrisrbloomAuthor Commented:
chrisrbloomAuthor Commented:
scratch some of the dns things I've said.  I got mixed up between the .com and the .local

SBS2008 - Serenity
2003 Server - tdcsrvnew

I can connect to telnet the 2008 server from the 2003 server using the fully qualified domain name.
chrisrbloomAuthor Commented:
I'm not exactly sure what solved my problem, but I added an SMTP connector to the server and pointed at the Virtual SMTP server and pointed at itself as a smarthost.  Immediately, all emails delivered.

Thanks for your help.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.