Search results for query: *

Steve, I never did find a solution. And since I've recently lost that job, I won't be trying the above suggestions. I'll pay more attention to what I play around with next time though. :) Tough luck to my old boss. Good luck to you tomorrow though.

I think I read somewhere that MS recommends that Exchange and the GC be on separate servers, if possible of course. I don't recall any rationale given for this recommendation though.

Ok then, either enable circular logging or let your backup software clear the logs.

Can you tell which server is generating the rejection? The complete error message should give clues. If it's the recipient's, go to www.dnsstuff.com and enter your mail server's address in the spam database lookup. "Mail rejected by server" sounds like an anti-spam tactic. If it's...

I bet "not able to establish..." is not the complete error message. If the PIX doesn't fix it, get the complete error message (if possible). Sounds like the time-out issue I and a few others have had recently.

Double check that Exchange does NOT have DNS configured. Even if it has entries that are correct, remove them. Default SMTP virtual server properties - Delivery Tab - Advanced Button - Configure External DNS servers.

I'm not sure if it was clear before, but don't do anything with the M drive. Don't check their email that way. Forget you ever saw an M drive.

Were those queues there an hour ago? If they're still hanging around since before you closed the relay, you can either delete them yourself or wait for them to terminate. If you're not sure, delete them yourself and keep an eye on it. Just because they're there doesn't mean you're still relaying.

Check out the mailbox manager. A search at support.microsoft.com should yield a wealth of info.

Can't answer your question, but fundamentally you have a bigger problem: One or two 5MB files should not use up all the empty space on your C: drive (whether they're Exchange log files or anything else). In other words, your C: drive is already too full. Move your log files to another partition...

You're hosed. In the future, backup the exchange databases and forget that the virtual M: drive even exists. Do not click on it. Do not scan it for viruses. Do not let your system do any routine tasks on it.

If something can't complete in the time specified, why not increase the amount of time specified? "Default SMTP Virtual Server" properties - General Tab: Connection Time-out (minutes). I recently had a single recipient I could not send mail to. Increasing this time-out value (as well...

You need some sort of front-end that bypasses/does not talk to the filesystem. Citrix comes to mind, and I don't exactly know how it could be made to work, but I imagine there are cheaper/more effective alternatives.

If the users had local admin rights prior to joining the domain, you will have to go to each machine and make their domain login a local admin. Prior to joining the domain is was their local login that had the local rights - separate from their new domain login. The alternative, as above is to...

Use Exchange Manager. Servers/<servername>/Protocols/SMTP/Default SMTP Virtual Server/Queues

And as soon as I said I wanted to wait for the supposed &quot;update&quot; to Entourage, management says buy it now. As for my setup problems, everything is very straightforward. It just didn't work the first time for either machine. The exact same settings had to be typed one or more times.

Don't use the external address of your webmail host when you're inside the network. Either use the NETBIOS name or the internal IP address (i.e. http://192.168.1.5/exchange). I even wrote a simple webpage that detects the host's IP address and redirects accordingly.

So if I'm reading #2 correctly, your internal email accounts can send mail to anyone, but cannot receive from external accounts? If this is true, the forwarding should not work from an external id to the internal id. It should only work from one internal id to another. If this is not true...

I've got 2 clients with OS9 & Office 2001. They get email fine, but appointments don't work. Setup can be a nuisance, but it eventually works. Appears to be as reliable/stable as anything else on the Mac, which is not all that stable in my opinion. If I recall, users also do not have PST...

I had this problem FOREVER with ArcServe 2000. Moved to Veritas last month and I love it. Sorry, doesn't help you though.