Search results for query: *

Exchange 2000 runs under the localsystem security context for this every reason. This supposedly means that admin account password changes don't affect the system - although there are more things than just exchange services that can use a stored password... see 5.5 procedure below for how to...

Does internal prompt for login credentials at all? Your post doesn't clearly indicate this. Just a guess, but this might be a problem with auth type. Internal computers probably have a security association through the domain, but as the servername doesn't match the authentication fails and...

Sounds like you might have urlscan installed but not confgured with the OWA template. Urlscan is commonly installed when you run the IIS lockdown tool. It can also be installed standalone. You have to replace the urlscan ini file with the special OWA template, otherwise some but not all of OWA...

There's no easy way around that one I can think of, but here's one little peice of advice - dont' set up 40+ accounts, set up 40+ security groups, each with you as the sole member and the webmaster@site#.com as the DL's email address. Then, grant each security group "send as" priv on...

If you need it to run without logging in then create a service using srvany.exe and instserv.exe. Both of these are Win2k resource kit tools that let you run almost anything as a service, and can be downloaded free from MS website along with easy instructions on use (run a search at either...

Sounds like you may not be pointing your network connection back at itself for DNS, which would allow proper registration on the local DNS server. Make sure your network connection is configured to point to itself for DNS (don't use loopback, use the static IP assigned to the server)...

Wait a minute - you are accessing OWA, installed on your Exchange server, attached to the internet, and with no firewall (nor NAT I assume)? Unless I'm missing something here I would be very worried about security if I were you.

I have no definite solution, but generally speaking you should NOT overwrite files on the first run, the logic being that skipped files can always be added later by reinstalling the service pack, but overwritten files are lost. As an inital troubleshooting step I would suggest you go back and...

Add a filter entry for your domain on the message delivery object under global settings. That way the server will filter inbound messages appearing to be from your domain. Note that this might break pop3 clients as well as any internal smtp delivery you do, and may cause problems if you have...

There are quite a few posssible causes, depending somewhat on your user's mail client. If this user is using a POP3/SMTP client, then he's probably got a configuration error on his client, or a bug, or possibly even just an unreliable link. Note that when sending via unauthenticated SMTP the...

You have to add the public folder to you public folder favorites first. Just select the PF, then go to FILE->FOLDER->ADD TO PUBLIC FODLER FAVORITES. Once it's added, you can set the entry under public folder favorites to sync. Make sure to choose the right options when adding the folder to your...

Also, if you are going to be receiving emails via smtp, make sure that "anonymous" has at least "create item" checked - nothing else is required.

You'd probably be better off with a mail-enabled public folder. This provides much finer control over access and visibility, and has most of the features of a mailbox plus some extras. What's it for?

Assuming that there's no relevant data currently in the server, AND if the server is named the same, AND the store is named the same, AND the database and transaction log paths are both the same, then all you need to do is shut down the store, remove all existing databases and transaction logs...

Those errors are just a generic side effect of the Exchange database not being mounted during the startup process. Reference the below MS article: http://support.microsoft.com/default.aspx?scid=kb;en-us;262456 If the database starts up normally during a manual mount but doesn't during system...

This may be overly-simplistic, but have you verified that the "do not mount store at startup" checkbox is cleared? (Store properties page, database tab) I recently wasted about an hour troubleshooting this only to discover that during a database recovery a few months earlier I had...