RE: Routing Connectors
- From: "Kamire, Thomas" <Thomas.Kamire@xxxxxxxxxxxxxxxxx>
- To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
- Date: Mon, 21 Mar 2005 19:59:45 +0300
I am having one server in Nairobi and another in London through a vpn. I am
having the error below:
An RPC communications error occurred. Unable to bind over RPC. Locality
Table (LTAB) index: 15, Windows 2000/MTA error code: 0. Comms error 0, Bind
error 1722, Remote Server Name HDQEXCHANGE001 [MAIN BASE 1 500 %10] (14)
I have configured routing group connectors. I do not think I will use smtp.
_____
From: Manjeet Singh [mailto:Manjeet.Singh@xxxxxxxxxxx]
Sent: Monday, March 21, 2005 4:26 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Routing Connectors
http://www.MSExchange.org/
Could you please explain more about your exchange setup and how you are
trying to connect?
Consider the below fact -
- If you have two exchange servers then there is no need of any
connector.
- If you have two routing group then it is good to use the RGC
connector
- RGC (routing group connector) is Microsoft propitiatory and can
be used between two exchange 2k and servers.
- You can use the SMTP connector to connect two exchange servers,
and you need to define the bridge head and other settings.
- If you are trying to connect to exchange 5.5 or any other which
is running X.400, then you can use the X.400 connector to communicate.
- If you are trying to connect to exchange server which are in
different forest, then you must have send as/receive as permission on the
exchange organization to send and ecive the mails.
Let me know with the error message you are getting.
Thanks,manjeet
_____
From: Kamire, Thomas [mailto:Thomas.Kamire@xxxxxxxxxxxxxxxxx]
Sent: Monday, March 21, 2005 9:42 PM
To: [ExchangeList]
Subject: [exchangelist] Routing Connectors
http://www.MSExchange.org/
I would like to know how to connect to other exchange servers in the
exchange enterprise. I have tried connecting to the first exchange server
but it cannot be reached.
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
Manjeet.Singh@xxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
thomas.kamire@xxxxxxxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
DISCLAIMER:
This message and any attachments are confidential and may be legally
privileged or otherwise protected from disclosure. Although the necessary
precautions have been taken, Kenya Airways does not accept legal
responsibility for any damage whatsoever that is caused by viruses being
passed or for the contents of this message.
This message, and any attachments, are intended solely for use by the named
addressee. If you are not the intended recipient, you must not copy them or
disclose their contents to any other person. If you have received this
message in error, please notify the sender by return e-mail and delete any
attachments accompanying it immediately. "PLEASE NOTE THAT OUR OPERATOR
NUMBER HAS CHANGED TO - +254-20-642 2000"
DISCLAIMER:
This message and any attachments are confidential and may be legally
privileged or otherwise protected from disclosure. Although the necessary
precautions have been taken, Kenya Airways does not accept legal
responsibility for any damage whatsoever that is caused by viruses being
passed or for the contents of this message.
This message, and any attachments, are intended solely for use by the named
addressee. If you are not the intended recipient, you must not copy them or
disclose their contents to any other person. If you have received this
message in error, please notify the sender by return e-mail and delete any
attachments accompanying it immediately. "PLEASE NOTE THAT OUR OPERATOR
NUMBER HAS CHANGED TO - +254-20-642 2000"
Other related posts:
