Exchange 2003: One user getting "No transport provider was available for delivery to this" several t

  • Thread starter Thread starter KingCronos
  • Start date Start date
K

KingCronos

We run Exchange 2003 in a WIndows 2000 domain. Most of our clients
(including the problem user) use citrix, so the setup for individuals
has little variation on basics such as Outlook 2003. One user
continually has problems sending out and several times a day
(sometimes much more), she is prevented from sending emails with
the error:


The following recipient(s) could not be reached:


John Doe on 20/09/2007 10:01
No transport provider was available for delivery to this
recipient.


I looked up the 'no transport' issue on Microsoft KB, and nothing was
really applicable except I thought problem contacts, but then the
user
told me that the last four times she received these NDRS, all she had
done was replied to messages that had been sent to her. The user can
usually re send the messages successfully later on in the day.


One thing I should also mention is that she is a remote user BUT, she
uses a DSL connection to get to her Citrix session, and therefore all
software and network connections are preferably running in the main
office.



Thanks in advance, C
 
The place to start is to find out how this user is addressing the e-mail
messages in question. Another thing to look at is how the Outlook profile
is configured.
 
Hi,

The mail profile is correct. We run a locked down Citrix system. Also,
often the user gets the problem even when she just replies to a
message she has received.

Any ideas?

Thanks
 
Repeating:

The place to start is to find out how this user is addressing the e-mail
messages in question.
 
Repeating:

The place to start is to find out how this user is addressing the e-mail
messages in question.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"








- Show quoted text -
Click to expand...

Im not sure what you mean by "how this user is addressing the e-mail
messages in question". On occasion she merely hits the reply button
after reading an email she has received, so the address was the same
as from where it was received, but the error still comes sporadically.
 
Is this internittent or is it repeatable with replies to the same
message(s)? Was this user migrated from a different Exchange system?
 
She was migrated from the old Exchange 2000 server to 2003, but so
were 500 other people and as far as Im aware no one else is having the
same problems. From what the user tells me it appears that this
problem is quite random, but that often messages she cannot send at
one point in the day, are successfully sent when she tries again at
another time. She is a remote user, but as she dials into the HQ
Citrix network via DSL, I dont see how this could make a difference.

Thanks
 
Her mailbox was on the old Exchange 2000 server, and we moved it
(along with 500 hundred others) on to the new Exchange 2003 server
using the Exchange task wizard.
 
The Move Mailbox Wizard? If you moved the mailbox this way, which would not
be what is typically called a migration and is that's why I asked, then she
should not see any difference in behavior after the move than she saw
before. Everything should be preserved in a move mailbox. So, the next
direction I would ask that you follow is to try to find out anything that
might have been differently for her. For example, did she get married,
change her name, and did someone recreate her mailbox because or something
like that? Or, is there something unusual about her Outlook configuration?
 
Hi Ed,

I have just checked, and regrettably I gave you some incorrect
information. I thought she was a long term user, but apparrently she
only joined August last year, which was after we had already migrated
to Exchage 2003, so her mailbox was never on the old server. She has
not changed her name, as far as Im aware during this time - although I
have emailed her to confirm. Bizarrely enough, the mailbox was
recreated by myself about 6 months ago, which I tried as a 'nuclear
solution' as at the time she was having the same problems. It seemed
to get better for a while after this, but is now back to the way it
was. I have checked her Outlook configuration, and it is absolutely
ordinary.

Thanks.
 
One other thing. I used message trackling to see what was happening to
these delayed messages, and I noticed that the delay was before it got
to the email server. The delay seems to be between the Outlook client
and the Exchange server. Thanks.
 
There isn't also a POP or IMAP service specified in addition to the MAPI
(Microsoft Exchange Server) service in the profile, is there?
 
Back
Top