Solved

I'm having an Issue with OCS2007 PIC

Posted on 2008-10-02
4
1,201 Views
Last Modified: 2013-11-29
I have an OCS 2007 Enterprise deployment with consolidated edge server. Everything works great federation works PIC works but we only have MSN and from the communicator side all messages get sent fine, from the MSN side about every third message gets an error that the message can't be sent but do it again and its fine.  I am also getting this error on my edge server but I don't know if it is related.
Category 1001 and Event ID 14502 :  Server fed.messenger.msn.com IP address x.x.x.x there has been 139 errors in the last 180 min.   Failure type 80072746 occurred 12199 times and 80072745 occurred 26 times.

0
Comment
Question by:jangell427
  • 2
  • 2
4 Comments
 
LVL 12

Expert Comment

by:gaanthony
ID: 22691784
The recommended firewall configuration when federating with public IM providers is to allow any IP address to connect to port 5061 on the Access Proxy.
Verify that 5061 doesn't have any ACL/host restrictions rules in your external firewall.
Ensure your internal and external Access Edge interfaces are on different subnets so that traffic routes out the correct interface.
0
 

Author Comment

by:jangell427
ID: 22769773
Customer is changing the IP of the Internal Interface Friday morning if that fixes the trouble I'll let you know.
0
 

Author Comment

by:jangell427
ID: 22843910
Change the IP address on the internal interface and that did not fix the issue.  I found something on the internet about using GoDaddy certificates so we are going to try a different cert and see if that fixes the issue.
0
 
LVL 12

Accepted Solution

by:
gaanthony earned 125 total points
ID: 22857833
GoDaddy certs work fine as long as you have the current Windows root CA update installed.
You mentioned that you are seeing 8007274C and 80072746 errors.
These are WSAECONNRESET and WSAETIMEDOUT errors respectively. The first is due to a TCP session failing to be established (other end sends a reset) and the second is
a TCP session that has been successfully established failing due to a time-out
(other end didnt answer).  Could be issues on either side (yours or MSN).
Also if your Edge server internal and external interfaces are on the same subnet it can cause this issue.  Either use one NIC with two IPs bound to it and the default gateway set to the external or change the internal and external interfaces to be on separate subnets. Default gateway would still go o the external NIC.
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

This is my 3rd article on SCCM in recent weeks, the 1st (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_4466-A-beginners-guide-to-installing-SCCM2007-on-Windows-2008-R2-Server.html) dealing with installat…
Messaging apps are amazing tools with the power to do a lot of good, but the truth is the process of collaborating with coworkers requires relationships established through meaningful communication - the kind of communication that only happens face-…
The goal of the tutorial is to teach the user how to instant message and make a video call in Skype.
Internet Business Fax to Email Made Easy - With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now