Skip to main content
A
Anonymous
July 5, 2010
Question

User can't connect to our Connect, but can a different one.

  • July 5, 2010
  • 1 reply
  • 496 views

We have just setup a Connect Pro (v7.5SP1 on Server 2008 R2) on a server in a datacentre here in Brisbane, Australia. We can connect to it fine and use it but one person can't join a meeting. It sounds similar to what we got initially when the firewall on the server was blocking connections to the FMS. However that person can connect to a different Connect Pro server (hosted by a business partner in Germany) and it connected fine.

What configuration and tests can we do to resolve this? That person is connecting from a government network so there would be  firewalls, etc, but I don't know enough about the configuration why the one in Germany works but ours doesn't.

TIA.

    This topic has been closed for replies.

    1 reply

    A
    Anonymous
    July 6, 2010

    OK, because no-one tells me the correct things, the server which I was told in Germany is actually Adobe-hosted. I got a username/password to connect to it and sniffed packets - it appears all communication uses port 443 to two different IP addresses. I am now looking at implementing SSL, hopefully it will work with one IP address?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices