Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AWV configuration

Status
Not open for further replies.

sunspark

IS-IT--Management
Oct 5, 2012
53
FR
Hi ,

I have a micollab 7.3 in lan mode with a MBG in Dmz

Micollab: lan address 192.168.1.1

Mbg.mycompagny.com / public address: x.x.x.58

conf.mycompagny.com / public address: x.x.x.59


I look at the engenieering guide line, but I do not understand how I have to redirect AWC in the firewall

Ps: I'm in version 7.2 so I have to use two external addresses.

Any help will be appreciated.
 
First off internal and external DNS have to be the same (split DNS):
Internal collab.mycompagny.com -> 192.168.1.1
External collab.mycompagny.com -> public address: x.x.x.58
Internal conf.mycompagny.com -> 192.168.1.1
External conf.mycompagny.com / public address: x.x.x.59

Both external addresses need to point to the mbg dmz address following all port forward rules as in the engineering guidelines.

In the MBG the Service Configuration, Application Integration needs to be setup.
If DMZ mode is not showing external address for set side streaming, try changing to custom mode and manually entering the ip's

Then the conf.mycompagny.com needs to be setup in the Remote Proxy Services

Then there is the config of the AWV on the MiCollab.
Under web conferencing settings the internal port should be 4443 and external 443, with the full web conferncing name (for default settings).

Finally you need to make sure that your certs are all ok on the MBG and the MAS.

To test basic cert and commincation when you are done, externally browse to
After this it is usually a networking, firewall or routing issue that would stop this from working.
 
Hi Alphamann

Big thanks.

from external i'm able to reach :
But with : nothing happens.

-Under web conferencing settings everything is good ( internal 4443 , external 443 , web conf name : conf.mycompagny.com)
- Certificat in MBG and Micollab OK

- MBG -> Remote proxy services -> WAN-side FQDN : collab.mycompagny.com not conf.mycompagny.com ( it is correct ? )


Sorry , but i'm not confortable with Firewall rules and redirection

Micollab is in Lan mode , so it dont have external adress ?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top