Continue reading »]]> So your Exchange Server has been running fine for months and all of a sudden it doesn’t want to send or receive external emails.

All else seems OK, the stores are mounted, you can telnet in externally, you can telnet externally.

You could be running into an issue with E2007 once the C:\ drive get below 3GB* E2007 will simply stop receiving/sending e-mails.  There’s not warning to this, no errors, noting in the event logs.

So here’s how to confirm this issue, the obvious answer is if you have less than 3GB* of space on your C:\ drive free some space, 5GB or more, restart the exchange services and see if mail comes in.  If you want to confirm this is the issue, then you need to the following:-

telnet mail.theirdomain.com 25
when you get the 220 line, send it this command:
helo whatever.com
when it replies, send it this command:
mail from: joe@whatever.com
when it replies, send it this command:
rcpt to: someone@theirdomain.com
when it replies, send it this command:
data
when it replies, send it this command:
subject: test
type some more stuff
whatever you want
end with enter then period then enter

if during this process you see the following error:

452 4.3.1 Insufficient system resources

That’s your issue… go free up some space and restart the exchange services, Information Store and Mail Submission worked for me.

* I haven’t been able to confirm at what disk space E2007 will decided to stop sending/receiving mail.  I have observed 3GB or less, but it only starts working with 5GB or more free.

Continue reading »]]> If you have created a A record called remote (for example) on your domain name to make it easier for users to access RWW (remote web workplace) from home, you will notice of course that this doesn’t work internally.  This can cause issues with Exchange Active Sync devices that you may have configured to connect to the the server using remote.domain.com and this works great when external from the internal network.  It doesn’t work when the device is within the network the and connected via Wi-Fi. 

Also this can become difficult when configuring OWA (Outlook Anywhere) for Outlook.  As the domain and the certificate has to match you can’t install the certificate because the domain doesn’t match internally if your using http://servername/.  This resolves that issue and keeps things generally orderly.

Oh, this video actually features me.  Sorry about the erms and pauses.   Hopeful the more of these I do the better I will get. 

DISCLAIMER:  Please use this advice at your own risk.  I have tested it in the lab (read virtual machines) and in production environments and I’ve had no issues.  Be careful.