Paymentech EDC 6.5 and ACLs

[Monocle42]

Hi! I'm new to the forum for posting but have long enjoyed many posts for useful information.

I currently am processing with CES with about 20 sites and have plans to migrate to Paymentech. In testing Paymentech I've encountered an issue that must be ACL related, but neither Radiant nor Paymentech has been able to point me in the right direction.

The ACLs I have in place allow only a few IP blocks and services through to or from my Aloha server. I've added the entire 65.124.118.0/24 range to my ACL but when I attempt to auth a transaction I get the dreaded "Network Error: Could not get response from server". When I completely disable my ACLs the transactions process with extreme prejudice.

A few things to note: The SOHO router in production is a Cisco (Linksys) RVS4000. The ACLs in place allowed CES to process without any hiccups. I'm using the SSL feature of Paymentech (I've even tried entering the IP addresses for netconnect1 and netconnect2 instead of DNS). When I get the Network Error, I'm able to plug

https://netconnect1.paymentech.net/NetConnect/controller

into a browser and get the expected response (this tells me the ACL is allowing traffic but EDC is upset about something being blocked).

Has anyone else experienced similar issues? For PCI reasons I really don't want to run without ACLs.

Thanks!

 

[Monocle42]

*bump*

 

[coorsman]

Edcsvr.exe (EDC Server) uses port 443 for credit card authorizations via a SSL or HTTPS connection.



Unless a port is defined with the IPPORT variable in the Edc.ini, the default SSL2 TCP ports are 6660 for RBS and 5003 for Visanet.



Thats all I could find.


Cheers,
Coorsman