No transport available

  • Thread starter Thread starter C.S.Mager
  • Start date Start date
C

C.S.Mager

Hi,

I'm trying to add an internet-email account to Outlook 2000 on an
Exchange server. Whenever I try to send an email, it sends through
the Exchange server instead...

There is no 'send from' or such like. If I try removing the exchange
account and leaving only the internet-email account and using a pst
file, I still get the same message.

Anyone have any ideas? Sounds like some sort of restriction... but I
can't remember adding it, and I can't for the life of me find it!

Thanks

C.S.Mager
 
My advice - get rid of the POP and host your own mail. Your current
configuration is not supported in versions of Outlook prior to 2002, and is
not ideal even then. You will likely not be able to resolve the problems you
are having now, and you're sorta defeating the point of a centralized server
by relying on Outlook to handle Internet mail. Hosting your own domain's
mail will be a lot easier, mail will be faster, you'll be able to use OWA
and Out of Office, you can easily assign multiple addresses to each user,
can use mail-enabled public folders, publicly addressable distribution
lists/groups, and can scan all inbound/outbound mail for viruses using
Exchange AV software on the server.

See MSKB 245446 for info on the
No transport provider
error message, and a statement that this is not a supported configuration.

See http://www.msexchange.org/tutorials/MF002.html for instructions on how
to get Exchange 2000 to receive Internet mail sent via SMTP, the way it's
meant to do. For Exchange 5.5, see
http://www.exchangeadmin.com/Articles/Index.cfm?ArticleID=15729

You can do this even with dialup/ISDN (get an ISP who supports ETRN) .

If you have broadband but with a dynamic IP (such as a cable modem/ADSL
account):

You can use a dynamic DNS host such as www.dyndns.org - you set up an
account, such as yourcompany.dnsalias.com, and whomever hosts your public
DNS should set your primary MX record to point to yourcompany.dnsalias.com.
Open up port 25 inbound in your firewall or router, direct all traffic to
your internal IP for the Exchange server.
You run a service on your server (software available for download from the
dyndns website) and set it up to update dyndns with your current dynamic
IP.
 
Lanwench said:
My advice - get rid of the POP and host your own mail. Your current
configuration is not supported in versions of Outlook prior to 2002, and is
not ideal even then. You will likely not be able to resolve the problems you
are having now, and you're sorta defeating the point of a centralized server
by relying on Outlook to handle Internet mail. Hosting your own domain's
mail will be a lot easier, mail will be faster, you'll be able to use OWA
and Out of Office, you can easily assign multiple addresses to each user,
can use mail-enabled public folders, publicly addressable distribution
lists/groups, and can scan all inbound/outbound mail for viruses using
Exchange AV software on the server.

See MSKB 245446 for info on the
No transport provider
error message, and a statement that this is not a supported configuration.

See http://www.msexchange.org/tutorials/MF002.html for instructions on how
to get Exchange 2000 to receive Internet mail sent via SMTP, the way it's
meant to do. For Exchange 5.5, see
http://www.exchangeadmin.com/Articles/Index.cfm?ArticleID=15729

You can do this even with dialup/ISDN (get an ISP who supports ETRN) .

If you have broadband but with a dynamic IP (such as a cable modem/ADSL
account):

You can use a dynamic DNS host such as www.dyndns.org - you set up an
account, such as yourcompany.dnsalias.com, and whomever hosts your public
DNS should set your primary MX record to point to yourcompany.dnsalias.com.
Open up port 25 inbound in your firewall or router, direct all traffic to
your internal IP for the Exchange server.
You run a service on your server (software available for download from the
dyndns website) and set it up to update dyndns with your current dynamic
IP.
Click to expand...

Thanks very much for the advice! I have one problem though: I tried
doing something similar a while back, but then I gave up. The POP3
through Outlook 2002 works - but as you've just told me, it obviously
doesn't on 2000! Exchange is still useful as-is because it means that
I can open my emails wherever I am without worrying about sync
problems and corrupting pst files

I have an ISDN connection run through a router with automatic dialup,
but whenever I gave my exchange server access to the internet (i.e.
entered the gateway address in the IP settings) it dialed up all the
time for no reason (as far as I could see!) - is there any reason for
this? And can I stop it?

Thanks

C.S.Mager
 
Re ISDN - is that your only option for Internet connectivity where you are?
If you have a chance to get a leased line, DSL, cable, or something, do it.
But with the ISDN, it can be made to work, but clearly omething is prompting
it to dial....I'd post in a W2k/networking group on that one to see if
someone can help troubleshoot.

See if you can set up Exchange as I suggested and things will be much
better. Even if you upgrade everyone to Outlook 2002, it's still best to
centralize all your mail on the single server - much more efficient, much
easier to run AV scans, and you can use Out of Office.
 
Back
Top