Link to home
Start Free TrialLog in
Avatar of wnabsolute
wnabsolute

asked on

Exchange 2003 delivery delays - help!

Hi,

We have Exchange 2003 / Windows Server 2003, fully patched and up to date.  We upgraded from Small business server 2000 and boy oh boy are we having problems.

A full prep was done on the SBS box prior to replication to the 2003 box.  Exchange mailboxes were migrated over and everything seemed to be working nicely except for a 10 minute delay in mail delivery.  It varies slightly, but generally 10 minutes for any mail (either internal to external, vice-versa, internal - internal)

I've found where the a problem is.  In the queue viewer, it sits in the 'Messages Pending Submission" for 10 minutes before it delivers.  There is never any large backlog, the server is under little load and there is ample ram (1 GB).

Looking at the problem through message tracker, during the same period of delay it immediately lists the message as:

SMTP: Message Submitted to Advanced Queuing.

but takes the full 10 minutes to actually get to:

SMTP: Started message submission to advanced queue.

So that's where the delay is.  Any ideas?

Thanks everyone,

Warwick
Avatar of Vahik
Vahik

The most important thing that i am sure u know is that u should not have any external dns configured in ur smtp server at all.Ur exchange and dns must point to internal dns servers.U must also have an external DNS listed in ur DNS servers forwarders tab.U must also make sure u have a GC running and ur ZNOE in ur dns is configured correctly and
lists ur GC and DC.Is this how u have configured ur network?
Avatar of wnabsolute

ASKER

Hi Vahik,

thanks for your quick response :)

In exchange we found that the DNS servers for our Default SMTP Virtual Server was wrong, so we set it to the internal DNS.  Unfortunately that didn't speed things up.

The forwarders in the DNS server console are correct.

We are getting errors in the event view regarding 'can't contact GC' every now and again.  Is there any way to check that the GC is running properly?  Exchange auto detects it in Exchange Systems Manager - so it's a bit hard to work out what's going on,

thanks,

Warwick
what dns servers in default was wrong?there should be none listed in ur smtp server.Call back to clarify this.
Also on ur exchange server run ipconfig /flushdns and ipconfig /registerdns.
on ur exchange servers tcpip settings for dns entery did u put down ur internal dns server?
Oh forgot after any changes to ur smtp server just restart ur exchange also.
As a matter of fact restart ur DC GC DNS and exchange.
Sorry, misread your previous email - DNS setting removed from exchange, I ran the ipconfig commands too - waiting for people to go to lunch before I restart, will let you know how I went, thanks so much for your help so far :)
Unfortunately it doesn't seem to fix the problem. Here are some recent logs from event viewer:

The Microsoft MTA registry parameter Max RPC Alloc Size is missing.  The default value will be used. [BASE MAIN BASE 1] (14)

-------------
I blanked out our company domain name in the item below
----------

A Kerberos Error Message was received:
         on logon session
 Client Time:
 Server Time: 1:53:43.0000 1/29/2004 Z
 Error Code: 0xd KDC_ERR_BADOPTION
 Extended Error: 0xc00000bb KLIN(0)
 Client Realm:
 Client Name:
 Server Realm: <company hidden>.COM
 Server Name: host/server03.<company hidden>.com
 Target Name: host/server03.<company hidden>.com@<company hidden>.COM
 Error Text:
 File: 9
 Line: ab8
 Error Data is in record data.
-------------------

I've also found DNS errors where our DNS server has tried querying up the names of workstations against our ISPs DNS, eg it will try to query WORKSTATION, I look in the logs and there are failed attempts for WORKSTATION.com and WORKSTATION.org

Thanks

I dont know why ur computers are authenticating against ur isp's dns servers.Why dont u delete ur zone in ur dns server and recreate again.
Does the zone in ur dns server matches ur active directory domain name?Do all ur clients on their tcpip setting for dns entery have ur internal dns server registerd?U may have to put a call to microsoft if ur active directory is screwed up.Call abck i will be here for a while.
One more thing if u dns service is not on then ur clients wont be able to contact KDC for authentication.So that may be the reason ur computers are contacting ur isp's dns server.
Why dont u reinstall ur dns server again.I think u have dens problem.
We've already deleted the DNS zones, both forward and backward lookup zones and recreated them, rebooted etc.  I think it may be retaining some one the DNS information in Active Directory - is there a way to flush out all DNS info out of Active Directory after we've removed the DNS server, so that we can install it clean again?
I just ran DNSDIAG again and here's some output that seems to be indicating a problem:


**********************************************************

No external DNS servers on VSI. Using global DNS servers.
Using the default DNS servers configured for this computer.
192.168.16.3
Created Async Query:
--------------------
        QNAME = server02
        Type = MX (0xf)
        Flags =  UDP default, TCP on truncation (0x0)
        Protocol = UDP
        DNS Servers: (DNS cache will not be used)
        192.168.16.3

Connecting to DNS server 192.168.16.3 over UDP/IP.
Connected to DNS 192.168.16.3 over UDP/IP.
Response received from DNS server.
Received DNS Response:
----------------------
        Error: 9002
        Description: Not available.
Querying via DNSAPI:
--------------------
        QNAME = server02
        Type = A (0x1)
        Flags =  No flags, (0x0)
        Protocol = Default UDP, TCP on truncation
        Servers: (DNS cache will be used)
        Default DNS servers on box.

Received DNS Response:
----------------------
        Error: 0
        Description: Success
        These records were received:
        server02.campanyname.com    A    192.168.16.3

No CNAME records in reply.
Checking reply for A record for server02
1 A record(s) found for server02

Target hostnames and IP addresses
---------------------------------
HostName: "server02"
        192.168.16.3
Shutting down ATQ
Shutting down IISRTL
Exit code: 0

************************************************************
In regards to the 'Error: 9002', I assuming the DNS if going mental because it doesn't produce a meaningful error - any ideas?

Thanks
I've also found that Error 9002 means: DNS_ERROR_RCODE_SERVER_FAILURE
well when u delete the dns zones just refresh itthen when u want to create the zone again just right click on server name in dns and choose
configure this server and go through the motion and once finish restart ur server and make sure the data is replicated to ur DC's.If u choose active directory integraded then all the data will be stored in ur AD
and if u go to ur active directory users and computers u will see under
system\microsoftdns.I really dont know what else to say at this point.
But do call back to see if this will ever  be resolved
OK boys and girls, I've fixed it.

It turned out it was an event sink problem due to active directory pollution from our migration from SBS2000 to Windows 2003 Standard.

I ran 'cscript smtpreg.vbs /enum' and it printed out 5 event sinks.

I then built up another windows 2003 box with exchange.  It was completely isolated from our network to stop any replication pollution.  I ran the 'cscript smtpreg.vbs /enum' on this fresh box and it only printed out 3 event sinks.  I found that all 3 existed on the troubled server, so I removed the 2 event sinks that didn't correlate.  Bingo.  All fixed.  Thanks for your help anyway!
ASKER CERTIFIED SOLUTION
Avatar of GhostMod
GhostMod
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial