Search results for query: *

Ok. Since we are having a Plato-type discussion which fails right at the beginning, I am out. Good luck with your installation. Cheers.

anonim1: read this post about the certificate install. note what he says about being on the domain. it is true...

anonim1: are you using the domain/username format for authentication? I made my own certificate and it indeed needed to be installed by joining the domain. It will not automatically install the correct cert just by connecting to the server via https. Perhaps your set up is different...

Andy...the client computer must have the certificate installed. The certificate is installed by joining the domain. Are you telling me that your remote clients are not joined to your AD domain? Anonim1: Okay, to check the settings on that certificate, open your IE 6 browser and select...

Okay. For starters anonim1, read this: http://support.microsoft.com/?scid=http://support.microsoft.com%2Fservicedesks%2Fwebcasts%2Fen%2Ftranscripts%2Fwct061604.asp In this document, the presenter explains the rpc-http tab addition and the "not part of an Exchange managed rpc-http topology"...

hehe. Okay, first of all, you must connect and configure your email clients on your local network before trying to connect via https. It will NOT work if you do not follow this basic step. The document you are referring to is incredibly inadequate. The steps involved in getting this thing...

Would you mind giving me a test email address with the FQDN of your email server? I could do some basic tests for you. If I had to guess, you may have some sort of anti-virus/anti-spam application running which is quarantining the email from those "problem" domains.

Check this post for confirmation. It should be simple, though I have never done it myself. I would get a new sales guy. http://www.webservertalk.com/message897317.html

In case you need confirmation, don't worry about trying to defrag, etc. Get the Enterprise edition and don't look back. The same thing happened to me years ago and it was a nightmare. We actually had to download the TRIAL version of Exchange 2000 Enterprise and use that to get the latest...

anonim1: I have this setup working and you apparently have a bad configuration on your RPC-HTTP tab. For a single server, you are supposed to have "not part of an exchange managed topography" selected, not the backend one. You may want to recheck this on your side.