[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 907
  • Last Modified:

Exchange Server 2003 -> Messages getting stuck in SMTP Connector Queue

Hi all. I need help from an Exchange expert. I am running MS Exchange 2003 (SP1) on a server running on Windows Server 2003 (SP1).  We have a small office (20 users) w/ all users connecting to Exchange via Outlook. Roughly two months ago I set up an SMTP connector to forward ALL outbound e-mail from our office to our web / internet e-mail hosting svc's (GoDaddy) outgoing mail server because we were having problems sending outbound e-mails to larger ISP based e-mail accounts such as aol.com, hotmail.com, optonline.net etc... The connector was working beautifully up until yesterday when all of a sudden messages started just accumulating in the connector’s queue and were not being sent. I checked and re-started all Exchange services, re-created the connector (multiple times), and have even re-booted the phsyical server itself twice. No luck. I also contacted GoDaddy to see if they were having any problems or made any changes on their end. They said all was fine on their end, w/ no changes made. Also, I can send e-mails directly from there server.

What’s weird is that if  I remove the connector, I can send outbound e-mails to addresses that don’t have all of the restrictions that the larger ISP accounts do. But if I put the connector in place, it seems that no messages get out to any external recipients whatsoever.

I should also note that we are not having any internet connectivity problems, nor have we made any changes whatsoever to our firewall settings or to the server running Exchange. It just seems to have started out of nowhere. I am not an Exchange expert so I may very well be overlooking something obvious. How can I resolve this??
0
mcascino
Asked:
mcascino
  • 7
  • 6
1 Solution
 
amaheshwariCommented:
Hi,

First go to your exchange server command prompt then telnet ip of smart host on port 25 by typing

telnet xxx.xxx.xxx.xxx 25 .Here xxx.xxx.xxx.xxx is you smart host IP in your exchange SMTP connector.

if you are not able to telnet then mail will not go.

0
 
mcascinoAuthor Commented:
Hi. Thank you for the quick response. I am able to telnet the smart host ok. What else should I check?
0
 
amaheshwariCommented:
Is there any error or event id for error in event viewer of your exchnage server.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
mcascinoAuthor Commented:
I wasn't seeing any yesterday, but I am now after re-booting the server earlier this morning. There are two errors:

Both are from source MSEXchangeAL:

First: Category LDAP Operations, "LDAP Bind was unsuccessful on directory s-remote.foxs.info for distinguished name ''. Directory returned error:[0x34] Unavailable."

Second: Category Service Control, "The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly."

However, all Exchange services that are set to start automatically on startup are running.
0
 
amaheshwariCommented:
Have you restarted your domain(AD) server.
0
 
amaheshwariCommented:
What are the event id that you are getting in event viewer?
0
 
mcascinoAuthor Commented:
Thanks for the link. I actually found that page yesterday but unfortunately it didn't help me.
0
 
mcascinoAuthor Commented:
I have not tried re-starting my server running AD. I will give that a shot now and see if that accomplishes anything. Also, the event IDs are as follows:

The first error (LDAP) has event ID 8026
The second error has event ID 8250
0
 
mcascinoAuthor Commented:
Ok. I just rebooted my DC server. After that finished, I re-booted the Exchange server again. The Exchange server once again reported the same two errors in Event Viewer that I indicated earlier. And the messages are still getting stuck in the SMTP queue. I also checked the event viewer on the DC server as well and see one error in the application section that I'm not sure what it is or if it even has any significance to my problem but here it is:

Source WMServer : Event ID 323 : "Plug-in 'WMS Anonymous User Authentication' on the server failed with the following information: Error code = 0x8007052e, Error text = 'Logon failure: unknown user name or bad password. '."


0
 
mcascinoAuthor Commented:
I should have checked this earlier, but apparently I have been getting those two errors in the Event viewer since long before this problem started to occur. Doing a little research revealed that these two errors are common during start up and shutdown do to a timing issue. So it does not appear they have anything to do with this problem.

Does anyone else have any other troubleshooting suggestions? I'm really in a bind here!!!!
0
 
mcascinoAuthor Commented:
The problem ended up being an authentication issue on GoDaddy's server. It is now fixed and e-mail is going through normally.

Thank you amaheshwari for your assistance.

Not sure what to do though as far as closing this question.
0
 
amaheshwariCommented:
Great to hear that your problem is resolved.
0
 
CetusMODCommented:
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now