RE: Public Folder Replication Across Routing Groups
What do you mean by instance? Do you mean an available public folder store on each local server which pertains to the global public's from the context you want to replicate from? Well if so, then yes :) I fixerered this problem, I think some kind of corruption took place more than anything. I reverted back to my old config, they still didn't work. I put it back how I wanted it, obviously they were still not working. What I did then was delete the public folder store on each server that was having the problem and re-created it, after a while they were back working again, so ive done this on every server and there all fine now, they are all working as I want them with my chosen setup :) -Original Message- From: Ed Crowley [mailto:[EMAIL PROTECTED] Sent: 31 May 2003 08:59 To: Exchange Discussions Subject: RE: Public Folder Replication Across Routing Groups Have you created instances on those public folder servers? Ed Crowley MCSE+I MVP Helping others with Exchange for over a twentieth of a century. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Doody Sent: Friday, May 30, 2003 12:48 AM To: Exchange Discussions Hi, to combat a problem I have been having, I have recreated the configuration within Exchange, and used different routing groups for different servers to accomplish the same setup as I had previously. However, since putting the different servers in different routing groups, public folders are no longer working. The public folders work at head office where I am, but at remote sites where servers are in a different routing group, the public folders cannot be accessed and they say that they probably haven't been replicated. _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=; lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Public Folder Replication Across Routing Groups
Have you created instances on those public folder servers? Ed Crowley MCSE+I MVP Helping others with Exchange for over a twentieth of a century. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Doody Sent: Friday, May 30, 2003 12:48 AM To: Exchange Discussions Hi, to combat a problem I have been having, I have recreated the configuration within Exchange, and used different routing groups for different servers to accomplish the same setup as I had previously. However, since putting the different servers in different routing groups, public folders are no longer working. The public folders work at head office where I am, but at remote sites where servers are in a different routing group, the public folders cannot be accessed and they say that they probably haven't been replicated. _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
Public Folder Replication Across Routing Groups
Hi, to combat a problem I have been having, I have recreated the configuration within Exchange, and used different routing groups for different servers to accomplish the same setup as I had previously. However, since putting the different servers in different routing groups, public folders are no longer working. The public folders work at head office where I am, but at remote sites where servers are in a different routing group, the public folders cannot be accessed and they say that they probably haven't been replicated. _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: SEPARATE EXCHANGE ROUTING GROUPS FOR HOSTING SAME DOMAIN ON S EPARATE EXCHANGE 2000 SERVERS
SMTP domains can span multiple routing groups.. your issues sound like they could possibly be directory related. Can users see the entire GAL? Do they receive NDRs? What do those NDRs say? Errors in the event viewer? -Original Message- From: Marko [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 08, 2002 1:16 AM To: Exchange Discussions Subject: SEPARATE EXCHANGE ROUTING GROUPS FOR HOSTING SAME DOMAIN ON SEPARATE EXCHANGE 2000 SERVERS Hi! I am trying to host a single domain, named us.com on two separate exchange 2000 servers that are each in a separate routing group connected by a routing group connector. However, it is not possible to send mail between recipients hosted on each exchange server, since a bounce occurs. Apparently, the same domain cannot be hosted on two exchange servers that are in SEPARATE routing groups. The above scenario DOES WORK if placing the two exchange servers in the SAME routing group. It appears that having exchange servers in the same routing group ensures that both exchange servers are using the same global catalog in active directory to deliver mail. The way my domain is split is so that one server, call it server A, hosts part of mailboxes for domain us.com. Server B hosts part of mailboxes for domain us.com and all mailboxes for domain europe.local. Both server A and B are primary domain controllers with active directory, DNS and Exchange installed on a single machine. Why do server A and B have to be in different routing groups and have to host the same domain? Server A is located in the US, server B is in Europe. They are connected via a rather reliable VPN. Only server A has a static Internet IP assigned, therefore server B cannot directly accept messages from the Internet; it is connected to a DSL modem with a dynamic IP. Users on server A and B share the same domain name - us.com; user account and mailbox for [EMAIL PROTECTED] is located in the US on server A, while user account and mailbox for [EMAIL PROTECTED] is located in Europe on server B. European users (connecting to server B) cannot have their accounts hosted on server A, since they use Outlook to connect to server B locally. The same, European, users also must have @us.com domain email set as Primary SMTP Account, with the intranet SMTP address @europe.local set as secondary SMTP account. ACTIVE DIRECTORY IMPLEMENTATION: Server A is PDC for domain us.com and has a trust relationship established with server B that is PDC for domain europe.local. Both domains are within the same forest. The DNS entry for domain us.com is on server A, a secondary copy of the domain us.com is stored in server B's DNS. The MX record for domain us.com is pointing only to the exchange server A, the host being a.us.com. Is there a better DNS configuration for what we want? Both Exchange servers are in the same Exchange organization and in the same administrative group. Once routing connectors are created, servers are connected to each other, everything appears to be working in the monitoring view. Is there any way to implement this scenario with two Exchange servers in separate routing groups. Once again, this scenario works with the two servers in the same routing group, where it appears that mailboxes within the same domain can be spread across multiple exchange servers. But we need to separate the two servers, since they are not connected in a LAN, and we are also using fax connectors that each must work within a separate routing group with a separate server. I would greatly appreciate any help! Regards, Marko _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: SEPARATE EXCHANGE ROUTING GROUPS FOR HOSTING SAME DOMAIN ONSEPARATE EXCHANGE 2000 SERVERS
just because you have two exchange servers in 2 seperate routing groups that should not prevent the 2 exchange servers from seeing each other or for the MTA's on each server to be able to recognise which server the mailboxes are on and send them to the appropriate server. Are your routing groups connected via a smtp or a ip connector. Also are the upns for the users the same on both servers, meaning when you create a user name on the win2k dc when it gives you the option for upn name does it say xyz.com on both servers, meaning if you create a user cslled kane on server a is it [EMAIL PROTECTED] and if you create a user called kane1 on server b is it [EMAIL PROTECTED] or is it [EMAIL PROTECTED] UPNS have to be the same on both servers. Having said that are these 2 servers in the same domain, sorry if you had already answered this question in your essay, but answer it again. Are they part of the same domain or are they 2 seperate domainslike one is xyz.us.com and the other is xyz.europe.com. If they are different i bet you your upns are also different. I would suggest trying to create a upn on server b also called xyz.us.com and assign that all your users and then see if the problem goes away. Also for your users in europe have you created a smtp server on their exchange server and have that forward to a smart host or you did not bother creating a virtual smtp server and directly forwarding everything to a smart host. Just wondering..hope this helps or atleast give you a direction to look in to trouble shoot. -Original Message- From: Ed Crowley [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 08, 2002 6:38 PM To: Exchange Discussions Subject: RE: SEPARATE EXCHANGE ROUTING GROUPS FOR HOSTING SAME DOMAIN ONSEPARATE EXCHANGE 2000 SERVERS Are the two domains in the same AD forest? If not, you have two organizations and you will need some sort of third party directory syncronization utility to essentially create contacts on one side for mailboxes on the other. Ed Crowley MCSE+Internet MVP kcCC+I Tech Consultant hp Services Protecting the world from PSTs and Bricked Backups! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Marko Sent: Wednesday, August 07, 2002 11:16 PM To: Exchange Discussions Subject: SEPARATE EXCHANGE ROUTING GROUPS FOR HOSTING SAME DOMAIN ON SEPARATE EXCHANGE 2000 SERVERS Hi! I am trying to host a single domain, named us.com on two separate exchange 2000 servers that are each in a separate routing group connected by a routing group connector. However, it is not possible to send mail between recipients hosted on each exchange server, since a bounce occurs. Apparently, the same domain cannot be hosted on two exchange servers that are in SEPARATE routing groups. The above scenario DOES WORK if placing the two exchange servers in the SAME routing group. It appears that having exchange servers in the same routing group ensures that both exchange servers are using the same global catalog in active directory to deliver mail. The way my domain is split is so that one server, call it server A, hosts part of mailboxes for domain us.com. Server B hosts part of mailboxes for domain us.com and all mailboxes for domain europe.local. Both server A and B are primary domain controllers with active directory, DNS and Exchange installed on a single machine. Why do server A and B have to be in different routing groups and have to host the same domain? Server A is located in the US, server B is in Europe. They are connected via a rather reliable VPN. Only server A has a static Internet IP assigned, therefore server B cannot directly accept messages from the Internet; it is connected to a DSL modem with a dynamic IP. Users on server A and B share the same domain name - us.com; user account and mailbox for [EMAIL PROTECTED] is located in the US on server A, while user account and mailbox for [EMAIL PROTECTED] is located in Europe on server B. European users (connecting to server B) cannot have their accounts hosted on server A, since they use Outlook to connect to server B locally. The same, European, users also must have @us.com domain email set as Primary SMTP Account, with the intranet SMTP address @europe.local set as secondary SMTP account. ACTIVE DIRECTORY IMPLEMENTATION: Server A is PDC for domain us.com and has a trust relationship established with server B that is PDC for domain europe.local. Both domains are within the same forest. The DNS entry for domain us.com is on server A, a secondary copy of the domain us.com is stored in server B's DNS. The MX record for domain us.com is pointing only to the exchange server A, the host being a.us.com. Is there a better DNS configuration for what we want? Both Exchange servers are in the same Exchange organization and in the same administrative group. Once routing connectors are created, servers are connected to each other, everything appears to be working in the monitoring view
RE: SEPARATE EXCHANGE ROUTING GROUPS FOR HOSTING SAME DOMAIN ONSEPARATE EXCHANGE 2000 SERVERS
Are the two domains in the same AD forest? If not, you have two organizations and you will need some sort of third party directory syncronization utility to essentially create contacts on one side for mailboxes on the other. Ed Crowley MCSE+Internet MVP kcCC+I Tech Consultant hp Services Protecting the world from PSTs and Bricked Backups! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Marko Sent: Wednesday, August 07, 2002 11:16 PM To: Exchange Discussions Subject: SEPARATE EXCHANGE ROUTING GROUPS FOR HOSTING SAME DOMAIN ON SEPARATE EXCHANGE 2000 SERVERS Hi! I am trying to host a single domain, named us.com on two separate exchange 2000 servers that are each in a separate routing group connected by a routing group connector. However, it is not possible to send mail between recipients hosted on each exchange server, since a bounce occurs. Apparently, the same domain cannot be hosted on two exchange servers that are in SEPARATE routing groups. The above scenario DOES WORK if placing the two exchange servers in the SAME routing group. It appears that having exchange servers in the same routing group ensures that both exchange servers are using the same global catalog in active directory to deliver mail. The way my domain is split is so that one server, call it server A, hosts part of mailboxes for domain us.com. Server B hosts part of mailboxes for domain us.com and all mailboxes for domain europe.local. Both server A and B are primary domain controllers with active directory, DNS and Exchange installed on a single machine. Why do server A and B have to be in different routing groups and have to host the same domain? Server A is located in the US, server B is in Europe. They are connected via a rather reliable VPN. Only server A has a static Internet IP assigned, therefore server B cannot directly accept messages from the Internet; it is connected to a DSL modem with a dynamic IP. Users on server A and B share the same domain name - us.com; user account and mailbox for [EMAIL PROTECTED] is located in the US on server A, while user account and mailbox for [EMAIL PROTECTED] is located in Europe on server B. European users (connecting to server B) cannot have their accounts hosted on server A, since they use Outlook to connect to server B locally. The same, European, users also must have @us.com domain email set as Primary SMTP Account, with the intranet SMTP address @europe.local set as secondary SMTP account. ACTIVE DIRECTORY IMPLEMENTATION: Server A is PDC for domain us.com and has a trust relationship established with server B that is PDC for domain europe.local. Both domains are within the same forest. The DNS entry for domain us.com is on server A, a secondary copy of the domain us.com is stored in server B's DNS. The MX record for domain us.com is pointing only to the exchange server A, the host being a.us.com. Is there a better DNS configuration for what we want? Both Exchange servers are in the same Exchange organization and in the same administrative group. Once routing connectors are created, servers are connected to each other, everything appears to be working in the monitoring view. Is there any way to implement this scenario with two Exchange servers in separate routing groups. Once again, this scenario works with the two servers in the same routing group, where it appears that mailboxes within the same domain can be spread across multiple exchange servers. But we need to separate the two servers, since they are not connected in a LAN, and we are also using fax connectors that each must work within a separate routing group with a separate server. I would greatly appreciate any help! Regards, Marko _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
Routing groups
I have 4 routing groups. 2 are pure 5.5 servers. 1 is mixed. 1 is pure exch2k. Should I set routing group connectors up to all groups from the pure exch2k group? Thanks. _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
