What has to be done to connect a local Sugar system (behind firewall) with a public Mambo Server? Which ports have to be opened on the firewall that they can comunicate?
What has to be done to connect a local Sugar system (behind firewall) with a public Mambo Server? Which ports have to be opened on the firewall that they can comunicate?
Linking Mambo<-->Sugar means (in my opininion), that Sugar is accsessible via public WWW. USE THAT IN YOUR OWN RISK!
You need first public static IP or domain name for Your Sugar server (some ISP-s provides dynamic IP). Also You can use http://www.no-ip.com/ services for static IP.
Port numbers are described in http://www.iana.org/assignments/port-numbers
First, refer your server software manual.
Alright, that was absolutely no help. What he needs and what I need is a list of ports that need to be made accessible between the public Mambo server and the Sugar server which resides behind a firewall. I've tried opening port 80 and 7627 (I think that is the port that soap uses).
Has anyone else figured out how to do this?
Hi,
The way to make it more secure is to configure the firewall so only the IP of the mambo server can use the ports required, so no-one else can log in to sugar. The easiest way to work out which ports are needed is to run a filter on the logfile of the firewall to see what's being blocked inbetween the two servers. Failing that, install mambo localy and run TCPdump on the interface, and see what ports it's using.
I'm hopefully doing this myself shortly so will be able to tell you, but I was under the impression that Mambo/Joomla and sugar didn't play nice together - http://www.sugarcrm.com/forums/showthread.php?t=8809
If anyone has 401 and mambo/joomla actually working, please say, and I'll keep trying!
~Aggy
So far I'm seeing from Mambo to Sugar only port 80 being called. The src port seems to change though. I've seen anything from 1152 to 2959 so far on that. Perhaps that part is working just fine. When I try to get cases right now I get a Connection Error and a huge error dump starting with:
Connection Error
HTTP Error: Unsupported HTTP response status 404 Not Found (soapclient->response has contents of the response)
2006-02-02 10:30:43.133816 soap_proxy_21466: call: portal_get_entry_list, Array, http://testuri.com, http://66.243.3.226/crm/soap.php/portal_get_entry_list, , rpc, encoded; endpointType: wsdl
2006-02-02 10:30:43.133869 soap_proxy_21466: opData:
On the Sugar server I ran a tcpdump and the only connection it attempts is to itself on port 5901.
Last edited by eggsurplus; 2006-02-02 at 04:04 PM. Reason: more info
Hi Eggsurplus,
you're right , the source port isn't of concern - that will be all over the place, it's the destination port that you're concerned about, and assuming you're using standard ports, I would have thought just 80 would be enough. The firewall logs should tell you more though.
Thanks, the logs helped with figuring that the ports can't be the issue. On the bottom of the error dump on the Mambo side is this line:
No web site is configured at this address.
This is throwing me for a loop. What address are they referring to here? The soap.php address? That is configured and reachable through a browser.
Found the problem! When the Sugar server was set up the site url was set to localhost. I had to change site_url in config.php to use the external address. Port 80 is the only port that needed to be open between the two.
What's funny is that I was facing the exact same issue today as we switched ISPs which broke our Mambo->Sugar SOAP linkage. Not able to figure it out I found this post from a year and half ago where I had to solve the same issue! Thank you for internet for persistence of information!
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks