Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
The remote server returned an error: (440) Login Timeout RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    Incoming Status: Failure - The remote server returned an error: (440) Login Timeout.

     

    Get this when trying to set up the email routing, If I send email from withing CRM it reaches my queue and creates a case, but external email is not reaching the queue.

     

    Any help much appreciated.

     

    Monday, June 16, 2008 11:01 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Looks like you guys are working through it together. That's great. However, you should be able to get it to work via Exchange and not have to use a POP3 workaround. Again, the Test Access is a helpful tool. Also, I found that when configuring for Exchange, using https://server for Location/Server worked for me.

    Wednesday, June 18, 2008 3:45 AM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    You may need to play with your E-mail Router Configuration Manager a  bit. Once you have it properly configured, or think you do, go to the Users, Queues, and Forward Mailboxes tab. Load the data and then once it has, click on the Test Access button on the right to see if things are set up properly afterall. Hopefully this will give you a tool to resolve your problem.

     

    Tuesday, June 17, 2008 3:39 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    email router has been thoroughly played with and the only way I can now get it to work is if I use pop3, but would really like to use exchange.  its actually the router test that returns this error.

    Tuesday, June 17, 2008 7:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am getting this same error with exchange 2007. I can not find the answer anywhere and have posted many questions. Hope someone knows what is going on.

     

    thanks

     

    Tuesday, June 17, 2008 12:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have now got mine working via pop3, have you tried that?  Have seen several threads in various places with similar issues but no answers yet.

     

    Does your server have a self signed certificate by any chance, ie when you go in to web mail do you get a security warning?

    Tuesday, June 17, 2008 12:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have also noticed that any changes to teh config are not always picked up till the crm email service is restarted which did throw out the trouble shooting process a bit.

     

    Tuesday, June 17, 2008 12:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    ok now that i set up crm email router to use POP3 i am getting the following error. No connection could be made because the target machine actively refused it. am i missing a setting somewhere?

     

    Tuesday, June 17, 2008 1:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    My settings are:

     

    in the configuration profile:

     

    server type POP3

    Auth type NTLM

    Server <your server name> Use SSL is not ticked

    access credentials, other specified then enter the password associated with the mailbox your reading from, although I now have 2 queues set up and the same password works for both, hmmmm, but then they both have the same password.

     

    in the deployments http://<server>:<port>/<name>

     

    access local system account

    and select the profiles.

     

    You will also need to make sure POP3 access is enabled on the 2007 exchange server, if your not sure just try connecting to it with outlook express or something similar.

    Tuesday, June 17, 2008 1:55 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Looks like you guys are working through it together. That's great. However, you should be able to get it to work via Exchange and not have to use a POP3 workaround. Again, the Test Access is a helpful tool. Also, I found that when configuring for Exchange, using https://server for Location/Server worked for me.

    Wednesday, June 18, 2008 3:45 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
     Larry Lentz wrote:

    Looks like you guys are working through it together. That's great. However, you should be able to get it to work via Exchange and not have to use a POP3 workaround. Again, the Test Access is a helpful tool. Also, I found that when configuring for Exchange, using https://server for Location/Server worked for me.

     

    I just tried this again as I know I tried it before, this time however after making the changes I also restarted the email router service, and would you believe it it worked.  So the moral of teh story is 'restart the email router service' whenever you change anything.

     

    Thanks for the help people.

    Wednesday, June 18, 2008 4:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I get this error too and have tried everything.  I am using Exchange 2007 and have a server with the hub role and client access role installed.  I have enabled OWA on this server as well.  I have disabled SSL for OWA to rule that problem out.  I still can't get this to work.

     

    Any ideas?

    Friday, July 4, 2008 1:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just wanted to point out that I have been having the same issue too and followed Larry's advice and the https://server worked perfect for me.  Solved the whole problem and when I test access for the users, they all succeed!!!Thanks Larry

    Monday, July 14, 2008 1:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You're quite welcome. Glad it worked for you.

     

    Monday, July 14, 2008 2:14 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    Unfortunately, this is not working for me. Any other thoughts?
    Friday, August 15, 2008 2:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I was experiencing this problem earlier; my Exchange Server address was configured as http://mail.mydomain.com which I tested in a browser window but the E-mail Router was erroring out.  After I changed the Exchange Server address to http://server-name it starting working like a charm.

     

    I hope this helps.

     

    Kenneth

    Monday, September 22, 2008 7:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I was having the same issue crm 2011 email router and followed Larry's advice and changed the exchange server address to: https://server-name and it worked first time. Thanks Larry

    Thursday, July 21, 2011 3:09 PM