Sorry, it's my first post, I didn't know what all you needed. I'll try
to answer you're questions better this time.
That's OK. For the future, the following would really help us to help you
i.e. you'd probably get an anwer much more quickly...
1) Make the subject of your post descriptive
2) Briefly mention the software you're using - that's especially important
if you're not using the latest versions, because we'll assume you are unless
you say you're not.
3) Explain what you're trying to do
4) Describe how you've tried to do it
5) If you're getting errors, tell us what they are - the more information,
the better.
6) Provide as much of the code as is relevant - especially the bits where
the error occurs...
This is what I was using, I actually took the the sample directly from
the "How do I send a simple Html email?" section (changing the email
addresses and host name). I tried using both the IP address and the
actual name of the exchange server but neither worked.
OK.
I figured that since I used the code on the systemnetmail.com page that
the code was fine, meaning the problem must be with iis or exchange. I
could easily be wrong though, I've never used the System.Net.Mail
classes and have no iis/exchange experience (this is my first asp.net
project)
From what you've said, I doubt very much that there is a problem with your
Exchange server - if there was, your network admin would already know about
it.
How do I check if my webserver can see the Exchange server?
Well, first things first. Log on to the webserver and try to ping the
Exchange server. I'm assuming (because you have not said the contrary) they
both servers are on the same network.
Our network admin said that no authenication is required, but I still
tried using
"smtp.Credentials = new NetworkCredential("userid", "password");" with
a valid username and password and it still failed.
Hmm - OK...
It throws a System.Net.Mail.SmtpException with message "Failure to send
mail" with an inner exeption System.Web.MailException with message
"Unable to connect to the remote server"
Ah! Now we're getting somewhere...
That message doesn't *necessarily*
indicate that the webserver can't actually connect to the remote server (but
do the ping test just to be sure), but certainly does indicate that
*something* is getting in the way of the mail process.
Are you using McAfee Anti-Virus software...?
