• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 285
  • Last Modified:

Exchange 2003- External mails getting stuck in que

Hi,
    We have an Exchange 2003 box. The users are receiving internal mails and are able to send internal and external mails. The problem is they are not able to receive external mails. It is sitting in the que we can see it. But it is not reaching the clients (outlook)

Please advice what we should do as it extremely urgent.

Thanks
0
Paawan
Asked:
Paawan
  • 6
  • 4
  • 2
1 Solution
 
MNH1966Commented:
You should increase logging so you have more troubleshooting information.
Go to the proberties of the Exchange server and the Diagnostic Logging tab.
Increase the logging levels on MSExchangeTransport and send some testmessages. You should see messages in your eventlog that hopefully point you in the direction of the cause of this problem.

Maurice
0
 
PaawanAuthor Commented:
Will try to do that.

Thanks
0
 
PaawanAuthor Commented:

Where are the log files stored? How do I look at them?

Regards

Paawan
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 
MNH1966Commented:
It logs in the Eventlog Application log, so you can view them with the standard Eventviewer.
0
 
PaawanAuthor Commented:

The site actually has two exchange 03 boxes lets call them A and B. Both of them speak to the ISP and both of them have MX records at the ISP. We had moved all the users to B from A. When messages come to A for users in B it should route it to B and it was happening from what we know. All of a sudden it is not happening anymore.

The messages are getting stuck at server A and not being routed to server B.

Help please.

Thanks

Paawan
0
 
rickyclourencoCommented:
If you moved all of the users from A to B, why do you still need A??
0
 
PaawanAuthor Commented:

Hi,
     As the MX records points to both server A and server B, the ISP sends mails randomly to both the servers hence we need to route mails from A to B.

We got the ISP to remove the MX record for the old server and now everything seems to be fine. There was event 2103 error which was due to DSAccess. Most probably the servers were not able to communicate between each other.

Thanks All.
0
 
PaawanAuthor Commented:
hi

We have exchange server 2003 server with Active domain controller.Recently we installed another exchange server with Additional domain controller in our network.Our main moto is we have to kill the old exchange server.After we moved all mail boxes from old server to new server,moved successfully.Then we tranfer the FSMO roles and exchnage 2003 recipient update service to new server,we removed old server ip address in ISP MX records.Now all mails are coming through the new server as well.When we shutdown the old server still users and dns is looking old server,even getting problem with mails also.After shut down the old server i am getting error in Event viewer in New server.

(1)The error is:Event Id : 9144   Catagory : NSPI Proxy   Source : MS Exchnage SA  Computer : GHQ01SW03 (New Server)
Description: NSPI proxy failed to connect to Global catalog ghq01sw02(old server address) hq.mewt (domain name) over transport Tcp/ip.This server is down or unreachable clients will not be directed to this GC until it is available again.

(2)Second Error: Event Id : 2103  Sorce : MS Exchnage DSAccess  Category : Topology  Computer : GHQ01SW03 (New Server)

Description: Process MAD.EXE (PID=4612).All Global catelog Servers in use are not responding
ghq01sw02 (Old server) hq.mewt (domain name).

PLease advice us still what are the roles we need to tranfer from old server to new server.

Its very urgent.Please kindly revert back as Asap.

Thanks
















0
 
rickyclourencoCommented:
is the old Exchange Server, also a Domain Controller?  DNS?
0
 
rickyclourencoCommented:
Thanks!
0
 
PaawanAuthor Commented:
hi

We have exchange server 2003 server with Active domain controller.Recently we installed another exchange server with Additional domain controller in our network.Our main moto is we have to kill the old exchange server.After we moved all mail boxes from old server to new server,moved successfully.Then we tranfer the FSMO roles and exchnage 2003 recipient update service to new server,we removed old server ip address in ISP MX records.Now all mails are coming through the new server as well.When we shutdown the old server still users and dns is looking old server,even getting problem with mails also.After shut down the old server i am getting error in Event viewer in New server.

(1)The error is:Event Id : 9144   Catagory : NSPI Proxy   Source : MS Exchnage SA  Computer : GHQ01SW03 (New Server)
Description: NSPI proxy failed to connect to Global catalog ghq01sw02(old server address) hq.mewt (domain name) over transport Tcp/ip.This server is down or unreachable clients will not be directed to this GC until it is available again.

(2)Second Error: Event Id : 2103  Sorce : MS Exchnage DSAccess  Category : Topology  Computer : GHQ01SW03 (New Server)

Description: Process MAD.EXE (PID=4612).All Global catelog Servers in use are not responding
ghq01sw02 (Old server) hq.mewt (domain name).

PLease advice us still what are the roles we need to tranfer from old server to new server.

Its very urgent.Please kindly revert back as Asap.

Thanks
0
 
rickyclourencoCommented:
Did you DE-MOTE the old domain controller??  You have to run DCPROMO to remove the Domain Controller Attributes from the server..

Make sure that the NEW Exchange server is a Global Catalog?

You want to make sure that you make the NEW EXCHANGE SERVER a GC while the OLD one was still up and running, so that the proper information was replicated (just a precaution)....do the following below(unless it is done already)

How to Create a New Global Catalog on the Destination Global Catalog Server
To create a new global catalog:
1.      On the domain controller where you want the new global catalog, start the Active Directory Sites and Services snap-in. To start the snap-in, click Start, point to Programs, point to Administrative Tools, and then click Active Directory Sites and Services.
2.      In the console tree, double-click Sites, and then double-click sitename.
3.      Double-click Servers, click your domain controller, right-click NTDS Settings, and then click Properties.
4.      On the General tab, click to select the Global catalog check box to assign the role of global catalog to this server.
5.      Restart the domain controller.

If this is done correctly, then you should check the EXCHANGE SYSTEM MANAGER -->Administrative Groups --> First Admin Group --> (SERVER NAME) <--right click on the server name goto properties -->Directory Access......once you get here, you can check which domain controllers Exchange is looking at for the GC, and you can MANUALLY change it
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

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