Am working on Win2K servers with Exchange 2000.
I have 2 servers in the same 'Routing Group'. They are Server1 and Server2.
Server1 and Server2 should be synchronizing the public folders but they are not.
Server1 sends messages to Server2 using the Server1-IS@domain.com account and Server2 receives and processes it.
The problem is that Server2's messages never make it to Server1.
I tracked those messages and on Server2 they only made it to the Categorizer.
Does anyone know whey this Server is not using the Server2-IS@domain.com account for sending updates and why the emails are getting stuck in the Categorizer.
Oops... The messages from Server2 (eventhough are submitted to the
Categorizer) do not show in the message queue.
I've already checked the 'ProxyAddress' using ADSIEdit and that seems fine on both the servers.
I get loads of logs with the 'The MAD monitor is initializing' and 'The MAD monitor is initialized'. MY log file is filled with them on both servers...
Changes taking place on Server2 are not propagating to Server1. I've checked everything MS says but no use.
Server2's email never gets to Server1.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I already did all that the website told me to. Nothing worked.
Do you have any idea why the mail only reaches the 'Categorizer'?
YOu can track emails from Server1 all the way to Server2. Doesn't do the same the other way around.
Another thing - Server1 has a SMTP queue for Server2.
Server2 doesn't have anything specific for Server1.
I checked after your posting.
Both servers have their own names only in the DNS setting of SMTP.
Where is mail supposed to go after being 'Submitted to the Categorizer'?
On Server1 it goes to Server2 but not the other way.
The Proxy addresses on Server2 are 'PublicFolderStore@domain.
More info...
I never used to get too many of the 'MAD monitor...' messages in the logs. Past 3 days have seen a hundred or more.
Server2 is the 'Master' in the 'First Routing Group' and Server1 is the 'Member'.
Is there a way for me to add a Queue on Server2 for mail going to Server1.
I have a Queue on Server1 which says Server2 (Remote delivery).
Take off the DNS entries on the SMTP virtual server, never use that setting. What I was talking about is using internal DNS only on the TCP/IP properties of the Exchange servers. the DNS settings on the SMTP can cause madness :)
you should only have 2 proxy addresses for the PF store by default; the SMTP, which is 'machinename-IS@domain.com
D
http://support.microsoft.c
I thought this would better explain message flow thru the cat, than I could type it :). I think your problem is the extra proxy address of the PF store, if I had to venture a guess.
D
I added the extra SMTP address to see what happens. Nothing did.
Anyways, I took it out after reading your post.
It was my bad in the DNS thing. The SMTP Virtual Server is not doing DNS. The servers are doing internal DNS.
I'm still in a dilemma as to why the Server's message isn't getting across.
Also, the PF store has another property called 'mail'. Should that be something specific?
- Vikram
On the diagnostics logging tab, turn up logging on MSEXCHANGEIS, Public folders, on attributes on Replication conflicts, Replication General, and you may want to check on Transport as well.
http://support.microsoft.c
http://support.microsoft.c
D
You were right about the Cat logging. Just as I turned that on I got some 5.4.8 NDRs
These messages were coming because Server1's recipient policy had server1.domain.com in it. Removing that value from the default policy got the message to the other end. But replication still did not happen as the 'Public Folder Heirarchy' folder was outdated (I think).
I'm almost certain that the 'mail' and 'proxyAddresses' are messed up.
I keep seeing PublicFolderStore@domain.c
hierarchy won't get outdated, it's just a listing of folders. the real replication is content, which you control by setting up replicas on other PF stores. As far as suggestions, my earlier comments still stand, try those and see. Do you have any content replicating to the other server, or just folder hierarchy? BTW, hierarchy is automatic.
D
I created some new folders (connected to server2). In a couple of minutes those (folders, without any content) replicated over to Server1.
I have now set replication on a folder on Server2 destined for Server1. Am waiting for a few minutes atleast before I conclude it working/dead.
Also, I got some 'Backfill' messages on Server1. What does that mean?
- V
One of the folders (old ones) with stuff in it got replicated onto Server1 without the contents. From your message I gather that things wouldn't happen instantly. So, I'm going to give it a couple of hours to fix itself right.
Now that I see the folder things look greener...
:-)
Will update after lunch.
- V
This is one of the warnings -
**********************
The transport configuration type 4 for the directory entry CN=MICROSOFT MTA,CN=***,CN=SERVERS,CN=F
For more information, click http://www.microsoft.com/c
***********************
It is accompanied with this informational event -
************************
(BASE IL OPERATOR(24) Proc 221) Address Registration failed for transport type : 3 (8)
For more information, click http://www.microsoft.com/c
************************
The Microsoft MTA does NOT have anything set on both the servers in the 'proxyAddress' attribute. No X.400 and no SMTP
Are you SURE that your RUS is working?? It doesn't sound like it.
http://support.microsoft.c
this is a 5.5 article, but it describes the error.
Are all the services running? I feel like I'm missing some valuable info here, all these attirbutes should be set. Is Exchange and AD in native mode or mixed mode? Let me know which for each....
D
Well, if I were you, I'd manually enter the addresses in the format I gave you in the above post. Do the SMTP and the X.400 both. Use the copy/paste, if you don't think you can recreate it. I KNOW you can do the SMTP address... :)
Please list the Exchange server's roles in the AD, such as DNS,WINS etc....
D
I did what you asked. I am giving the computers to think about their task :)
I will write about more progress in the morning.
The 2 servers in question are DNS servers within our domain. We have another machine as our WINS server.
These 2 servers are DCs and DNS servers.
Are the proxy Addresses supposed to be filled in by some utility or are they set by default installation?
- V
The Event 9302s that I was getting (am still)
http://support.microsoft.c
talk about 5 types. I only get the warnings for types 1 thro 4. Since I don't get anything for type 5 I must be alright with those warnings...
Its getting dark here again :(
- V
BTW, did you do anything to change this server? Like install a windows service pack, or change IIS services in any way? Something sounds badly screwed up, and I'd like to start with the basics. TCP/IP properties, tell me what DNS server each machine is looking at. Second, check DSAccess and tell me what GCs and DCs are listed on that page. (properties of the server object, in the ESM)
d
I don't remember changing anything ... did install certificates on the 2 servers approximately when I saw the issue for the first time.
Both teh servers are pointing to themselves as Primary DNS and a 3rd machine as secondary.
On Server 1 -
Server2 - GC - Port 3268
Server3 (not running exchange) - GC - Port 3268
Server1 - DC - Port 389
Server1 - Config - Port 389
(all set to auto)
On Server2 -
Server2 - GC - Port 3268
Server2 - DC - Port 389
Server2 - Config - Port 389
(all set to auto)
Honestly, I think you have issues aside from Exchange. If you rebooted the 2 exchange boxes, reboot the other DC/GC as well. I'd also like to peek at the event viewer to see what messages are showing up in the applog, upon rebooting, from all 3 servers.
http://support.microsoft.c
Troubleshooting the RUS, read over this one too. Let me know how you'd like to proceed.
D
Didn't have to do any of that.
I think I've reached a little ahead of where you left me.
You see all this while I was trying to replicate folders which had been created before I changed the Recipient Policy (since I was getting the 5.8.4 NDRs). I think that the contents were not going over to Server1 as all these folders were stamped with an email address which was no longer up to date with the recipient policy.
This dawned on me in my sleep last night and was worth a shot.
This morning I created a new folder on Server2, and added a post to it (random crap). Then I added this new folder to be replicated to Server1. It happened within 30 seconds with the contents.
So, I think the RUS needs to rebuild all the public folders. If you think this is the right thing to do, how do I do it i.e. Is there a way to ask RUS to only update PFs?
- V
By default, folders in 2000/2003 are not mail-enabled, you have to mail-enable them yourself. In 5.5, all PFs are mail enabled. that's why some fodlers have an address, and some do not.
As to the previous comment, allow me to explain the PFs. the hierarchy, or listing of folders that you see, comes over automatically when the servers are in teh same org, and internal DNS is set up properly. the RUS doesn't rebuild them, so to speak. the RUS stamps every object in AD with a proxy address, and this includes the public and private store objects. If that store is not properly stamped, things aren't going to work very well. So, it sounds like to me that since you've changed the RP, and it's working, you should simply do an update, then a rebuild on the RUS, it's as simple as a right-click.
Now, if this doesn't take care of existing replicas that were failing before, you should consider removing the replica, waiting about an hour, then putting that replica back in. that should probably finish it off.
Happy New Year!
D
It seems to be working just fine now. Don't know what we did all through but no errors and all replication is happening just fine. Didn't need to rebuild also.
I was asking about the PFs rebuilding as in the network I am in there is another Unix mail server which forwards email to an exchange address which is different from username@domain.com (it is username@server1.domain.co
Now that I'm not rebuilding it doesn't matter...
Thanks a lot for all your help. It was great.
:)
Happy New Year
- V
"It seems to be working just fine now. Don't know what we did all through but no errors and all replication is happening just fine. Didn't need to rebuild also."
Eventually, the RUS will update and restamp anyway, if it's functioning properly. Don't think of the rebuild as a big deal, in an environment without complex replication, it should only take a few minutes.
D
Business Accounts
Answer for Membership
by: JasonBighamPosted on 2003-12-23 at 12:22:10ID: 9993467
Any help here (based on your subject)?
http://www.eventid.net/dis