It has to do with the way the Fortinet does it's NAT when using a VIP.
So for example my Expressway-E server has an IP address of 10.1.1.1 and an external address of 188.8.131.52
My DNS is jabber.lab.com pointing to 184.108.40.206 both internally in my domain and externally. It is important that internal and external clients use the external address so they must be the same.
On the Fortinet my Expressway-E is shown as a VIP with a static NAT so 10.1.1.1 <-> 220.127.116.11 on any interface.
When my Expressway-C needed to connect to the Expressway-E via the external address it was failing.
The solution was to follow the article I linked to at the start of this post. In this article be aware that in point 2 where they are editing the match-vip setting the edit 2 relates the rule you are changing this setting on.
here the solution. On VBA Code add PtrSafe after the Declare statements, *** TIP: Save file as .XLT 32Bit Config - VBA64Bit Config - VBAPrivate Declare Function SHBrowseForFolder _Lib "shell32" _( _lpbi As BrowseInfo _) _As...
we recently announced new addition in our portfolio : Webex Desk Pro.
The Webex Desk Pro is designed for executive desktop and focus rooms that accommodate one to two people.
It is an all-in-one premium collaboration and productivity devi...
i understand there is api and macro can be used to connect to service now via the touch panel . the problem in my organisation is that there is a need to connect to a proxy to be able to connect to service now how can i do that ? htt...
we recently announced new addition in our portfolio : Webex Room USB.
Cisco Webex® Room USB is a lighter version of the Webex Room Kit Mini that works as an extension of your laptop/desktop to provide advanced camera/a...