• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 685
  • Last Modified:

Users / Devices cannot send mail through SMTP on Exchange 2007

Hello,

I have users and devices that are trying to send mail through out MS Exchange 2007 SMTP server, but connections are being rejected.

The Outlook client just keeps asking for the username and password regardless of how the authentication box is checked.

While I am fairly familiar with 2003, 2007 appears to elude me.  I'm not even sure where to begin looking...

- Chris
0
caw01
Asked:
caw01
  • 3
2 Solutions
 
djaburgCommented:
Is your exchange server part of your domain, and are your clients all users on the domain as well?  Or do you have a different kind of scenario?  If the computers are NOT part of the domain, then you need to specify the domain name as part of the username.  For example if your domain is domain.local and the user is bob, then you'd typically have to use domain.local\bob as the username and then the appropriate password.  What kind of connection errors are you getting?
0
 
caw01Author Commented:
Yes, exchange is part of the domain.  All SMTP user accounts are domain members with mailboxes on the server.

The computers or in some cases copiers are not necessarily domain members, but some are.  I am trying this from an outlook client now (that is on the domain) and the error is:

There was a problem logging onto your mail server. Your Password was rejected. Account: '192.168.25.56', Server: '192.168.25.56', Protocol: POP3, Server Response: '-ERR Logon failure: unknown user name or bad password.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92
0
 
caw01Author Commented:
wrong error...  Sorry...

Ok, so I tested this using the domain\username and it works.  However I am able to send mail both unauthenticated and authenticated.  How do I tell the server that I only want those users to be able to send mail through our servers if it is authenticated?

- Chris
0
 
caw01Author Commented:
AFter running through this endlessly...

We eventually found that on the receive connector, on the authentication tab, the Basic authentication had a checkmark in "Only offer Basic Authentication after TSL is started."  Once we unchecked that box, basic auth and pop were working just fine.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now