exchange apperantly not sending all emails out

[reynolwi]

New exchange server... i removed the old one because it was having lots of problems after the DR so i replaced it. It was working perfectly. Email was coming in and out. I recently just added a DC into the system so that i could bring down one of them for maintenance. I transfered all the roles off the DC im bring down and transfered them to the new server i brought up and now email is having problems. The new server is running DNS, WINS, DHCP, it has all 5 FSMO roles and doesnt have any errors in the logs except for AutoEnrollment and DTC Error. Im installing Certificate Server on the new DC and uninstalling it from the old DC before i remove it from AD. I have exchange pointed to use the DNS server on the new DC. The queue says its going out but its not. I can send to my other domain name that forwards back into exchange, but exchange does not manage it (user@domain.com forwards to user@domain.net) and i get that email. But I have been trying to send emails to the domain suddenlink.com and suddenlink.net and its never received. The queue shows that suddenlink.com sent out but i have noticed that suddenlink.net sits back and says queued when i bring up that message.

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[reynolwi]

it is refusing to send out it looks like. I sent a test email out and it went straight into the queue and sat there saying its been queued. Why would this happen? I have gone in and manually set the directory access to look at the new dc.

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[58sniper]

When you moved Exchange, did you follow kb 822931?

What do the event logs say?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[noveyron]

Is the old DC switched off while these delivery problems occur? Is your new DC is a glogal catalog server?

 

[reynolwi]

Ok... it sorted itself out kinda and then it went right back to delaying every message. Im baffled at this because it was working perfectly and i change AD and exchange freaks out. At the site where exchange is sitting, there are 2 domain controllers now instead of 1 like there used to be. They both have completely different names and neither one has the old dc name or the old dc ip address, i used new names and new ip addresses when i brought them both up. Below is what each server is, and the FSMO roles are split between the two of them.

+ DC 1 is AD, GC, WINS, DNS, FILESVR and has the Schema, Domain Naming, and PDC FSMO roles assigned to it.

+ DC 2 is AD, WINS, DNS, DHCP, CERTSVR, and will have Sharepoint (i know, but not my choice so im following steps to install it on a domain controller) and also has the RID and Infrastructure FSMO roles assigned to it.

looking at ESM i cann see under the directory access tab that exchange has located both DCs in this site and has them listed as Domain controllers, the configuration server is DC2, and the Global Catalog is DC1.

Ive gone thru DNS and looked and can not find anything that points back to the old dc server or its IP address. There are no errors on exchange, dc 1 has an auto enrollment error which i posted below, and dc 2 has no errors.

DC 1 Error
Event Type: Error
Event Source: AutoEnrollment
Event Category: None
Event ID: 13
Date: 8/8/2008
Time: 12:35:39 PM
User: N/A
Computer: DC 1
Description:
Automatic certificate enrollment for local system failed to enroll for one Domain Controller certificate (0x80070005). Access is denied.

DC 2 has been online longer than DC 1 has been. DNS is setup like this (somebody told me this is how it needed to be setup):

DC 1
Primary points to DC 2
Secondary points to itself

DC 2
Primary points to itself
Secondary points to DC 1

EXCHANGE
Primary points to DC 2
Secondary points to DC 1

DC 3 (remote site 1)
Primary points to DC 2
Secondary points to itself

DC 4 (remote site)
Primary points to DC 2
Secondary points to itself

And all the WINS Server entries have DC 1 listed at the top of the list.

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[reynolwi]

Ok i have timed it and exchange is delaying messages by about 30mins before delivery.

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[58sniper]

Still not sure what's causing the delay, but I'd recommend all DCs that are running DNS point to themselves (the IP of the server, NOT 127.0.0.1) as the primary DNS, and to another server as secondary. It's faster, and reduce network traffic.

Look at the SMTP logs to see what's going on when the server is attempting to send something out.

Are you using a smarthost?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/