Re: Can't change password for outbound mail!

Update: I don't use ISA. I have 1) reconfigured Exchange to use port 2525,
and have made sure that 2) our router/gateway's NAT firewall has port
forwarded 2525 to our server, and 3) our firewall on the server allows
traffic in both directions on port 2525.

Still no success. Same problem.

-- Jim

"Lanwench [MVP - Exchange]" wrote:

Jim <Jim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
OK -- I set up the dummy account in OE, and sent a test message to my
AT&T hosted email account. The following error message was generated
in Outlook Express:

"The connection to the server has failed. Account '[our SBS server
name]', Server: 'outbound.mailhop.org'. Protocol: SMTP, Port 25
Secure (SSL): No, Socket Error 10060, Error Number 0x800CCC0E"

-- Jim

Perhaps your ISP blocks outbound connections on port 25. This clearly isn't
an Exchange issue at this point. If you use ISA, that could also be a
culprit (I'm not an ISA person, tho).

As mentioned, I use MailHop Outbound all the time & have had no problems
with Exchange & it interacting.

"Jim" wrote:

To clear things up: I'm testing by sending mail from my local
Exchange hosted mailbox to my remote AT&T email account (I can
receive mail just fine -- I just can't send it).

I'll set up the dummy account in OE, and post after that step.

Just to be clear -- I have disabled TLS, but we still can't
authenticate with DynDNS's outbound mail server. DynDNS's website
suggests that TLS isn't a problem, however, and recommends enabling
that feature.

Finally, I'm using DynDNS to smarthost our outbound mail because out
ISP will not allow us to relay mail through their mail server
without upgrading to a more expensive static IP business account.
We're a small shop, and we don't generate or receive that much email.

-- Jim

"Lanwench [MVP - Exchange]" wrote:

Jim <Jim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Update: I disabled TLS, same problem, same message in the Queue
(remote server did not respond, etc.).

I have an external email account hosted by AT&T that I'm using to
test outbound mail from our SBS.

I'm not sure what that means. Send from a mailbox on your Exchange
server, not your AT&T mailbox.

Do you think that setting up a dummy
email account in Outlook Express will add anymore information?

Yes - I think it will let you know if there are problems with more
logging. Do you *have* to use a smarthost for some reason?


Shouldn't the number of characters in the password field match the
character length of password which I have inputted under "basic
authentication"?

No....

Since the number of masked characters is greater
than the length of our password (even after I have entered the
correct password) -- I suspect that SBS is not letting me change
the password, and hence leading to the failure to authenticate
with the remote outbound mail server.

No, the number is irrelevant.

I really appreciate your attention and help. Thank you so much.

-- Jim

"Lanwench [MVP - Exchange]" wrote:

Jim <Jim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I reset the IIS virtual SMTP properties to their default and
re-ran the CEICW.

Cool beans. But this isn't IIS - you manage all this in Exchange
system manager, although I know what you mean. :-)

Then I visited the SMTP connector settings in the
Exchange Settings Manager; plugged in the correct user ID and
password in the "basic authentication" field, enabled TLS (which
is supported by the smarthost),

Did you test without TLS, as well?

clicked OK & Apply. Fired off a test
email, and it did not reach the smarthost's outbound mail server.

Checking the "Queue" -- the message says that "the remote server
did not respond to a connection attempt."

Thank you for your collective help and attention. I really
appreciate your time.

Try setting up a dummy email account in OE to use the same SMTP
server & credentials, and see what happens.


-- Jim

"Dave Nickason [SBS MVP]" wrote:

I would either up the SMTP logging, or check with the tech
support at the smarthost. My guess is that the number of dots
or asterisks that show in the password box is the same
regardless of the password.

Did this previously work?

"Jim" <Jim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:75CAF162-88E6-4F12-B07D-E6EA512C5582@xxxxxxxxxxxxxxxx
Our server can receive mail but can't send it because it is not
communicating
the correct username and password to our smarthost's outbound
mail server. This is confirmed by checking the Queue in
Exchange under Server Management.

When I try to change the default username and password in
exchange manager (or under IIS under the SMTP virtual server
properties), under "basic authentication", I can change the
user ID, but I can't reset the password. (What happens is, I
type in the password to log into our smarthost's mail server,
and click "OK", but the default password does not change -- I
can tell by reopening the panel and counting the number of
password characters).

Please help! Has anybody seen this problem before? It's
pretty wierd, and
I've lost serious time trying to solve this problem.

-- Jim




.

Relevant Pages

  • Re: Exchange Name
    ... When Exchange is responsible for an e-mail domain, ... If a local recipient with that e-mail address does not exist, ... Configure the SMTP virtual server in Exchange to send mail with unresolved ... recipients to the Internet service provider's mail server. ...
    (microsoft.public.windows.server.sbs)
  • RE: DNS and Exchange issues
    ... with the Exchange Server after you have installed the patch 888619. ... XFOR: Telnet to Port 25 of IMC to Test IMC Communication: ... Start Exchange System Manager. ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: MSADC 8355 LDAP Result failed
    ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ... If you put Exchange on one, ...
    (microsoft.public.exchange.setup)
  • Re: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.setup)
  • Re: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.admin)