Error when trying to log in to a C60 using TC Console

[awander]

I get:

I can log in to a C40 on my network with no problem.

the C60 I am having trouble with is running

Software version: TC4.1.0.247017

[Paula Talamo]

Hello Andy,

• Are both the C40 and C60 running TC 4.1?
• Are you able to connect to the C60 over https using your browser (https://xxx.xxx.xxx.xxx:443)?
• What are the HTTP/HTTPS configuration settings on the C60 showing?  (xConfiguration NetworkServices HTTP Mode)

- Paula

[awander]

Hi Paula:

Thanks for the reply.

• Are both the C40 and C60 running TC 4.1?

-C40 is running TC4.0.1.240265; C60 is running TC4.1.0.247017

• Are you able to connect to the C60 over https using your browser (https://xxx.xxx.xxx.xxx:443)?

-no, I can't connect using https, though it is ON in web config pages

• What are the HTTP/HTTPS configuration settings on the C60 showing? (xConfiguration NetworkServices HTTP Mode)

-*c xConfiguration NetworkServices HTTP Mode: On

-*c xConfiguration NetworkServices HTTPS Mode: On

I tried changing to:

*c xConfiguration NetworkServices HTTP Mode: Off

*c xConfiguration NetworkServices HTTPS Mode: On

And rebooting

As well as to:

*c xConfiguration NetworkServices HTTP Mode: On

*c xConfiguration NetworkServices HTTPS Mode: Off

And rebooting

And in both cases, I can't connect via https, with or without the ":443"

I also realized that the unit had no password set, so I set the adminpassword back to the default, and tied again-still no go.

Finally, I am having inconsistent results using the CLI commands; I have always been able to use abbreviations of the commands as long as they are long enough to be unique-for instance, "xconf networks" instead of "xConfiguration NetworkServices", but they only work "some of the time" on this unit. Don't know if it is related.

Andy Wander

This communication including any attachments, are intended

for the exclusive use of the addressee(s) and contains

confidential or copyrighted materials. Duplication,

distribution or reproduction is strictly prohibited by law

without written permission of Verrex

[Justin Ferello]

All,

We are seeing the same problem here, let me clarify a few things.  The problem directly relates to the codec not having an SSL cert loaded.  I know the codec is supposed to have the default 'TANDBERG' cert loaded from the factory but they do not.  So it seems that the TC Console attempts to use HTTPS first when connecting, it receives an 'Unable to connect' error back and instead of falling back to HTTP it just fails.

If one disables HTTPS on the codec then the TC Console app will successfully connect via HTTP to the codec.

We have seen this 'cert' issue on both new C series codecs and RMA'ed C series codecs.  In fact I have an RMA'ed codec right now that has this problem.  I can provide IP and credentials upon request.

We due have a ticket opened with TANDBERG, it is 153520.

The only fix we have found is to downgrade the codec to TC3.x and re-upgrade it back to TC4.x.  This will re-install the default 'TANDBERG' cert and you will now be able to acess the codec via HTTPS thru the browser or the TC Console.  Oddly enough though, downgrading to TC4.x and back to TC4.x does not resolve the issue.  I can only assume that the codec is smart enough to know it only needs to modify a few files as opposed to needing to replace all the files via a major release upgrade/downgrade.

The next solution I was going to try was going to create a self signed fake 'TANDBERG' cert like the one that comes from the factory and try and load this on the codec.

Thanks,

Justin

[awander]

Thanks, Justin! (I can't get away from your support, it seems!)

Andy Wander, CTS, TCE I / TCE II

Vice President, Engineering

[Paula Talamo]

Andy,

Please go ahead and open a service request with TAC so they can investigate this further.

- Paula

[Paula Talamo]

Andy,

When you run the command "xcon systemunit", do you see a SystemUnit Name displayed?  If not, add it using "xConfiguration SystemUnit Name:, reboot the system and give it another try. 

- Paula

[Justin Ferello]

Paula,

Thanks for the information, that resolves the TC Console connection issue.

Thanks,

Justin

[awander]

This morning, I finally had a chance to work on the C60 again.

I set xconf networkservices http mode to ON and https mode to OFF.

I confirmed that there was no Nmae set under Systemunit.

Then I decided to confirm that I could nbot connect using TC Console, and.....I can now connect using TC Console!

just to confirm:

-originally I could not connect to TC Console, either through http or https. Ii could connect using telnet, or a wb browser.

-I tried upgrading the system software(to teh same version) and found no change in behavior.

-I let the unit sit for  a week or so, an dthis morning, when i firsta attempted to connect using a web browser, it would NOT connect using either htp or htps

-I connected via telent and found taht https mode was ON, and http mode was OFF, I swapped teh setting so https mode was OFF and http mode ON

-I then was able to connect using http thru web browser.

-and, suddenly, i was also able to connect using TC Console.

I am guessing the web connect problem this morning was related to teh missing certificate that Justin mentioned.

But, why I can now connect console without setting a system name, I don;t know.

Andy

[soohyung choi]

We had a similar problem.

Upgrading of codec can solve a problem. (TC5.X.X)

I recommend using TC5.X.X

if you cannot upgrade, downgrade to TC3.X.X

Now you can connect Codec using TC Console, but cannot use vidoe compositor.

then upgrade to TC4.X.X again,

you can connect Codec and use video compositor.

thanks