I have just gone through the auto update process on the server and on my local client workstation from 7.51 to 7.5.2

The upgrade appeared to go without any issues and after the upgrade the server operates with no problems, client on the server works fine and all of the jobs appear to be running with no issues.

However the client on my workstation will no longer connect to the server. I get a message "The login attempt failed". If I change the password on the server only and try again I get an "Invalid password" message. If I turn off all firewalls there is no difference, everything worked before the upgrade so I was just covering off every issue. I have deleted the server details from my workstation, and even uninstalled and removed all traces of Visualcron and reinstalled. Still the same error.

Is it just me, or is there an issue?

It is not related to firewalls as communications seem to work - you do get a login attempt failed. But the actuall error is unknown to us. Can you post a screenshot? Also, please send log_serverDATE.txt to support@visualcron.com

---

We had a similar problem on going to 7.5.1 and found that we just needed to delete and re-add the users.

We had a similar problem on going to 7.5.1 and found that we just needed to delete and re-add the users.

This is very different error. According to logs there is no sign of Client even connecting to server.

I suggest the following test:

1. install the Client on another computer that is updated with all Windows update. Perform a remote connection. Same error? We are suspecting that the client computer might be out of date in updates.

---

I am having issues as well. Upgraded from 7.5.1 to 7.5.2 and now the clients cannot connect. Workstations are fully patched and up to date. We are getting:

Connection failed to 'SERVERNAME'. Connecton failed with error: 'The target principal name is incorrect'. Do you want to try reconnecting?

I've deleted and re-added the user (we are using AD), delete the connection in the client and re-setup, etc.

Same issue here upgrading to 7.5.2. We use local accounts and am getting an invalid login error. Tried removing and re-adding local users but without success. We are able to login with those accounts on the server itself, but all remote connections from clients fail.

Reverting to 7.5.1.

Same issue here upgrading to 7.5.2. We use local accounts and am getting an invalid login error. Tried removing and re-adding local users but without success. We are able to login with those accounts on the server itself, but all remote connections from clients fail.

Reverting to 7.5.1.

What if you create a local account and log on with VC authentication? We would like to know if this is limited to AD or something else?

---

Same issue here upgrading to 7.5.2. We use local accounts and am getting an invalid login error. Tried removing and re-adding local users but without success. We are able to login with those accounts on the server itself, but all remote connections from clients fail.

Reverting to 7.5.1.

What if you create a local account and log on with VC authentication? We would like to know if this is limited to AD or something else?

We create local accounts in VC, and then attempt to login with those credentials in the client. We are not using any AD authentication for the client to server connection. We removed the VC local accounts, and recreated and still same issues.

Same issue here upgrading to 7.5.2. We use local accounts and am getting an invalid login error. Tried removing and re-adding local users but without success. We are able to login with those accounts on the server itself, but all remote connections from clients fail.

Reverting to 7.5.1.

What if you create a local account and log on with VC authentication? We would like to know if this is limited to AD or something else?

We create local accounts in VC, and then attempt to login with those credentials in the client. We are not using any AD authentication for the client to server connection. We removed the VC local accounts, and recreated and still same issues.

With new version, can you telnet to remote server:

telnet servername 16444

---

Besides telnet test please test the following:

Locally, on the server, start the VC Client. Click on Manage Connections, the little icon to the right of servers combo. Add a new connection:

- uncheck "Is local connection"
- type the local ip as host/address. Do not use 127.0.0.1 but the local IP

Save the Server connection and select the new connection and click Connect. The question is if this works better. After doing this, please send log_serverDATE.txt to support@visualcron.com

---

Tried to telnet from a client and it doesn't connect. I also tried to telnet from another server in the datacenter to eliminate any firewall issues and couldn't telnet from another server on the same network switch, so it doesn't sound like this is a networking issue to me.

From the local server, I can change the connection to be non-local as per the recommendation above and it connects just fine.

On a whim, I changed the client connection from the server name to the server IP address and now it works ok. Not sure if that would be a VisualCron issue or something else, but I can make other connections from the workstation to the server using the name with no problems.....strange.

Tried to telnet from a client and it doesn't connect. I also tried to telnet from another server in the datacenter to eliminate any firewall issues and couldn't telnet from another server on the same network switch, so it doesn't sound like this is a networking issue to me.

From the local server, I can change the connection to be non-local as per the recommendation above and it connects just fine.

On a whim, I changed the client connection from the server name to the server IP address and now it works ok. Not sure if that would be a VisualCron issue or something else, but I can make other connections from the workstation to the server using the name with no problems.....strange.

I see - interesting. I sounds like it is related to IPv4 and IPv6. That it only listens to IPv4 address. If you ping the hostname - do you get the IPv4 or IPv6 address?

---

We are having this same problem. Had to downgrade all of our machines to 7.5.1. We are getting these 2 error messages:

"The target principal name is not correct"
"An existing connection was forcibly closed by the remote host"

This is also happening for us.

We are having this same problem. Had to downgrade all of our machines to 7.5.1. We are getting these 2 error messages:

"The target principal name is not correct"
"An existing connection was forcibly closed by the remote host"

We are investigating different errors. Your error is related to DNS resolution. Changing to IP will solve that problem.

---

That's not really an option or us (that's changing connection entries for over a dozen servers, and some of these are not static, so they could change). We'll have to stick with 7.5.1 until this is resolved.

That's not really an option or us (that's changing connection entries for over a dozen servers, and some of these are not static, so they could change). We'll have to stick with 7.5.1 until this is resolved.

Ok, we will notify you about this when it is re-released. Thank you.

---

Hi all,

hopefully all issues should now have been fixed in this version:

http://www.visualcron.co....aspx?g=posts&t=4676 

---