Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


XAAS
  •  XAAS
  • Paid support Topic Starter
2022-07-26T14:27:57Z
when trying to connect to the visual cron server remotely it fails with following error :

Connection failed to '10.2.1.35:16444'. Connection failed with error:

'The requested upgrade is not supported by 'net.tcp://10.2.1.35:16444/'. This could be due to mismatched bindings (for example security enabled on the client and not on the server).'

Do you want to try reconnecting?
Sponsor
Forum information
Joey S
2022-07-26T14:41:56Z
Error messages are not always 100% accurate so instead of focusing on the exact message I would suggest double checking all possible, easy, failure points

1. in the instance to which you are trying to connect (let's call that computer A), go to the Server tab (next to file and tools) and then the User/Logon tab and verify that that the setting 'Only allow local connections' is NOT checked
image.png

2. Check that you are using the right port by going to Server - Settings (like in step 1) then Main Settings and check the port and the firewall
image.png

3. Unlikely, but depending on the security on your network, is it possible that Computer A cannot talk to the computer that is trying to connect (let's call that Computer 😎. One quick way to sort that out without help from an IT security person at your company might be to; check or setup a quick network share, ping computer A from computer B or maybe run a traceroute from B to A

4. The user that is trying to connect, have them log in locally on Computer A first before you try to connect them remotely

5. Is the user a local user OR an AD user? If they are an AD user, is it possible they are locked out?

6. If nothing else try to logon (from computer 😎 as the default "Admin no password" user

7. maybe double check your IP or try to use the name of computer A instead of IP

I will try to think of some others. I know the message indicates a connection issue but it could certainly be a user issue...I think that is more likely but it depends on your network
XAAS
  •  XAAS
  • Paid support Topic Starter
2022-07-26T15:22:59Z
1. Only allow local connection is disabled
2. Port and firewall are correct
3. it was working before and no firewall changes on our side. We just upgraded the VC from 9.9.6 to 9.9.8
4. The remote user is AD User
5. locally I can logon with the AD user but not remotely
6. logging in with admin works.
7. with admin it works. with ad user it does not work anymore.

Thank you.
Joey S
2022-07-26T15:27:57Z
delete the user and re-add
XAAS
  •  XAAS
  • Paid support Topic Starter
2022-07-26T15:41:01Z
Originally Posted by: Joey S 

delete the user and re-add



Hi Joey,

I deleted my user and re-added it. But unfortunately, it did not help.
when I tried to modify it again, the message "You need to allow active directory logon in the server Settings>Logon tab". This setting is enabled. as have mentioned I am able to login with AD user locally.

Unbenannt.png

There is also new option "identity type". When I try DNS Identity it wont login but when I try other option "windows default" or UPN Identity i am receiving the first error message I sent in the first post.

Unbenannt2.png

Thank you.

bweston
2022-07-26T16:36:44Z
https://www.visualcron.c...aspx?g=Posts&t=10586 
https://www.visualcron.c...aspx?g=Posts&t=10625 

What seems to work for me is SPN identity with a Principal name of "HOST/LOCALHOST"

However, I think what will or won't work for you depends on your domain controller setup.
XAAS
  •  XAAS
  • Paid support Topic Starter
2022-07-27T09:32:18Z
Using SPN Identity with principal FQDN solved the problem.

--
Identity Type: SPN Identity
Principal Name: servername.domain
--
Michael Fjellström
2022-11-11T14:50:17Z
Originally Posted by: XAAS 

Using SPN Identity with principal FQDN solved the problem.

--
Identity Type: SPN Identity
Principal Name: servername.domain
--


Thanks for the update/information.
Scroll to Top