ECC 5.2 Remote Console Login Failure

Could mean 2 things:

1) ECC server is in fact down
2) Latency between your Console and the ECC server is too high. You can check the log file to read what the ECC Console "thinks" is happening here

The number 2 happened to me as well and since all traffic had to go through a firewall to get to the ECC Server, there was nothing we could do. We now log in to a Terminal Server which resides on the same subnet as the ECC Server, so we know latency is low. ECC now works just fine.

I see, now I am using RDP , but I still need to be able to login from a remote console, there is no network issue at all, because the ecc server and the remote client exist in a private switch in the same LAN, I don't see why it can't get connected. The point is that the authentication works fine, when I use the wrong password, I receive the bad password error, but it can't open the console.

I see, now I am using RDP , but I still need to be able to login from a remote console, there is no network issue at all, because the ecc server and the remote client exist in a private switch in the same LAN, I don't see why it can't get connected. The point is that the authentication works fine, when I use the wrong password, I receive the bad password error, but it can't open the console.

Can you verify that you can do DNS resolution between the client device and the ECC server? If you have a distributed environment (Store on a different server than the ECC Server) you need to make sure you can resolve to there as well.

If you enable the Console logging you may find some additional information in the log it generates (can't remember exact location, but it is easy to find) to trace what is happening or worst case open a case with SAC to trouble-shoot.

Sorry for the stupid question, but are you able to open the ECC console from anywhere?

apologies also, for the stupid question
if you are RDPing onto the Console client why dont you RDP directly onto the ECC server ?
I'm curious why not ?
regards
Alick

Is it really a domain issue ?

He never answered the question:


I think we're all curious if ECC does work at another console.

is it a domain isssue , if you are using AD then you will have to login with

domain\username and not just username

hope this helps

regards

Alick

Not all environments have a console installed on the infrastructure host. I have a distributed environment where the Console is installed on two hosts (which also have other agents on them) and we access it through RDP. There are two other hosts with the actual infrastructure (Server, Repository, Store) on them.

I don't use any AD for user authentication, also I don't have any DNS issues, these basic problems have been checked before posting this message.
I don't see why this remote console doesn't work.
The reason that why I don't use RDP instead of remote console doesn't make sense.
ECC Console works fine at ECC Server, and Web Console works fine from other clients too.
I can't directly RDP into ECC Server, because it is located in a physically private network and I have only one multi home client to reach ECC Server.
Please try to resolve the problem, we don't have to omit the problem itself

The private network is an interesting twist on this and may explain your problems a little more.

Since it sounds like you have multiple NICs on your ECC host did you follow the configuration guide for multi-homed host configurations with ECC? It is possible the ECC console is failing to communicate over your main network connection.

You could also see some flaky results (such as other things like Web console working) if this is not configured correctly.

If you are unsure or did not make these changes - check the Installation guide for some detail on this.

If this is not the case you probably want to get a case open with SAC on this issue - they can dig deeper into this issue than you'll get from peers on a forum.

Problem resolved. I reviewed configuration files of ecc console and changed some fields and it works fine now.
Thanks for all your kind recommendations.

What parameters did you need to adjust out of curiosity if nothing else?

That's what I want to know as well

What fields did you change ? Please let us learn from this as well

In eec console installation directory, in data/ecc_console.ini file, there is a field named "server host", which was set to localhost, I replaced the value with ECC Server's hostname. This is what console is trying to connect and that was why it claimed that ecc server can not be reached, because it referred to the console itself.