Outbound messages stopped sending

[BiJae]

I have a problem where my outgoing messages are sitting in the queue and not going anywhere. The server is able to receive messages but not send.

I'm fairly new to exchange and Microsoft Servers in general. I've been working on getting some RPC errors fixed over the last couple weeks. This has required some DNS maintenance. All that was done last week and messages were still flowing then. They stopped at 11:40 am on Monday, Dec 4. I'm not sure what changed and could use some help diagnosing/fixing the problem.

Any suggestions on where to start? I've been reading about exchange configuration setups and I think this one is configured correctly. I haven't changed things in Exchange Management.

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[Zelandakh]

What does it say in the SMTP queue? What about the event log?

 

[BiJae]

I've expanded /Administrative Groups/Servers/Server/Queues and see that there is an entry with SMTP Mailbox Store(TCUD-EX1) using protocol X400 , Source EXHCANGE MTA, that shows active.

There is an entry for SIG using protocol SMTP that is Not Avaiable (SIG appears to be a SMTP Virtual Server).

Everything else appears as such:

Name                                Protocol    Source
Test - domain.com (SMTP Conncetor)  SMTP        Default SMTP Virtual Server

State  Number of messages
Ready  X

The event viewer has a lot of error messages that state the following:

Event Type:	Error
Event Source:	MSExchangeFBPublish
Event Category:	General 
Event ID:	8213
Date:		12/3/2006
Time:		9:47:54 PM
User:		N/A
Computer:	TCUD-EX1
Description:
System Attendant Service failed to create session for virtual machine TCUD-EX1. The error number is 0xc007052e. 

For more information, click [URL unfurl="true"]http://www.microsoft.com/contentredirect.asp.[/URL]

These messages go back well before the start of the problem.

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[BiJae]

I did a port query on the server from itself and from another server on the network both responded LISTENING. Next I ran a port query on the server that is configured in the source "Default SMTP Virtual Server" DNS Settings.

C:\>portqry -n tcud-ex1 -e 25

Querying target system called:

 tcud-ex1

Attempting to resolve name to IP address...

Name resolved to 192.168.20.106


TCP port 25 (smtp service): LISTENING

Data returned from port:
220 tcud-EX1.tcud.state.tx.us Microsoft ESMTP MAIL Service, Version: 6.0.3790.18
30 ready at  Wed, 6 Dec 2006 11:46:10 -0600


C:\>portqry -n merlin.texan.state.tx.us -e 25

Querying target system called:

 merlin.texan.state.tx.us

Attempting to resolve name to IP address...

Name resolved to 168.39.1.19


TCP port 25 (smtp service): LISTENING

Port did not return extended data - request timed out


C:\>

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart

 

[BiJae]

I found the problem, it was with the next hop computer. As the test above indicated the server on the other end of the DNS server was not returning data. I changed the IP address of the DNS server that the SMTP server was configured and everything started moving again.

http://www.bijae.net

"If the only prayer you said in
your whole life was, 'thank you,'
that would suffice."
-- Meister Eckhart