Search results for query: *

Have you tried running an ESEUTIL check on the database or even an ISINTEG to fix the corruption??? I'd do that before thinking that you have to restore from backup, because if this has been going on for a while, your backups are corrupt as well. Casbot.

You do not need to setup DNS unless you're going to DNS host your own domain. If your domain is hosted by some ISP, you just need to have them add your WWW and FTP records to point to your static ip address. Then just assign your Linksys the static ip and then use port forwarding to forward...

That's the long way of doing things if you logon as the user, assign the permissions and then add the resource to another person's profile. The easy way to do it is within the AD Users and Computers MMC. Simply configure your MMC to view the Advanced Features and then go to the Exchange...

I have the same issue. If you have your Exchange Server behind a firewall, then keep in mind that when traffic goes out to the internet, the traffic is being assigned your global ip address which may not be the same ip address as your MX record. The only way around it is to use your ISP's smtp...

Putting Exchange (any version) on a DC is BAD! Keep in mind that if you use the OWA feature of Exchange, you have to give the Domain Users group "Log on Locally" permission. Do you want Joe Blow to have the ability of logging onto a domain controller locally? I know I wouldn't...