Meeting Place express server 2.0 won't start a meeting outside the firewall

stroutjustin · ‎02-28-2008

My meetingplace express server has a NAT address outside our firewall. Internally the server starts web meetings without issues but whenever you try to launch a web meeting outside of the firewall from the internet an error occurs during the meeting startup that says it cannot connect. Any ideas?

comprendre · ‎03-05-2008

your public IP address should be routable on the DNS

okuehn · ‎03-06-2008

Hi Justin,

you have to open tcp port 1935 for adobe breeze traffic. using cisco PIX/ASA firewall your access-lists would look like:

access-list OUTSIDE-INBOUND extended permit tcp any host YOUR-EXTERNALNATIP eq https

access-list OUTSIDE-INBOUND extended permit tcp any host YOUR-EXTERNALNATIP eq www

access-list OUTSIDE-INBOUND extended permit tcp any host YOUR-EXTERNALNATIP eq 1935

so long, Oliver

stroutjustin · ‎03-06-2008

Oliver,

Thank you for your reply. I already have these statements on my pix 7.2 firewall. I was thinking there was maybe something else on the meetingplace server I should be looking at. It all works inside the pix firewall.

Thanks,

Justin

goldbergj · ‎03-07-2008

Justin,

You're 2nd NIC on the MPx Server must also have an public IP address that is translated to its internal (private) IP. The first NIC is for audio/http management while the 2nd NIC is the one that takes care of the web portions of the conference.

This would make sense as to why it works internally and not externally.

HTH,

JG

Please rate helpful posts

okuehn · ‎03-07-2008

Hi Justin,

sorry, but it seems my last reply got lost...

please ensure that you have a NAT statement and a working external dns host entry for your second MPX network interface. which is used for RTMP.

your PIX firewall ACL should look like:

************** MPX Web interface

access-list OUTSIDE-INBOUND extended permit tcp any host YOUR-MPXWEB eq https

access-list OUTSIDE-INBOUND extended permit tcp any host YOUR-MPXWEB eq www

access-list OUTSIDE-INBOUND extended permit

tcp any host YOUR-MPXWEB eq 1935

************** MPX RTMP interface

access-list OUTSIDE-INBOUND extended permit tcp any host YOUR-MPXRTMP eq https

access-list OUTSIDE-INBOUND extended permit tcp any host YOUR-MPXRTMP eq www

access-list OUTSIDE-INBOUND extended permit tcp any host YOUR-MPXRTMP eq 1935

if you use ssl, you have to have two hostnames and according certificates, one for each interface.

Oliver

ricardorojas123 · ‎05-15-2008

What ports I need to open in my firewall to works Meeting Place Express ?

What I need to public my cisco meeting place express for outside client?

okuehn · ‎05-15-2008

Hi,

please read my previous post in this topic. it describes in detail the firewall port requirements.

additionally you have to setup NAT translation and external DNS/IP adresses for both network interfaces of the MPX server

regards, oliver