I'm having an Issue with OCS2007 PIC

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.

jangell427Asked:
Who is Participating?
 
gaanthonyConnect With a Mentor Commented:
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
 
gaanthonyCommented:
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
 
jangell427Author Commented:
Customer is changing the IP of the Internal Interface Friday morning if that fixes the trouble I'll let you know.
0
 
jangell427Author Commented:
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
All Courses

From novice to tech pro — start learning today.