|
|
|
date: Thu, 28 Feb 2008 13:53:49 +0800,
group: microsoft.public.exchange.connectivity
back
Exchange 2003 - Routing Group connector
Hi there,
Appreciate someone could give me some hint on the solution.
We have few Exchange servers in branches that all connected to HQ Exchange
server via Routing Group Connector. All emails among the branch offices and
from External are delivered from HQ Exchange 2003 to the branch Exchange
2003 server.
Recently Branch-A patch their Exchange server 2003, and after the patch the
Routing Group Connector between branch-A and HQ stop working. We thought it
is due to patch problem, therefore we uninstall patch, still probelm
persist. Then we rebuild the server from OS level and reinstall Exchange
2003 without any further patching, it still problem.
We then setup another Exchange 2003 server on separate hardware into same
SITE, and use that new server only for Routing Group connection to HQ, it
works perfectly.
We are running out of idea, and the only think one that we suspect is
possible due to the server name, as when we rebuild the existing problematic
server, we use back the same server name. If this the problem, how can we
get that corrected ?
When we force the Routing Group connection from HQ Exchange 2003 (from
Exchange Systems Mgr -> Queues) we can see from the network the SMTP traffic
passing, and sametime when we perform telnet port 25 from HQ Exchange we
notice a response from Exchange 2003 in Branch-A. So network is not a
problem.
We struggle for a month, and I really hope I can get something before we
perform another rebuild of the Exchange 2003 again.
thanks in advance
date: Thu, 28 Feb 2008 13:53:49 +0800
author: yhyap am
RE: Exchange 2003 - Routing Group connector
Hello Customer,
Thank you for posting here.
According to your description, I understand that the Routing Group
Connectors between the Head Office and branch office not work. If I have
misunderstood the problem, please don't hesitate to let me know.
Based on my research, I think the corrupted Routing Group Connectors
configuration may related this issue. I suggest we try the following steps
to see if we can resolve this issue:
I. Please ensure you create the Routing Group Connectors correctly in your
Exchange 2003. Please go thru the following KB:
HOW TO: Use Routing Group Connectors to Connect Routing Groups in Exchange
Server 2003
http://support.microsoft.com/?id=822929
Note: please clean the old Routing Group Connectors on both sides and
recreate a new one.
II. This problem may occur if the Authenticated Users group has been
removed from the Access this computer from the network user right.
To resolve this problem, grant the Authenticated Users group the Access
this computer from the network user right. To do this, follow these steps:
1. Click Start, point to Programs, point to Administrative Tools, and then
click Local Security Policy.
2. Expand Local Policies, and then click User Rights Assignment.
3. In the right pane, double-click Access this computer from network.
4. In the Local Security Policy Setting dialog box, look for Authenticated
Users in the Assigned To list.
If this item does not appear in the list, add the Authenticated Users
group. To do this, follow these steps:
a. Click Add, type authenticated users , click Check Names, and then click
OK.
b. In the Assigned To box, click to select the Local Policy Setting check
box that is displayed next to Authenticated Users.
c. Click OK.
5. Exit the Local Security Settings MMC snap-in.
6. Update the local security policy on the computer. To do this, click
Start, click Run, type secedit /refreshpolicy machine_policy /enforce , and
then click OK.
7. Follow steps 1 through 6 on every computer that is a member of the
routing group to verify that the Authenticated Users group has the Access
this computer from the network user right assigned.
If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:
Do you get any event error about the Routing Group Connectors?
I hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on exchange technical issues. If you have
issues regarding other Microsoft products, you'd better post in the
corresponding newsgroups so that they can be resolved in an efficient and
timely manner. You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "yhyap" <yhyap@newsgroup.nospam>
| Subject: Exchange 2003 - Routing Group connector
| Date: Thu, 28 Feb 2008 13:53:49 +0800
| Lines: 47
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| X-RFC2646: Format=Flowed; Original
| Message-ID:
| Newsgroups: microsoft.public.exchange.connectivity
| NNTP-Posting-Host: 203.115.247.206
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.connectivity:3602
| X-Tomcat-NG: microsoft.public.exchange.connectivity
|
| Hi there,
|
|
| Appreciate someone could give me some hint on the solution.
|
|
| We have few Exchange servers in branches that all connected to HQ
Exchange
| server via Routing Group Connector. All emails among the branch offices
and
| from External are delivered from HQ Exchange 2003 to the branch Exchange
| 2003 server.
|
|
| Recently Branch-A patch their Exchange server 2003, and after the patch
the
| Routing Group Connector between branch-A and HQ stop working. We thought
it
| is due to patch problem, therefore we uninstall patch, still probelm
| persist. Then we rebuild the server from OS level and reinstall Exchange
| 2003 without any further patching, it still problem.
|
|
| We then setup another Exchange 2003 server on separate hardware into same
| SITE, and use that new server only for Routing Group connection to HQ, it
| works perfectly.
|
|
| We are running out of idea, and the only think one that we suspect is
| possible due to the server name, as when we rebuild the existing
problematic
| server, we use back the same server name. If this the problem, how can we
| get that corrected ?
|
|
| When we force the Routing Group connection from HQ Exchange 2003 (from
| Exchange Systems Mgr -> Queues) we can see from the network the SMTP
traffic
| passing, and sametime when we perform telnet port 25 from HQ Exchange we
| notice a response from Exchange 2003 in Branch-A. So network is not a
| problem.
|
|
|
| We struggle for a month, and I really hope I can get something before we
| perform another rebuild of the Exchange 2003 again.
|
|
|
| thanks in advance
|
|
|
|
date: Fri, 29 Feb 2008 10:46:22 GMT
author: (Terence Liu [MSFT])
Re: Exchange 2003 - Routing Group connector
Yes, the way to create RGC is correct, as we have that running for other
branches connection with HQ server.
I have check the "Access this computer from the network Properties" and
"User" in fact "Everyone" is in.
The problem is kind of weird that the branch can send email to HQ Exchange
via the RGC created, but not the other way round.
thanks again in advance for any thoughts...
"Terence Liu [MSFT]" wrote in message
news:a3YXUBseIHA.4720@TK2MSFTNGHUB02.phx.gbl...
> Hello Customer,
>
> Thank you for posting here.
>
> According to your description, I understand that the Routing Group
> Connectors between the Head Office and branch office not work. If I have
> misunderstood the problem, please don't hesitate to let me know.
>
> Based on my research, I think the corrupted Routing Group Connectors
> configuration may related this issue. I suggest we try the following steps
> to see if we can resolve this issue:
>
> I. Please ensure you create the Routing Group Connectors correctly in your
> Exchange 2003. Please go thru the following KB:
>
> HOW TO: Use Routing Group Connectors to Connect Routing Groups in Exchange
> Server 2003
> http://support.microsoft.com/?id=822929
>
> Note: please clean the old Routing Group Connectors on both sides and
> recreate a new one.
>
> II. This problem may occur if the Authenticated Users group has been
> removed from the Access this computer from the network user right.
>
> To resolve this problem, grant the Authenticated Users group the Access
> this computer from the network user right. To do this, follow these steps:
>
> 1. Click Start, point to Programs, point to Administrative Tools, and
> then
> click Local Security Policy.
> 2. Expand Local Policies, and then click User Rights Assignment.
> 3. In the right pane, double-click Access this computer from network.
> 4. In the Local Security Policy Setting dialog box, look for
> Authenticated
> Users in the Assigned To list.
>
> If this item does not appear in the list, add the Authenticated Users
> group. To do this, follow these steps:
>
> a. Click Add, type authenticated users , click Check Names, and then
> click
> OK.
> b. In the Assigned To box, click to select the Local Policy Setting check
> box that is displayed next to Authenticated Users.
> c. Click OK.
>
> 5. Exit the Local Security Settings MMC snap-in.
> 6. Update the local security policy on the computer. To do this, click
> Start, click Run, type secedit /refreshpolicy machine_policy /enforce ,
> and
> then click OK.
> 7. Follow steps 1 through 6 on every computer that is a member of the
> routing group to verify that the Authenticated Users group has the Access
> this computer from the network user right assigned.
>
> If we cannot resolve the issue after we perform the above steps, please
> help me collect some information for further investigation:
>
> Do you get any event error about the Routing Group Connectors?
>
> I hope these steps will give you some help.
>
> Thanks and have a nice day!
>
> Best regards,
>
> Terence Liu(MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> This newsgroup only focuses on exchange technical issues. If you have
> issues regarding other Microsoft products, you'd better post in the
> corresponding newsgroups so that they can be resolved in an efficient and
> timely manner. You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check
> the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In
> doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> --------------------
> | From: "yhyap" <yhyap@newsgroup.nospam>
> | Subject: Exchange 2003 - Routing Group connector
> | Date: Thu, 28 Feb 2008 13:53:49 +0800
> | Lines: 47
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
> | X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
> | X-RFC2646: Format=Flowed; Original
> | Message-ID:
> | Newsgroups: microsoft.public.exchange.connectivity
> | NNTP-Posting-Host: 203.115.247.206
> | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.connectivity:3602
> | X-Tomcat-NG: microsoft.public.exchange.connectivity
> |
> | Hi there,
> |
> |
> | Appreciate someone could give me some hint on the solution.
> |
> |
> | We have few Exchange servers in branches that all connected to HQ
> Exchange
> | server via Routing Group Connector. All emails among the branch offices
> and
> | from External are delivered from HQ Exchange 2003 to the branch Exchange
> | 2003 server.
> |
> |
> | Recently Branch-A patch their Exchange server 2003, and after the patch
> the
> | Routing Group Connector between branch-A and HQ stop working. We thought
> it
> | is due to patch problem, therefore we uninstall patch, still probelm
> | persist. Then we rebuild the server from OS level and reinstall Exchange
> | 2003 without any further patching, it still problem.
> |
> |
> | We then setup another Exchange 2003 server on separate hardware into
> same
> | SITE, and use that new server only for Routing Group connection to HQ,
> it
> | works perfectly.
> |
> |
> | We are running out of idea, and the only think one that we suspect is
> | possible due to the server name, as when we rebuild the existing
> problematic
> | server, we use back the same server name. If this the problem, how can
> we
> | get that corrected ?
> |
> |
> | When we force the Routing Group connection from HQ Exchange 2003 (from
> | Exchange Systems Mgr -> Queues) we can see from the network the SMTP
> traffic
> | passing, and sametime when we perform telnet port 25 from HQ Exchange we
> | notice a response from Exchange 2003 in Branch-A. So network is not a
> | problem.
> |
> |
> |
> | We struggle for a month, and I really hope I can get something before we
> | perform another rebuild of the Exchange 2003 again.
> |
> |
> |
> | thanks in advance
> |
> |
> |
> |
>
date: Fri, 29 Feb 2008 19:24:10 +0800
author: yhyap am
Re: Exchange 2003 - Routing Group connector
Hello Customer,
Thank you for your update.
We do not recommend customer use one RGC for multiple sites. One RGC for
one branch is better.
Before you recreate the RGC on the branch office Exchange, I suggest you
delete the related RGC on the head office first. Restart SMTP service on
both sides. Then, recreate the RGC on both sides from beginning.
Then, verify the RGC status. To confirm that the Routing Group connector is
working as expected:
1. Start Exchange System Manager.
2. Expand Tools, expand Monitoring and Status, and then expand Status.
3. Confirm that two objects are listed for each Routing Group connector
(one for each end). The Status column indicates the current state of the
link.
If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:
Do you get any event error about the Routing Group Connectors?
I hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on Exchange technical issues. If you have
issues regarding other Microsoft products, you'd better post in the
corresponding newsgroups so that they can be resolved in an efficient and
timely manner. You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "yhyap" <yhyap@newsgroup.nospam>
| References:
| Subject: Re: Exchange 2003 - Routing Group connector
| Date: Fri, 29 Feb 2008 19:24:10 +0800
| Lines: 194
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| Message-ID: <#FlceWseIHA.5984@TK2MSFTNGP06.phx.gbl>
| Newsgroups: microsoft.public.exchange.connectivity
| NNTP-Posting-Host: 203.115.247.206
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.connectivity:3614
| X-Tomcat-NG: microsoft.public.exchange.connectivity
|
| Yes, the way to create RGC is correct, as we have that running for other
| branches connection with HQ server.
|
| I have check the "Access this computer from the network Properties" and
| "User" in fact "Everyone" is in.
|
| The problem is kind of weird that the branch can send email to HQ
Exchange
| via the RGC created, but not the other way round.
|
| thanks again in advance for any thoughts...
|
|
|
| "Terence Liu [MSFT]" wrote in message
| news:a3YXUBseIHA.4720@TK2MSFTNGHUB02.phx.gbl...
| > Hello Customer,
| >
| > Thank you for posting here.
| >
| > According to your description, I understand that the Routing Group
| > Connectors between the Head Office and branch office not work. If I have
| > misunderstood the problem, please don't hesitate to let me know.
| >
| > Based on my research, I think the corrupted Routing Group Connectors
| > configuration may related this issue. I suggest we try the following
steps
| > to see if we can resolve this issue:
| >
| > I. Please ensure you create the Routing Group Connectors correctly in
your
| > Exchange 2003. Please go thru the following KB:
| >
| > HOW TO: Use Routing Group Connectors to Connect Routing Groups in
Exchange
| > Server 2003
| > http://support.microsoft.com/?id=822929
| >
| > Note: please clean the old Routing Group Connectors on both sides and
| > recreate a new one.
| >
| > II. This problem may occur if the Authenticated Users group has been
| > removed from the Access this computer from the network user right.
| >
| > To resolve this problem, grant the Authenticated Users group the Access
| > this computer from the network user right. To do this, follow these
steps:
| >
| > 1. Click Start, point to Programs, point to Administrative Tools, and
| > then
| > click Local Security Policy.
| > 2. Expand Local Policies, and then click User Rights Assignment.
| > 3. In the right pane, double-click Access this computer from network.
| > 4. In the Local Security Policy Setting dialog box, look for
| > Authenticated
| > Users in the Assigned To list.
| >
| > If this item does not appear in the list, add the Authenticated Users
| > group. To do this, follow these steps:
| >
| > a. Click Add, type authenticated users , click Check Names, and then
| > click
| > OK.
| > b. In the Assigned To box, click to select the Local Policy Setting
check
| > box that is displayed next to Authenticated Users.
| > c. Click OK.
| >
| > 5. Exit the Local Security Settings MMC snap-in.
| > 6. Update the local security policy on the computer. To do this, click
| > Start, click Run, type secedit /refreshpolicy machine_policy /enforce ,
| > and
| > then click OK.
| > 7. Follow steps 1 through 6 on every computer that is a member of the
| > routing group to verify that the Authenticated Users group has the
Access
| > this computer from the network user right assigned.
| >
| > If we cannot resolve the issue after we perform the above steps, please
| > help me collect some information for further investigation:
| >
| > Do you get any event error about the Routing Group Connectors?
| >
| > I hope these steps will give you some help.
| >
| > Thanks and have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on exchange technical issues. If you have
| > issues regarding other Microsoft products, you'd better post in the
| > corresponding newsgroups so that they can be resolved in an efficient
and
| > timely manner. You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
| > the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
| > doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
| > --------------------
| > | From: "yhyap" <yhyap@newsgroup.nospam>
| > | Subject: Exchange 2003 - Routing Group connector
| > | Date: Thu, 28 Feb 2008 13:53:49 +0800
| > | Lines: 47
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| > | X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| > | X-RFC2646: Format=Flowed; Original
| > | Message-ID:
| > | Newsgroups: microsoft.public.exchange.connectivity
| > | NNTP-Posting-Host: 203.115.247.206
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.exchange.connectivity:3602
| > | X-Tomcat-NG: microsoft.public.exchange.connectivity
| > |
| > | Hi there,
| > |
| > |
| > | Appreciate someone could give me some hint on the solution.
| > |
| > |
| > | We have few Exchange servers in branches that all connected to HQ
| > Exchange
| > | server via Routing Group Connector. All emails among the branch
offices
| > and
| > | from External are delivered from HQ Exchange 2003 to the branch
Exchange
| > | 2003 server.
| > |
| > |
| > | Recently Branch-A patch their Exchange server 2003, and after the
patch
| > the
| > | Routing Group Connector between branch-A and HQ stop working. We
thought
| > it
| > | is due to patch problem, therefore we uninstall patch, still probelm
| > | persist. Then we rebuild the server from OS level and reinstall
Exchange
| > | 2003 without any further patching, it still problem.
| > |
| > |
| > | We then setup another Exchange 2003 server on separate hardware into
| > same
| > | SITE, and use that new server only for Routing Group connection to
HQ,
| > it
| > | works perfectly.
| > |
| > |
| > | We are running out of idea, and the only think one that we suspect is
| > | possible due to the server name, as when we rebuild the existing
| > problematic
| > | server, we use back the same server name. If this the problem, how
can
| > we
| > | get that corrected ?
| > |
| > |
| > | When we force the Routing Group connection from HQ Exchange 2003 (from
| > | Exchange Systems Mgr -> Queues) we can see from the network the SMTP
| > traffic
| > | passing, and sametime when we perform telnet port 25 from HQ Exchange
we
| > | notice a response from Exchange 2003 in Branch-A. So network is not a
| > | problem.
| > |
| > |
| > |
| > | We struggle for a month, and I really hope I can get something before
we
| > | perform another rebuild of the Exchange 2003 again.
| > |
| > |
| > |
| > | thanks in advance
| > |
| > |
| > |
| > |
| >
|
|
|
date: Mon, 03 Mar 2008 09:42:17 GMT
author: (Terence Liu [MSFT])
|
|
