Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

X.400 1

Status
Not open for further replies.

teckystuff

Technical User
Jan 26, 2006
289
ZA
Here's a potential stupid question. Why do I get X.400 events in event viewer if I dont have any X.400 Connectors?

My knowledge with Exchange and connectors is shoddy at best. The network I inherited is a multi site Exchange 5.5 network which seems to have been setup with no connectors, ie they are all in the same site. Problem is the servers are actually across very crappy slow links, 64k and up.

Am I understanding this wrong?
In my connections container I only have "Connectors for cc:Mail" of which we have no lotus products at all and "MS Mail Connector" of which I dont think we use at all. There are no X400 connectors listed here.

*****************************************
Your mouse has moved - reboot for changes to take effect
 
I can't explain why you are getting entries in your log without knowing what the entries are. If they're not affecting the operation of the system, I woldn't worry about them.

With slow links between your physical sites, you would have been better off setting up individual sites and using X.400 connectors between them. X.400 is the protocol of choice with slow WAN links.

When all else fails, read the book!
 
Yup that was what I was thinking too. Do you know if there is a limit to how many servers you can have in a "site" - i.e that all connect via RPC without connectors.

*****************************************
Your mouse has moved - reboot for changes to take effect
 
I think there is a technical limit, although it's higher than the practical limit you'll face. I've run a site with 20 servers in it before with no problems, although it was based on a fast LAN. Running a 5.5 site over slow WAN links is definitely not a good thing.
 
Yeah thats the problem I have at the moment. 24 servers all in the same site but over very crappy slow links. *sigh*
Inherited network. nuff said. Still waiting impatiently for my AD/Exchange upgrade project to be approved. *sigh*x2
Thanks ZB

*****************************************
Your mouse has moved - reboot for changes to take effect
 
Teckystuff...It sounds like you are using 5.5 and looking to upgrade. I just upgraded my 5.5 server to PostPath and it is fantastic. It's a linux based product that works with MAPI clients and basically does everything Exchange does natively and it was a simple upgrade. I decided to go this route instead of going to 2k3 or even the fork lift 2k7 upgrade. Just though i would share this info with you.
 
Thanks Techone but I have already spend countless hours on my AD/Exchange upgrade proposal which amounts to a multi million bucks upgrade (all new hardware/software/Licenses included)
Its sitting with management awaiting approval - where its been for months now. Worst part is it seems I wont even get to see the fruits of my labour as I will probably move on from this job before it ever happens. Pity.

*****************************************
Your mouse has moved - reboot for changes to take effect
 
Sure thing. Though I would add my 2 cents. We actually saved quite a bit of money going to PostPath instead of exchange, but our upgrade was not in the millions!!! Good luck with your project and your move ;-)
 
Having 24 x.400 connectors shouldn't be an issue. The tricky part is determining how they should be interconnected. If there are no connections between your separate physical locations, then just have all the traffic flow through your primary server. It's a little slow, but it's reliable.

When all else fails, read the book!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top