Discussion Locked

No transport provider was available

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a small office with Exchange 5.5 and a few desktops. Email has been running fine. Recently, one client running Outlook 2000 on Win98 can no longer send email, all are returned; "No transport provider was available for delivery to this recipient." She can still recieve email and has network functions. Her computer also is the one that shares out Internet access via a DSL. Everyone else is OK, but I can't get email out. I check the server and there are no limits on messages. She didn't have personal folders, although I can see the .pst files, but adding anyone of them made no difference. I inherited this stuff and can't see anything obvious. Any ideas?

7 replies

by brasslet

There are lots of possibilities, as you'll see by a search in the MS Knowledge Base. I've personally seen this a couple of times, with different causes. Given that your client can't send out anything, my guess is the most likely cause is the Outlookinstallation is corrupt. Try uninstall/reinstall Outlook 2000. You can try simply reinstalling but in my experience, you might as well go all the way. Good luck.

by tomsal

Hi. I adminster our mail, I have dealt with this several times myself. Like the other poster who replied before me - they are right, there are more than one possibilities for this error. But breaking down the error "No transport provider" - when trying to send out email your user's machine can't grab hold of a connection to take the message. That's of course layman's terms of what's happening.

I have found it largely to be a bandwidth issue, as after my users get this and they wait - their mail goes through fine after there is less traffic on the Internet connection.

There is something I'd like you to check as well though if you the mail administrator. Go to your mail server and check how your mail gateway settings are set.

Though we have our own mail server and domain, our mail server is configured to bounce mail through uuNET's mail gateway if after 3 tries it doesn't go through our own gateway.

(Which is a good feature anyway...because some mailservers will reject mailfrom non-standard gateways....like AOL does for instance - it blocks some gateways (SMTP ports) )

Inform me of your sucess or failure with these ideas and we can take it from there if need be.

Good luck.

by chris hirst

First look at the connection settings for the Outlook client you will probably find that it is using the direct connection to the ISP rather than sending e-mail to exchange for delivery and the ISP's mail server is refusing what appears to be a mailrelay attempt ( the messages in outlook express are much better for this issue)

This discussion is closed to new replies.