Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

smtpsvc error 4000

7 views
Skip to first unread message

MSNews

unread,
Oct 4, 2009, 4:29:52 PM10/4/09
to
We have setup smtp iis6 on several XPsp3 boxes for progams to use
internally. It should send mail to our internal exchange 2003 server, but
they all get the connection dropped and messgaes stuck in local machines
queue folder.
I checked our exchange config and nothing is blocking these IP
addresses(internal) DNS is good and I can telnet into exchange server from
any of these boxes and send mail. Is there a problem with the format or
anything? I can send mail to my gmail account from any of these. any
explanation appreciated

regards

Craig

--


Sanford Whiteman

unread,
Oct 4, 2009, 7:08:21 PM10/4/09
to
> I checked our exchange config and nothing is blocking these IP
> addresses(internal) DNS is good and I can telnet into exchange server
> from any of these boxes and send mail.

How are you routing from the IIS SMTP installs to the main mailbox server
-- DNS MX or hard-coded Remote Domains?

If you're using DNS, have you ensured that the IIS boxes get the private
IP address of the mailbox server instead of trying to do a loopback NAT
through your firewall (which can often trip up such setups).

-- Sandy


------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
------------------------------------

MSNews

unread,
Oct 4, 2009, 9:32:46 PM10/4/09
to
These are smtp boxes in the same network/domain. All have Static IP with
DNS and RDNS.
Our programmers wanted to use this to send notifications when there was a
program error. I doubt if routing or NAT would effect this behavior.

thanks


"Sanford Whiteman" <swhitemanlis...@cypressintegrated.com> wrote
in message news:op.u1as77vb6c17zw@gw02...


>> I checked our exchange config and nothing is blocking these IP
>> addresses(internal) DNS is good and I can telnet into exchange server
>> from any of these boxes and send mail.
>
> How are you routing from the IIS SMTP installs to the main mailbox

Sanford Whiteman

unread,
Oct 4, 2009, 11:11:49 PM10/4/09
to
> These are smtp boxes in the same network/domain.

Exactly.

> I doubt if routing or NAT would effect this behavior.

Take IIS box at 192.168.1.3 and Exchange at 192.168.1.4.

Exchange NATed to public IP 1.2.3.4.

DNS MX RR for example.com points to exchange.example.com. DNS A RR for
exchange.example.com points to 1.2.3.4.

When 192.168.1.3 tries to send to us...@example.com, it will attempt to
connect to 1.2.3.4. Enterprise firewalls will not allow that transit.

It's in fact a common problem that calls for either split DNS (internal
copy of the zone that serves private IPs) or hard-coded mailroutes (Remote
Domains in IIS SMTP).

-- Sandy

MSNews

unread,
Oct 4, 2009, 11:41:59 PM10/4/09
to
Thanks, I'll verify that the internal DNS settings are correct.


"Sanford Whiteman" <swhitemanlis...@cypressintegrated.com> wrote
in message news:op.u1a4hzaf6c17zw@gw02...

MSNews

unread,
Oct 6, 2009, 2:12:42 PM10/6/09
to
Solved. DNS was good. I loaded an opensource smtp server and mail flies
right thru no problems
I think there is an issue with XPsp3 IIS6 smtp services- I just wont use
that anymore in the field

regards


"Sanford Whiteman" <swhitemanlis...@cypressintegrated.com> wrote
in message news:op.u1a4hzaf6c17zw@gw02...

Sanford Whiteman

unread,
Oct 6, 2009, 2:24:32 PM10/6/09
to
> I think there is an issue with XPsp3 IIS6 smtp services- I just wont use
> that anymore in the field

Up to you if you want to use it, but there's no reason to believe there is
a bug without proof. The setup you describe is eminently easy to do with
IIS SMTP and is likely in place in hundreds of thousands of developer
installations. I relay through XPSP3 IIS SMTP every day.

MSNews

unread,
Oct 6, 2009, 3:13:57 PM10/6/09
to
Thank you and understood but time is a factor and we dont have time to get
something that doesnt work to work, when we have another free product that
works as is.

thanks for taking the time to reply !!

Carli
"Sanford Whiteman" <swhitemanlis...@cypressintegrated.com> wrote
in message news:op.u1d5e6146c17zw@gw02...

Sanford Whiteman

unread,
Oct 6, 2009, 3:23:27 PM10/6/09
to
> Thank you and understood but time is a factor

That's a very good reason to stop troubleshooting... but not justification
to claim there is a defect in the product. Sorry to be harsh, but I take
very seriously the concept that there's a bug in something so basic that
has been in continuous use for 6 years all over the Windows community.
The burden o' proof is on you to create a controlled, technically fluent
experiment before publishing stuff like that for the whole world.

-- Sandy

0 new messages