Posts: 1
Joined: 6.Aug.2004
From: UK
Status: offline
Hi
Im running Exchange 2003, and am having trouble gettin mail to a few domins, others are working fine. The error reported on the SMTP Connector is "The connection was dropped by the remote host." HELP!
Incoming mail seems to be ok just outgoing?
PS Were on BT Broadband connection.. And it doesn't seem to make any difference whether we use a smarthost to route the mail or use DNS?
Posts: 96
Joined: 30.Jun.2004
From: Birmingham, United Kingdom
Status: offline
Another person in the UK suffering from not sending mails out?
We use Demon-UK and we cant get our mails to go out unless we restart the server then the queue clears.
I get the exact same error "connection dropped by remote host".
Exchange gets a "GetNextHop=0ms" error in full logging mode! It stops being able to trace the hops to outside on the Internet within 5 to 10 minutes of logging on after restarting!
Please someone find a solution!
It seems UK exchange users are getting some very bad effects.
[ August 06, 2004, 04:01 PM: Message edited by: Chris White - Stirling ]
Posts: 20
Joined: 27.Jul.2004
From: Portugal
Status: offline
hey.. it's not just a UK Exchange users problem... I have the same problem as you do in my Exchange Server (check the "Cannot send mail to certain domains" thread on this forum)..
so far, no one was able to get me in the right direction... I thought it was a DNS problem, but I can telnet all the problematic domains...
Posts: 2
Joined: 23.Aug.2004
From: Oman
Status: offline
Hi, we are facing the same problem. We have been on MSExchange 2003 since the last 2 months and no problems. The only change made recently is the updated to Symantec ver 9, 2 weeks back. Since then have been having the outgoing queue filling up with mails not being sent to various domains till we restart the server. It started with just aol and msn domains and now its any random domain. We receive an NDR which says "The connection was dropped due to an SMTP protocol event sink"
We have tried checking the dns, blocked dns and there is no problem in those areas. Any pointers will be greatly appreciated. TIA kbs
[ August 23, 2004, 02:11 PM: Message edited by: kbs ]
Posts: 20
Joined: 27.Jul.2004
From: Portugal
Status: offline
I completely agree, Chris...
unfortunately, the configuration change I've made to Symantec AV has not completely solved my problem... It's true that mails to some of the problematic domains began to be sent (like hotmail.com for example), but I'm still having some problems...
this has to be some bug in Exchange 2003 (I have installed SP1 and this started only AFTER its installation)...
I have DNS properly configured and running, I can nslookup and telnet all those faulty domains and I can access my DNS server as well... However, I'm having events 2012 and 2013 constantly being reported in my Exchange Server computer Event Viewer (Windows 2003 Server):
Event 2012 (warning) "SMTP could not connect to the DNS server '192.168.10.1'. The protocol used was 'UDP'. It may be down or inaccessible."
Event 2013 (error) SMTP could not connect to any DNS server. Either none are configured, or all are down.
of course, I can connect to my DNS Server (another Windows Server 2003: domain controller)
Posts: 94
Joined: 1.Dec.2001
From: Maybrook, NY
Status: offline
I'm tagging along here. I'm using E2K3 on W2K3, been running this new setup for a week now with no issues, until today.
Mail to vzw.blackberry.net (Verizon) is just sitting in the queue. The odd thing is, it's listed as "queued" and delivery failures are "0". I changed the external DNS used on my DNS Forwarders to another DNS, and cycled the DNS server service - still no help. Mail seems to be flowing to other places at present.
Posts: 2
Joined: 19.Sep.2004
From: santa monica, CA
Status: offline
I am having exactly the same issue, to mycingular.blackberry.net..... still looking for the solution, DNS looks fine.
quote:Originally posted by dfosbenner: I'm tagging along here. I'm using E2K3 on W2K3, been running this new setup for a week now with no issues, until today.
Mail to vzw.blackberry.net (Verizon) is just sitting in the queue. The odd thing is, it's listed as "queued" and delivery failures are "0". I changed the external DNS used on my DNS Forwarders to another DNS, and cycled the DNS server service - still no help. Mail seems to be flowing to other places at present.
I know it may seem slightly off topic, but it resolved our issue. We were using our own DNS servers (which have forwarders to the internet set up) but mail was not going out correctly. I changed the exchange 2003 DNS settings to use our ISP's and touch wood, we havent had any problems since.
Posts: 96
Joined: 30.Jun.2004
From: Birmingham, United Kingdom
Status: offline
You mean you have a forwarder to your ISP's DNS Addresses?
I think most people would unless they are hosting their own Internet DNS server.
Everything on my SBS2003 Server is running perfectly bar the Exchange 2003 which wont send to certain or as Microsoft put it "growing list" of domains.
Its a bug and we have to face it that Microsoft have screwed alot of us with it. You cant say there are easy fixes with this like "you just need to check this tick box", its a very real incompatibility problem.
Certain ways of setting up the server even using the Wizards cant be getting it right. DNS is at fault here and is not ready to take on Exchange 2003 properly.
Where are the flamin white papers? Do Microsoft want to hide this problem from its hot fixes and reports of bugs?
If your a standard off the shelf buyer you pay ú850+ for this and it doesn't work properly. Even worse if you buy all the Mailbox CAL's too!
RE: Exchange 2003 - Mail Getting stuck going to certain... - 4.Nov.2004 3:58:00 PM
Guest
We have seen exactly the same thing running Exchange 2003 server. First of all we had a lot of problems and narrowed it down to our new firewall autoblocking certain legitemate email servers.
After switching this feature off the problem was much reduced but it is still present on a few domains. With errors like the connection was dropped due to an smtp protocol event sink and also connection dropped by remote host.
We are also using Demon UK, our DNS servers are ok. Is this an exchange 2003 thing?