Search results for query: *

Do you have SMTP relay agent enabled?

Do you have Deleted Item retention set? If so, you may need to disable it, run the ESEUtil and then reenable it. Here's an article: http://www.winnetmag.com/Windows/Articles/ArticleID/25649/pg/2/2.html

Is the Outlook 2003 profile using "Cached Mode"? If it's caching the Exchange information you'll run into problems communicating with the Exchange 5.5 server. Outlook 2k3 and Exchange 5.5 don't play nice together.

I wouldn't do it either as it could corrupt the database. Now, if you have the database files on a different drive (which is HIGHLY recommended), you can safely defrag the OS drive.

Go to your network settings and enable LMHOSTS lookup. Try those steps again.

The originating mail user must send messages to Exchange Server recipients in either MIME or Uuencode format.

TCO would be cheaper for an off site solution.

Doublecheck to make sure the SMTP relay agent isn't enabled. By default it is.

Yes, in order to be able to send mail to the internet the IMC must be installed.

Have users move emails to PST files. Run backup utility and run a FULL backup on your Exchange IS. This should delete the transaction logs and free up space. Implement some sort of archiving procedures, teach your users, adhere to them.

Try stopping and restarting the MTA

Set up separate Outlook profiles and require it to prompt the user for credentials.

Hosts file or LMHOSTS? There's a difference. You want to add it to the LMHOSTS because it takes the place of a WINS server. Outlook 2k3 still uses NETBIOS names for name resolution of the Exchange server. Go to a command prompt and type in "nbtstat -c" and check to see if the server and ip...

I had a lady who had a 2gb mailbox by herself. The IS was 6gb total. Needless to say, I set up mailbox limits quickly. Have everyone archive their messages to PST files on their local (or network) storage.

Can you ping the server? RPC ping? Try adding an LMHOSTS file to the users' laptop with the server name and IP address and use LMHOSTS lookup for name resolution, or use the FQDN of the Exchange server as the name for the Exchange server when you enter the users' name. Remember to turn off...

You'll need to contact Microsoft on this one. They'll have you go through several places to rename the HOMEMTA to the new Exchange server name. The IS "encrypts" the name of the HOMEMTA so that it can only be used on that one system: ie, you won't be able to move the IS to another server...

Are all the servers in the same organization/site? If so, they should be able to communicate with one another through RPC. If not, set up an X.400 connector between the two. You may want to try to removing the IMS and reinstalling it on the external box. Is there a firewall between the two...

Try sending a test message to the account. Even though you create the mailbox, the mail store isn't created until you send a message to it.