What port for Authorze.net (AIM) module?

I am using a clean install of Zen Cart 1.3.8a with the Authorize.net (AIM) module configured for use with Securenet per Securenet's instructions. They do not use cURL for what that is worth.

I get a communications error when attempting to process a transaction. Securenet advises they the request is not reaching their server. My host is Eleven2.

To test the settings, I did the same installation on HostMonster. There, it worked fine. So I am thinking that Eleven2 just needs to open a port. Can someone please tell me what port I should ask them to open?

I appreciate any help. BTW, I did see someone who had a similar issue with GoDaddy, but I could not determine that any information in that thread was what I needed here.

The AIM module *only* uses CURL to talk to the payment gateway.
If your host doesn't support CURL, then you can't use that module.

AIM works on port 443, which is the standard SSL port for HTTPS traffic.

Thanks. It is not the host that doesn't use cURL but rather Securenet that doesn't. As I mentioned, I did use their settings successfully (without cURL) on another host. One difference is that on the other host I did not have SSL (since I was just testing the module). On the main site I do have SSL.

Quote:

---

Originally Posted by pwaites

Thanks. It is not the host that doesn't use cURL but rather Securenet that doesn't.

---

You're misunderstanding what CURL is.
Neither Authorize.net nor Securenet "use" CURL in the process of your store communicating to them.
It's the Zen Cart module that uses CURL, not the payment company.

Ah, ok. I can try that. Can you please point me to what the settings should be? I am confused though by the fact that it worked without any different cURL settings on HostMonster. But if it works here, that's all I care about.

I'm not sure what CURL settings you think you need to change.

It was this that I saw that made me think cURL might have something to do with it. http://www.zen-cart.com/forum/showthread.php?t=39438

If you're not using GoDaddy and your hosting company doesn't use a CURL Proxy for CURL communications, then you would simply leave the CURL Proxy setting OFF in your admin area. It's off by default.

Problem resolved. The host reports that there was an issue on their end that is now fixed. Tested and works! Sorry for the false alarm and thank you for the info.