RPC Endpoint 6001 Error 1818 - Outlook Anywhere and POP/SMTP does not work

Hello.

I have fully configurated an exchange 2007 schema, working with no problem since 4 years ago.
Suddenly, clients with POP/SMTP or Outlook Anywhere connections started yesterday to fail to connect to exchange.
Testing the connection in www.testexchangeconnectivity.com, it shows:

      Attempting to ping RPC Endpoint 6001 (Exchange Information Store) on server exchange.game.es
       The attempt to ping the endpoint failed.
       
      Additional Details
       An RPC Error was thrown by the RPC Runtime. Error 1818 1818

I have tried the solutions provided in other similar post from your web and didn't work (changing some value keys in rpc values)

What is happening?
Raul_GAsked:
Who is Participating?
 
Raul_GAuthor Commented:
Changed the POP connector authentication to "Plain text authentication logon (Integrated Windows authentication)" and restarted POP services and works flawless again.

Disabled the Outlook Anywhere, and recofigurated again, and everthing works fine again.

Dunno what was happened, cause everything was working since 4 years ago.

Thanks anyway for your help.
0
 
e_aravindCommented:
When you ping localhost from E2k7 CAS server, are you receiving ::1?

If yes,
Can you edit the host-file entry on the CAS server
<ip-v4> Netbios-name of the cas server
<ip-v4> fqdn-name of the cas server
<ip-v4> localhost

Then, now, ping localhost should return an IP-v4 address.
Then can you check the rpc/https configuration/connection from any Outlook client?
0
 
Raul_GAuthor Commented:
This settings have not been changed.

The fqdn-name is exchange.game.es and the ip is 212.170.159.45, and is well configured on client, as yesterday when it was working.

The extrange thing is why the POP/SMTP account connections are not working, but if you try to connecti to the same accounts via exchange or OWA, there is no problem at all.

Please help!
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
endital1097Commented:
try some of the simple troubleshooting steps

verify your external DNS records are still accurate
attempt to telnet into the vairous ports

telnet exchange.game.es 110
telnet exchange.game.es 25
telnet exchange.game.es 443
0
 
Raul_GAuthor Commented:
Telnet working on this ports.

I have checked certificate for SMTP service and is out to date.
Maybe could be this the problem to this issue?

How could we renew the certificate on exchange?
0
 
endital1097Commented:
you can run the following
get-exchangecertificate | where { $_.Services.ToString().Contains("SMTP") -eq $true } | new-exchangecertificate
0
 
Raul_GAuthor Commented:
I had 2 certificates.

All external, one validated an in-date with services IMAP, POP, IIS.
Another one, out-to-date with services POP, IIS, SMTP

I have deleted the out-to-date certificate and enabled the right one with the SMTP Service, so now I have this:

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System
                     .Security.AccessControl.CryptoKeyAccessRule, System.Securi
                     ty.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {exchange.game.es}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=Thawte SSL CA, O="Thawte, Inc.", C=US
NotAfter           : 01/09/2013 1:59:59
NotBefore          : 10/08/2010 2:00:00
PublicKeySize      : 1024
RootCAType         : ThirdParty
SerialNumber       : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Services           : IMAP, POP, IIS, SMTP
Status             : Valid
Subject            : CN=exchange.game.es, OU=SISTEMAS, O=GAME STORES IBERIA S.L
                     ., L=Pozuelo de Alarcon, S=Madrid, C=ES
Thumbprint         : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

0
 
endital1097Commented:
outlook anywhere should then work with a valid cert for IIS
0
 
Raul_GAuthor Commented:
But at the moment is not working, and the crazy thing of it is that happened suddenly, without touching anything.

Our clients could not connect to pop/smtp secure connections. If we create a connector for SMTP with anonymous user authentification, people can send emails, but they cannot log to the POP3.

Outlook anywhere is not working via RPC / HTTP, and www.testexchangeconnectivity.com give me that error on RPC again (1818 1818).

Should be a problem with the certificate in any way? Should I copy or renew this certificate?

Why this things are not working suddenly?

Please, help me friends!

0
 
Raul_GAuthor Commented:
I get the pop3 connector and SMTP Working but the authentification is really slow, also as the OWA clients outside the domain.

How could see if the server is dispatching emails or is being attacked by any external machine?
0
 
endital1097Commented:
outlook anywhere was impacted by the expired certificate
pop3... enough said :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.