Thursday, November 19, 2009 3:26 PMHi all,
We have a problem with file transfers between OCS R2 Communicators, I think I know the reason why but here's the error:
You cannot receive the file "Reset Log count.docx" from Jan Mietle. This may be due to firewall restrictions or network problems. If you need further assistance, please contact your system administrator.You cannot receive the file "Reset Log count.docx.old" from Jan Mietle. This may be due to firewall restrictions or network problems. If you need further assistance, please contact your system administrator.
All our users have Communicator connecting via the Edge Server (due to complex routing we have between data centers) - this means we're all remote, internet users as such. Does this cause the problem with OCS Communicator file transfer failures as it should be peer to peer on internal lan only? If I open specific ports for file transfer, it will still fail? (I've found another topic on here with port requirements and still had issue).
Tuesday, November 24, 2009 9:15 AMModeratorHi
Could you plase dexcription more detail about your scenario?
Because that the issue will be caused by several reason.
For example: the connection about your branch site and the data centers
your whole topology about your ocs system
Does your user client install the VMware installed and configure a virtual network interface?
Any antvirus software installed on you client?
Or you can retrieve some trace log using netmon, and check out the issue exactly.
You can get more information about the file transfer between the oc refer to below link
Wednesday, November 25, 2009 9:21 AMThanks Gavin.
Our Infrastructure is based on OCS 2007 R2 std server with various roles including CWA on a remote data centre, users all connect via remote to the access edge server.
The clients are mainly Windows 7 with some being XP SP3, all fail this file transfer. All are using Sophos including OCS servers.
I've asked our comms guys to setup logging over our complex 2 firewall setup between data centre and office, we'll then be able to confirm the peer to peer traffic routing. With that link you've sent it really does look like a port issue with 6891 to 6901 being randomly selected - thanks for that. Will run testing and then confirm if resolved.
Thursday, November 26, 2009 11:47 AMFound problem, file transfers were working between OCS infrastructures so thought I'd test with another IM user within my infrastructure...that worked as well! Problem ended up being a local firewall on one laptop which blocked OCS file transfers.
- Marked As Answer by swisstonihasher Thursday, November 26, 2009 11:47 AM