B
Bill Bauman
Ok, so I was clearly frustrated when I made my initial post. 
I usually don't customize much in Exchange, as little as possible, really.
I was running E2k on Win2k AS SP3. A hardware failure rushed my upgrade to
the new server, E2k3 on WS03 Enterprise. As far as the authentication type,
well, it didn't change initially, but in efforst to just make things work, I
don't know where I am now.
How? What happens? Are your users connecting to Exchange via an Exchange
account or via POP3/SMTP?
I WANT to use POP3/SMTP. That's how things were working. It makes things
simple for me. I'll explore Exchange native in the future. I have been
using POP3.
What happens now is that POP is successful at authenticating. I installed a
Certificate Authority and am using POP SSL on port 995. I get a warning
every time I connect. That's all fine. We receive mail like champs. But
absolutely no configuration has solved my SMTP sending issue. When I try a
test, or when I configure in Outlook Express, I get a pop-up asking for
user/pass, type it in, pops back up, and there is no end to it until I
finally cancel 2 or 3 times in a row.
That was all with various settings of Authentication enabled in the SMTP
Virtaul Server. Also with and without checking Server Requires
Authentication on the client side. The only thing that seems to work is
disabling all Authentication except for Anonymous. In my Relay settings I've
configured Relay enabled for 192.168.1.0, my internal subnet, and I have all
clients VPN in before sending. This feels like overkill to me.
What's preventing the client from authenticating via SMTP to the server
either via Integrated Windows Auth. or Cleartext, or any of the sort?
I've actually had so many problems with this install of E2k3 I can't even
remember what was what. I am actively warning friends/colleagues not to take
the plunge at this point. I had to contact a colleague at Deloitte just to
figure out that POP wouldn't work without enabling Reversible Encryption on
the my domain GPO. What's up with that?
Back to the point, I guess. I would be MORE than happy to let an MS
representative VNC/RDP into the server and tell me what I did wrong. Heck,
I'd even write it up in layman's terms for the world to follow. If there's a
guide, I haven't found it. Several of the whitepapers from MS don't follow
at all, they say a-b-c, I do a-b-uhhh... what 'c'? I followed the RPC over
HTTP whitepaper, but ummm.. there's no RPC Virtual Directory. Go figure.
Help?
-Bill Bauman
I usually don't customize much in Exchange, as little as possible, really.
I was running E2k on Win2k AS SP3. A hardware failure rushed my upgrade to
the new server, E2k3 on WS03 Enterprise. As far as the authentication type,
well, it didn't change initially, but in efforst to just make things work, I
don't know where I am now.
How? What happens? Are your users connecting to Exchange via an Exchange
account or via POP3/SMTP?
I WANT to use POP3/SMTP. That's how things were working. It makes things
simple for me. I'll explore Exchange native in the future. I have been
using POP3.
What happens now is that POP is successful at authenticating. I installed a
Certificate Authority and am using POP SSL on port 995. I get a warning
every time I connect. That's all fine. We receive mail like champs. But
absolutely no configuration has solved my SMTP sending issue. When I try a
test, or when I configure in Outlook Express, I get a pop-up asking for
user/pass, type it in, pops back up, and there is no end to it until I
finally cancel 2 or 3 times in a row.
That was all with various settings of Authentication enabled in the SMTP
Virtaul Server. Also with and without checking Server Requires
Authentication on the client side. The only thing that seems to work is
disabling all Authentication except for Anonymous. In my Relay settings I've
configured Relay enabled for 192.168.1.0, my internal subnet, and I have all
clients VPN in before sending. This feels like overkill to me.
What's preventing the client from authenticating via SMTP to the server
either via Integrated Windows Auth. or Cleartext, or any of the sort?
I've actually had so many problems with this install of E2k3 I can't even
remember what was what. I am actively warning friends/colleagues not to take
the plunge at this point. I had to contact a colleague at Deloitte just to
figure out that POP wouldn't work without enabling Reversible Encryption on
the my domain GPO. What's up with that?
Back to the point, I guess. I would be MORE than happy to let an MS
representative VNC/RDP into the server and tell me what I did wrong. Heck,
I'd even write it up in layman's terms for the world to follow. If there's a
guide, I haven't found it. Several of the whitepapers from MS don't follow
at all, they say a-b-c, I do a-b-uhhh... what 'c'? I followed the RPC over
HTTP whitepaper, but ummm.. there's no RPC Virtual Directory. Go figure.
Help?
-Bill Bauman