Webex install 2.6.1 unable to connect to admin page

[Thomas Marie]

Hello,

I'm trying to install Webex 2.6.1 with ova on esxi 5.5.

Installation and Deployment are OK , when i start the virtual machine ,all check are in green.

Admin Station is in the same VLAN so port 10200 is open.

there is no firewal enable on admin station

When i try to reach url with firefox, chrome or IE i have this message after SSL certificat warning accepted.

I remove all cookies from web-broswer

I can ping server , when i do a telnet from the admin station to the server on ports 10200 , server doesn't answer.

It seems the server doesn't listen on port 10200.

did someone meet this issue ?

Is deployement issue ?

I tried to reinstall many time the server but i have always the same issue.

There is a way to switch in CLI on the virtual machine with CTRL+ALT+F2 but i need a login.

Is there a default login  ? , it will be usefull for troubleshoot why redirection doesn't work :

Thanks for you help .

Regards,

Thomas

[Richard Simmons]

Do you have DNS configured correctly for all the servers?

Have you tried accessing it via the IP address? i.e. https://IPADDRESS/Deployment?....

[Thomas Marie]

Hello Richard,

Yes DNS works fine , i check it with nslookup .

With the ip address , this is the same issue

If the server doesn't listen on port TCP 10200 , redirection will failed.

Regards,

Thomas

[Richard Simmons]

Do you have the correct PTR records in DNS too?

I had a similar issue and it appeared to be doing a reverse lookup and coming back with a different host name.

You can check this by from the cmd prompt via ping -a IPADDRESS

Do this a few times to see which hostname is returned.

[Thomas Marie]

Hello Richard,

i have an answers when i do it , the only difference is the FQDN.

C:\Users\tmarie>ping -a

Envoi d'une requête 'ping' sur webex-tin [2] avec 32 octets de données :
Réponse de : octets=32 temps=10 ms TTL=56
Réponse de  : octets=32 temps=3 ms TTL=56
Réponse de : octets=32 temps=3 ms TTL=56
Réponse de  : octets=32 temps=3 ms TTL=56

Thomas

[Richard Simmons]

try browsing to this

https://FQDN/Deployment?.......

For the DNS Local domain name you don't need the proceeding . it will be fine with just ' net.esi.adp.com '

[Thomas Marie]

yes i try with FQDN but it's the same.

When i do an wireshark trace, there is lot of tcp connections  restart  with alway the same packet , it will increase 52073 52074 52075 ...

and it stop.

I really don't now what i can do .

Thomas