[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 319
  • Last Modified:

Outlook can't use Outlook Anywhere to Exchange 2007 - RPC issue?

I'm unable to auto-create an Outlook 2013 profile by using the new account wizard in Outlook and also I'm unable to do so even if I manually add the settings.

After using the testexchangeconnectivity.com tool I noticed I'm getting the errror:

Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server mail.server.com.
       The attempt to ping the endpoint failed.
        Tell me more about this issue and how to resolve it
       
      Additional Details
       
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3112 ms.

I did connect directly to the Exchange server and tried to telnet to port 6004 and it does not work. I believe this is Exchange 2007 SP3, it says the version is 8.3.

Not sure where to go from here.. I've checked all the registry keys, tried to modify some etc. I did make sure ipv6 was disabled but when I ping the machine to its own FQDN I get an IPv6 response.. not sure why.. nor not sure if related.
0
Metaltree
Asked:
Metaltree
  • 7
  • 3
2 Solutions
 
Simon Butler (Sembee)ConsultantCommented:
If you have tried to disable IPv6, then reverse that. It causes more problems than it is worth and is a very old fix for a very old problem.

The quickest fix for this kind of issue is to
a. disable Outlook Anywhere in Exchange,
b. wait 15-20 minutes for an entry in the event viewer to say it has been disabled.
c. Remove the RPC Proxy feature from IIS. Run IISRESET after doing so.
d. Check in IIS manager that the two RPC virtual directories have been removed. If not, remove them and run IISRESET again.
e. Reinstall the RPC proxy feature.
f. Enable Outlook Anywhere again.

That fixes it 90% of the time.

However do ensure that whatever you did for IPv6 has been corrected.

Simon.
0
 
MetaltreeAuthor Commented:
ipv6 is currently and has always been disabled. should it be enabled?
0
 
Simon Butler (Sembee)ConsultantCommented:
IPv6 would have been enabled by default and that is the only scenario that Microsoft test. They do not support IPv6 being disabled. Furthermore a lot of people don't disable it correctly - it is a little more than deselecting the box in network connections. If find a machine with it disabled then I enable it, reversing whatever has been done to try and disable it. Only then do I do further troubleshooting.
The product expects IPv6 to be enabled.

Simon.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
MetaltreeAuthor Commented:
I went through the entire process you listed. It did not resolve the issue and I'm still unable to telnet to 6004  even on the localhost and it fails the ms testexchange test.
0
 
Simon Butler (Sembee)ConsultantCommented:
What about the Ipv6 fixing? Did you resolve that? Have you undone the changes to IPv6 to try and disable it?

Simon.
0
 
MetaltreeAuthor Commented:
It was previously disabled, I had it enabled then tried to perform these steps. I'm not sure how I can test if ipv6 is "broken" or even how to begin to fix it.
0
 
MetaltreeAuthor Commented:
Ok, I enabled ipv6 on the ESX host which this VM resides on and now I'm not getting an error on port 6004 when I putty in.

However, the issue is still happening, so I'll go through the previous steps again now that this ipv6 issue appears to be resolved.
0
 
MetaltreeAuthor Commented:
Alright, IPv6 is fixed, I've gone through all these steps again. Still not working.
0
 
MetaltreeAuthor Commented:
Figured it out, ended up being a HOSTS file issue. It was blank, and for some reason when I would try to resolve MAIL.SERVER.DOMAIN locally on any port, it would fail. So I added all of the NetBios and FQDN ipv4 address to the hosts file and it resolved the issue.

It could resolve when I pinged etc locally, so I'm not sure what the issue actually was.
0
 
MetaltreeAuthor Commented:
Found the solution on my own with the help of Sembee
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 7
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now