Search results for query: *

If both IMS's are configured the same, the mail will always go out the first server because it is the least cost route with all mailboxes on that server. If there is a problem, mail will simply build up in its queues. The IMS is not "tied into" the MTA the way a Site Connector is...

2 servers in the same site talk to each other constantly. 9318 means that your new server is still trying to contact the old one, but is not getting an answer. Search technet for the article about removing the first server in a site.

Sounds like an RPC problem. Use the utility rpcping on the Exchange CD. Should be a KB article on how to use it. Not all routers will pass RPC traffic. Also look for article about TCP ports and Exchange. You may need to statically map some ports.

MS makes something called the InterOrg Tool. Sometimes it works. Don't know if it is meant for 5.5 to 2000. Compaq has a $20,000 tool called LDSU. Regular directory export/imports. For mail: if both were 5.5, IMS Connections tab, Specify by email domain, Forward to host to each other's ip...

Try it from the server side. Set up a custom recipient for the home address, then on the mailbox, set that as an alternate recipient. Another thing to check: in Site Addressing, Routing. See if you have more than one listing for SMTP. This could happen if you have more than one server in...

Sounds to me like you need to install the Internet Mail Service. File>New Other. Just take all the defaults to set it up. Then visit www.swinc.com, they have a good section on internet mail with Exchange. And there is plenty on MS site.

Aside from MS site, try www.swinc.com. They have a tutorial.

The IMS has a key in the registry along with all the other services (HKLM\System\CCS\Services). It's config info is also in the directory. I would think the IMS would be the least of your worries. Just take screenshots and set up the new one the same as the old.

These files are in the mtadata directory. They have nothing to do with your databases. When the mta processes messages, it creates .dat files as it needs them, but it does not delete them when done. It saves them in case it needs them again. The designers of the mta thought this would be...

As for how to do it, install the new server in the same site (using the same service account). Install the IMS on the new server. Replication will take care of the rest.

The migration wizard should do what you need. There's a whitepaper here: http://www.microsoft.com/exchange/techinfo/administration/55/default.asp

Same as NT: ipconfig /release ipconfig /? shows all switches

The server you are communicating with is an smtp server. Exchange is an esmtp server. It begins a session by saying EHLO. An smtp server does not recognize this and asks for a HELO instead. Usually Exchange realizes this and changes to HELO, but some servers ask for the HELO in a way that...

You need to change from Do not reroute to Reroute on the Routing tab of the IMS.

No, you can not have 2 IMS's on one server. However, you can easily use one to receive for 2 domains. On the routing tab, simply add the second domain, route to inbound. The users for the second domain will have to have their smtp addresses modified on their mailboxes.

Run Performance Optimizer, and let it move things around for you.

In 5.5 it is eseutil. It's located in system32, and can be run right from the C prompt.

The items in these directories are copies of messages that have passed through the IMS. The way they got there is by having Message Archival set on Diagnostics Logging tab of IMS. You can open them in Notepad, but of course you won't be able to view attachments. Unless you have some business...

Piece of cake. IMS properties, Diagnostics Logging tab. Set Message Archival to None, stop and start IMS. While you're in there, see if you have SMTP Protocol Logging enabled. That writes logs into the imcdata\log directory (files start with L0000x). This can take up lots of space too! All...

Don't know why, but your MTA is hosed. The last event you list is a 2152, which means some or all of your core .dat files are missing or corrupted. It is extremely difficult to recover from this without losing data (call Microsoft, and they probably won't suggest even trying). But it is easy...