Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
VNC connection failing after upgrading from ASG2015 to ASG2016
#1
Good Morning,
I am hoping you can assist with an issue we are encountering since updating from ASG Remote Desktop 2015 to 2016. We have several hundred Kronos InTouch time clocks that make use of the VNC protocol. We are able to connect to them perfectly using ASG version 2015 but if we attempt to connect through the new version the connection never completes. When you try to connect it sticks on a screen stating "Connecting.. (SmartCode VNC viewer)"

Screen shots of both the connection set up as well as a Side by Side comparison of what we see when connecting using Version 2015 and Version 2016 have been attached.

Connection Setup:

.gif   vnc_connection_setup_screenshot.gif (Size: 45.16 KB / Downloads: 144)

Side By Side Comparison

.gif   vnc_2015v2016_comparison_screenshot.gif (Size: 403.8 KB / Downloads: 142)

Thanks!
Tedd
Tedd Moreno  |  Application Developer, Sr  |  Information Services and Technology (IST)
PeaceHealth  |  123 International Way | Springfield, OR 97477  | office 541-686-3753
Reply
#2
We didn't change the VNC component between version 2015 and 2016 - should be the same - did you compare your settings in both versions?
Regards/Gruss
Oliver
Reply
#3
Hi Oliver,
The connections were stored in a database. We created a backup of the V2015 database and restored it to another name. Then installed the 2016 client on a machine and used it to update the new copy of the DB. If we log into the original DB with 2015 software we can still make VNC connections but cannot make those same connections on the upgraded DB.

It really looks like some changes have taken place surrounding VNC. The PlugInVNC.dll library file differs from version 2015 to 2016. There are also visible differences on the "VNC Experience" submenu. I've attached a screen shot showing the differences:
 
.jpg   VNC_Experience_comparison.jpg (Size: 204.89 KB / Downloads: 101)

If it helps at all, our 2015 version is : 8.0.4872.0 .. for 2016 we have 9.0.5385.0..

I went through all of the "Tools -- > Settings" on both applications and validated that they were the same (when both apps had the setting, there were a few new ones in 2016).  The settings on the actual VNC connections are also identical. As I was going through the menus, I also ran a Components Check from the Administration menu and both versions checked out the same.

Thanks,
-Tedd
Tedd Moreno  |  Application Developer, Sr  |  Information Services and Technology (IST)
PeaceHealth  |  123 International Way | Springfield, OR 97477  | office 541-686-3753
Reply
#4
Yes you are right - we changed the UltraVNC plugin settings...

Did you try to change some values for VNC? In your pic I see that you didn't enable it in version 2015 and the same for 2016 - so should be the same... 

Do you have any VNC connection that is running well? Could you try to create a new connection to see if it makes any difference?
Regards/Gruss
Oliver
Reply
#5
Since the update to 2016 we don't have any working VNC connections. I created a new connection but it exhibits the same behavior as the others, it hangs on the "connecting" screen.

I had not tried changing any of the VNC settings. Honestly, I'm not sure what to change them to. The only devices we connect to with VNC are these time clocks. We have around 400 of them and all were setup just using the default VNC values; we add the Destination IP address, set the protocol to VNC and all the MAC address.

It seemed like the UltraVNC DSM plug-in shouldn't be the problem since we have not utilized it (not even sure our clocks could support it). It just stood out as a change in the module, which made me wonder if something else may also have changed, causing our connection issues.

Thanks again for all your time on this,
-Tedd
Tedd Moreno  |  Application Developer, Sr  |  Information Services and Technology (IST)
PeaceHealth  |  123 International Way | Springfield, OR 97477  | office 541-686-3753
Reply
#6
Tedd, could you please run the Components Check to see if your VNC control is running well - and perhaps you can try to connect via VNC on another computer using ASG-RD 2016 - perhaps a machine where no other version of ASG-RD is running - because the settings you use should run without any issues...
Regards/Gruss
Oliver
Reply
#7
Good Morning Oliver,
I can the Components Check and VNC came back as good (I've pasted the results at the bottom of this message).

It seems we are doing something wrong though as we couldn't get PC to PC connections working with VNC, either using 2016 or 2015, though we can still connect to the clocks using 2015.

When attempting to connect to a PC we get an actual error though "Failed to connect to server {ip address}. Error code: 10060...."

When attempting to connect to a clock with 2016 no error appears, just in infinite "connecting..." window. Connecting to the clock from 2015 results in an immediate connection.

RDP:
The installed RDP client is fully supported.
Installed version: 6.3.9600 (NLA supported)

HTTP/S:
Internet Explorer control was found but compatibility mode is active.
Installed version: 9.11.9600.18537

VNC:

The internal VNC component is installed and working correctly.

ICA:
The installed Citrix-Receiver is fully supported.
Installed version: 14.4.1000.16

SSH, Telnet:
PuTTY was found and the installed version is the one that is supported.
Installed version: 0.66

VMware:
VMware vSphere Client not installed. Connect to console can't be used within the application.

HyperV:
PowerShell 2.0 or higher is installed. Communication with HyperV is possible.

General:
Local operating system version: Microsoft Windows NT 6.1.7601 Service Pack 1
Program version: 9.0.5385.0
Installation path: C:\Program Files (x86)\ASG-Remote Desktop 2016
Config file (user): C:\Users\tedmor\AppData\Roaming\ASG-RemoteDesktop\9.0
Config file (all): C:\ProgramData\ASG-RemoteDesktop\9.0
Settings file: C:\Users\tedmor\AppData\Roaming\ASG-RemoteDesktop\9.0

Display Setup:
Total Monitors: 2
All Monitors Same Bounds: No
All Monitors Same Working Area: No
Overall Monitor Bounds: {X=0,Y=0,Width=3200,Height=1080}
Monitor with Largest Bounds: 1
Monitor with Smallest Bounds: 2
Monitor with Largest Working Area: 1
Monitor with Smallest Working Area: 2
Monitor 1 Details:
 Device Path: \\.\DISPLAY1
 Device Name: Intel® HD Graphics 520
 Is Primary: Yes
 Resolution: 1920x1080
 Working Area: 1920x1040
 Color Depth: 32 bit
Monitor 2 Details:
 Device Path: \\.\DISPLAY2
 Device Name: Intel® HD Graphics 520
 Is Primary: No
 Resolution: 1280x1024
 Working Area: 1280x1024
 Color Depth: 32 bit
Graphics Card(s): Intel® HD Graphics 520;
DPI: 96
Windows Theme: Aero style
Symmetric Monitor Setup: No
Your Monitor Setup: Unsupported
Tedd Moreno  |  Application Developer, Sr  |  Information Services and Technology (IST)
PeaceHealth  |  123 International Way | Springfield, OR 97477  | office 541-686-3753
Reply
#8
Hi Tedd,

how is your connection entry under the "connection" node for the specific connection ? You have choosen "VNC" and how did you specify the adress to the Kronos box ?
Do you use the IP adress under Destination ? As from your screenshots, Port settings havent changed because with the former version Port 5900 was used and it worked.
But usually you should be able to make a testconnection to another VNC Box (pc) also to verify general function. The Error 10060 is mostly found as a timeout for the vnc
connection that points more or less to a firewall problem. But if it works with RD2015 that doesnt make sense here... ; For my testings I use a linux box with x11vnc and make sure server runs on port 5900. Then I make sure to use VNC as protocol in connections , use the Target IP in the Destination field and verify the port in the vnc node. That should be it. Off course port must be enabled.

Best regards,
Michael
-- michael.scholz@asg.com --
Reply
#9
Good Morning,
Sorry for the long delay on this response.

The destination is set up as an IP address. When we created the connections we just entered each device's IP address and left all other fields with default values. If I use the previous version of ASG, 2015, then the connection works fine. If I use a different application (VNCViewer 6.0.2 from realvnc.com) the connection works fine. But if I use ASG2016 it just "sticks" on the connection window.

I ran a quick test comparing 2015 to 2016 and VNCViewer, with Wireshark monitoring the host. Below are snippets from the 3 outputs. It's worth nothing that in the ASG2016 output there are a number of errors stating "Unknown server message type". This error does only appears when using ASGRD-2016.

Thanks,
-tedd

VNC Viewer:
No. Time Source Destination Protocol Length Info
1 0 170.96.158.81 170.96.112.237 TCP 66 52782  >  5900 [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
2 0.007782 170.96.112.237 170.96.158.81 TCP 66 5900  >  52782 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 SACK_PERM=1 WS=32
3 0.007913 170.96.158.81 170.96.112.237 TCP 54 52782  >  5900 [ACK] Seq=1 Ack=1 Win=65536 Len=0
4 0.015708 170.96.112.237 170.96.158.81 VNC 66 Server protocol version: 003.003
5 0.075519 170.96.158.81 170.96.112.237 VNC 66 Client protocol version: 003.003
6 0.084886 170.96.112.237 170.96.158.81 TCP 60 5900  >  52782 [ACK] Seq=13 Ack=13 Win=5856 Len=0
7 0.089333 170.96.112.237 170.96.158.81 VNC 74 Security types supported
8 0.298875 170.96.158.81 170.96.112.237 TCP 54 52782  >  5900 [ACK] Seq=13 Ack=33 Win=65536 Len=0
9 4.575548 170.96.158.81 170.96.112.237 VNC 70 Authentication challenge from server
10 4.594107 170.96.112.237 170.96.158.81 VNC 60 Authentication response from client[Malformed Packet]
11 4.594279 170.96.158.81 170.96.112.237 VNC 55 Authentication response from client[Malformed Packet]
12 4.612252 170.96.112.237 170.96.158.81 VNC 108 Authentication response from client
13 4.618311 170.96.158.81 170.96.112.237 VNC 106 Authentication result
14 4.631754 170.96.158.81 170.96.112.237 VNC 74 Authentication result
15 4.646081 170.96.112.237 170.96.158.81 TCP 60 5900  >  52782 [ACK] Seq=91 Ack=102 Win=5856 Len=0
16 4.648468 170.96.112.237 170.96.158.81 VNC 133 Share desktop flag
17 4.649946 170.96.158.81 170.96.112.237 VNC 64 Server framebuffer parameters[Malformed Packet]
18 4.65055 170.96.158.81 170.96.112.237 VNC 106 Server framebuffer parameters
19 4.650577 170.96.158.81 170.96.112.237 VNC 64 Client framebuffer update request
20 4.659065 170.96.112.237 170.96.158.81 TCP 60 5900  >  52782 [ACK] Seq=170 Ack=174 Win=5856 Len=0
21 4.659095 170.96.112.237 170.96.158.81 VNC 133 Server framebuffer update; Unknown server message type
22 4.666799 170.96.158.81 170.96.112.237 VNC 60 Client pointer event
23 4.703652 170.96.112.237 170.96.158.81 TCP 60 5900  >  52782 [ACK] Seq=249 Ack=180 Win=5856 Len=0
24 4.817975 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer update; Server cut text; Server framebuffer update
25 4.818116 170.96.112.237 170.96.158.81 TCP 1514 [TCP segment of a reassembled PDU]
26 4.818154 170.96.158.81 170.96.112.237 TCP 54 52782  >  5900 [ACK] Seq=180 Ack=3169 Win=65536 Len=0
27 4.819908 170.96.112.237 170.96.158.81 TCP 1514 [TCP segment of a reassembled PDU]
28 4.820287 170.96.112.237 170.96.158.81 TCP 1514 [TCP segment of a reassembled PDU]
29 4.820288 170.96.112.237 170.96.158.81 TCP 1514 [TCP segment of a reassembled PDU]
30 4.820322 170.96.158.81 170.96.112.237 TCP 54 52782  >  5900 [ACK] Seq=180 Ack=7549 Win=65536 Len=0
31 4.828612 170.96.112.237 170.96.158.81 TCP 1514 [TCP segment of a reassembled PDU]
32 4.828613 170.96.112.237 170.96.158.81 TCP 1514 [TCP segment of a reassembled PDU]
33 4.828614 170.96.112.237 170.96.158.81 TCP 1514 [TCP segment of a reassembled PDU]
34 4.828665 170.96.158.81 170.96.112.237 TCP 54 52782  >  5900 [ACK] Seq=180 Ack=11929 Win=65536 Len=0
35 4.829913 170.96.112.237 170.96.158.81 TCP 1514 [TCP segment of a reassembled PDU]
36 4.829927 170.96.112.237 170.96.158.81 TCP 999 [TCP segment of a reassembled PDU]
37 4.829956 170.96.158.81 170.96.112.237 TCP 54 52782  >  5900 [ACK] Seq=180 Ack=14334 Win=65536 Len=0
38 4.83019 170.96.158.81 170.96.112.237 VNC 106 Client set encodings
39 4.83072 170.96.158.81 170.96.112.237 VNC 74 Client set pixel format

ASGRD2015:
No. Time Source Destination Protocol Length Info
1 0 170.96.158.81 170.96.112.237 TCP 66 53115  >  5900 [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
2 0.008875 170.96.112.237 170.96.158.81 TCP 66 5900  >  53115 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 SACK_PERM=1 WS=32
3 0.008989 170.96.158.81 170.96.112.237 TCP 54 53115  >  5900 [ACK] Seq=1 Ack=1 Win=65536 Len=0
4 0.01689 170.96.112.237 170.96.158.81 VNC 66 Server protocol version: 003.003
5 0.01707 170.96.158.81 170.96.112.237 VNC 66 Client protocol version: 003.003
6 0.024872 170.96.112.237 170.96.158.81 TCP 60 5900  >  53115 [ACK] Seq=13 Ack=13 Win=5856 Len=0
7 0.024986 170.96.112.237 170.96.158.81 VNC 74 Security types supported
8 0.025153 170.96.158.81 170.96.112.237 VNC 70 Authentication challenge from server
9 0.03487 170.96.112.237 170.96.158.81 VNC 60 Authentication response from client[Malformed Packet]
10 0.036131 170.96.158.81 170.96.112.237 VNC 55 Authentication response from client[Malformed Packet]
11 0.042871 170.96.112.237 170.96.158.81 VNC 108 Authentication response from client
12 0.054849 170.96.158.81 170.96.112.237 VNC 74 Authentication result
13 0.054892 170.96.158.81 170.96.112.237 VNC 110 Authentication result
14 0.055301 170.96.158.81 170.96.112.237 VNC 64 Authentication result
15 0.062913 170.96.112.237 170.96.158.81 TCP 60 5900  >  53115 [ACK] Seq=91 Ack=116 Win=5856 Len=0
16 0.065343 170.96.112.237 170.96.158.81 VNC 189 Authentication result
17 0.065344 170.96.112.237 170.96.158.81 VNC 66 Authentication result
18 0.06537 170.96.158.81 170.96.112.237 TCP 54 53115  >  5900 [ACK] Seq=116 Ack=238 Win=65280 Len=0
19 0.073655 170.96.112.237 170.96.158.81 VNC 1514 Share desktop flag
20 0.073879 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
21 0.07393 170.96.158.81 170.96.112.237 TCP 54 53115  >  5900 [ACK] Seq=116 Ack=3158 Win=65536 Len=0
22 0.073956 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
23 0.075725 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
24 0.07575 170.96.158.81 170.96.112.237 TCP 54 53115  >  5900 [ACK] Seq=116 Ack=6078 Win=65536 Len=0
25 0.075804 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
26 0.075977 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
27 0.075989 170.96.158.81 170.96.112.237 TCP 54 53115  >  5900 [ACK] Seq=116 Ack=8998 Win=65536 Len=0
28 0.081649 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
29 0.089998 170.96.158.81 170.96.112.237 TCP 54 53115  >  5900 [ACK] Seq=116 Ack=10458 Win=65536 Len=0
30 0.091983 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
31 0.092073 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
32 0.092099 170.96.158.81 170.96.112.237 TCP 54 53115  >  5900 [ACK] Seq=116 Ack=13378 Win=65536 Len=0
33 0.092211 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
34 0.092385 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
35 0.092391 170.96.158.81 170.96.112.237 TCP 54 53115  >  5900 [ACK] Seq=116 Ack=16298 Win=65536 Len=0
36 0.09252 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
37 0.092631 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
38 0.092639 170.96.158.81 170.96.112.237 TCP 54 53115  >  5900 [ACK] Seq=116 Ack=19218 Win=65536 Len=0
39 0.092785 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]

ASGRD2016:
No. Time Source Destination Protocol Length Info
1 0 170.96.158.81 170.96.112.237 TCP 66 52686  >  5900 [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
2 0.015408 170.96.112.237 170.96.158.81 TCP 66 5900  >  52686 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 SACK_PERM=1 WS=32
3 0.015516 170.96.158.81 170.96.112.237 TCP 54 52686  >  5900 [ACK] Seq=1 Ack=1 Win=65536 Len=0
4 0.027435 170.96.112.237 170.96.158.81 VNC 66 Server protocol version: 003.003
5 0.027642 170.96.158.81 170.96.112.237 VNC 66 Client protocol version: 003.003
6 0.04013 170.96.112.237 170.96.158.81 TCP 60 5900  >  52686 [ACK] Seq=13 Ack=13 Win=5856 Len=0
7 0.041382 170.96.112.237 170.96.158.81 VNC 74 Security types supported
8 0.041527 170.96.158.81 170.96.112.237 VNC 70 Authentication challenge from server
9 0.060181 170.96.112.237 170.96.158.81 VNC 60 Authentication response from client[Malformed Packet]
10 0.061263 170.96.158.81 170.96.112.237 VNC 55 Authentication response from client[Malformed Packet]
11 0.075824 170.96.112.237 170.96.158.81 VNC 108 Authentication response from client
12 0.077133 170.96.158.81 170.96.112.237 VNC 74 Authentication result
13 0.077152 170.96.158.81 170.96.112.237 VNC 134 Authentication result
14 0.091135 170.96.158.81 170.96.112.237 VNC 64 Authentication result
15 0.09143 170.96.112.237 170.96.158.81 VNC 189 Authentication result
16 0.091431 170.96.112.237 170.96.158.81 VNC 66 Authentication result
17 0.091481 170.96.158.81 170.96.112.237 TCP 54 52686  >  5900 [ACK] Seq=140 Ack=238 Win=65280 Len=0
18 0.116373 170.96.112.237 170.96.158.81 VNC 1514 Share desktop flag
19 0.116527 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
20 0.116578 170.96.158.81 170.96.112.237 TCP 54 52686  >  5900 [ACK] Seq=140 Ack=3158 Win=65536 Len=0
21 0.116714 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
22 0.116997 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
23 0.117025 170.96.158.81 170.96.112.237 TCP 54 52686  >  5900 [ACK] Seq=140 Ack=6078 Win=65536 Len=0
24 0.1302 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
25 0.130757 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
26 0.130811 170.96.158.81 170.96.112.237 TCP 54 52686  >  5900 [ACK] Seq=140 Ack=8998 Win=65536 Len=0
27 0.130877 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
28 0.132266 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
29 0.1323 170.96.158.81 170.96.112.237 TCP 54 52686  >  5900 [ACK] Seq=140 Ack=11918 Win=62720 Len=0
30 0.148477 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
31 0.14866 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
32 0.148679 170.96.158.81 170.96.112.237 TCP 54 52686  >  5900 [ACK] Seq=140 Ack=14838 Win=59648 Len=0
33 0.148836 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters[Malformed Packet]
34 0.148964 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer parameters
35 0.148977 170.96.158.81 170.96.112.237 TCP 54 52686  >  5900 [ACK] Seq=140 Ack=17758 Win=56832 Len=0
36 0.160218 170.96.112.237 170.96.158.81 VNC 1514 Server ring bell on client; Server framebuffer update; Unknown server message type
37 0.160365 170.96.112.237 170.96.158.81 VNC 1514 Server framebuffer update; Unknown server message type
38 0.160384 170.96.158.81 170.96.112.237 TCP 54 52686  >  5900 [ACK] Seq=140 Ack=20678 Win=54016 Len=0
39 0.160501 170.96.112.237 170.96.158.81 VNC 1514 Unknown server message type
Tedd Moreno  |  Application Developer, Sr  |  Information Services and Technology (IST)
PeaceHealth  |  123 International Way | Springfield, OR 97477  | office 541-686-3753
Reply
#10
Hi Tedd,

thanks for your efforts trying to find out whats going on here. We also want to find a solution here, but we need additional input from you side: could you find out what kind and version of VNC Server runs on your Kronos Box ?
Because there are differnet versions of VNC/UltraVnC and not all are really compatibel to each other. The error you captured with wireshark maybe points to a problem that has to do with some incompatibility.

Thanks,
Michael
-- michael.scholz@asg.com --
Reply
#11
Hi Michael,
The software is installed on our time clocks and they don't have much of an interface for trying to gather that data. A quick search does reveal that it uses "TightVNC Viewer" but doesn't have any versioning information. I have entered a ticket with the vendor asking for the information.

I will be out of the office for the next 2 weeks though, so unless they get back to me by tomorrow, this post will be on hold again for a bit. Thanks for all your patience with the sporadic responses from my side Smile

-tedd
Tedd Moreno  |  Application Developer, Sr  |  Information Services and Technology (IST)
PeaceHealth  |  123 International Way | Springfield, OR 97477  | office 541-686-3753
Reply
#12
Hi Michael,
The vendor was not able to get the full version information for us. Here's a quote with the information they were able to give:



VncViewer.jar is packaged in the rpm called fbserver-1.0-5.armv6jel_vfp. VncViewer is a java based open source library that's using TightVNC viewer applet with Xvnc.

After finding out the above, I checked the package:
rpm -qil fbserver
Name : fbserver Relocations: (not relocatable)
Version : 1.0 Vendor: Kronos
Release : 5 Build Date: Wed May 16 17:18:34 2012
Install Date: Wed May 16 18:46:05 2012 Build Host: windriver-dev
Group: Applications/System Source RPM: fbserver-1.0-5.src.rpm
Size: 302098 License: Kronos
Signature: (none)
Packager: Kronos Incorporated <http://www.kronos.com>
Summary: The vnc viewer
Description: The vnc viewer
/etc/RAS
/etc/RAS/rasconfig.ini
/root/.vnc
/root/.vnc/vncpass
/usr/bin/fbserver
/usr/bin/storepasswd
/usr/local/RAS
/usr/local/RAS/classes
/usr/local/RAS/classes/VncViewer.class
/usr/local/RAS/classes/VncViewer.jar
/usr/local/RAS/classes/index.vnc
/usr/local/bin/storepasswd

I opened up the VncViewer.jar and found this in the manifest:
Manifest-Version: 1.0
Created-By: 1.6.0_07 (Sun Microsystems Inc.)
Main-Class: VncViewer

The zipped up JAR file from the clock has been added as an attachment to this thread, if that helps.

Thanks!
-tedd


Attached Files
.zip   VncViewer.zip (Size: 58.91 KB / Downloads: 82)
Tedd Moreno  |  Application Developer, Sr  |  Information Services and Technology (IST)
PeaceHealth  |  123 International Way | Springfield, OR 97477  | office 541-686-3753
Reply
#13
Hi Tedd,

thanks for your efforts in finding out more about the used version. But I think the problem is not a viewer...the Kronos box has a vnc server that is connected by our viewer. But I don't have the ressources to dive deep into the VNC protocol. But hopefully we can get rid of the problem with our new version of ASG-RD that will be released soon: we implemented an updated VNC component !
You will see the announcement here in the forum and / or see that an update will be available after starting ASG-RD, when the new version is released.

Best regards,
Michael
-- michael.scholz@asg.com --
Reply
#14
Good Morning Michael,
Thanks for your time on this. I'll keep an eye out for that update.

Thanks!
-tedd
Tedd Moreno  |  Application Developer, Sr  |  Information Services and Technology (IST)
PeaceHealth  |  123 International Way | Springfield, OR 97477  | office 541-686-3753
Reply
#15
Hi Michael,
I have some news. I downloaded the new 2017 version and am experiencing the same issues. However, I have more detail now (and a work around). I've found that the never-ending connecting window can be eliminated by turning off Auto-Size on the "VNC Experience" settings. I tried to do this at the root level and use inheritance to adjust the settings on child objects but it didn't work. However, if I do a multi-edit connections and set Auto size to "none" on each individual connection we are in business.

Thanks,
-tedd
Tedd Moreno  |  Application Developer, Sr  |  Information Services and Technology (IST)
PeaceHealth  |  123 International Way | Springfield, OR 97477  | office 541-686-3753
Reply
#16
I know I am dragging up a 2 month old thread, but we are having a similar issue with our Kronos In-Touch clocks with ASG 2017. We have previously been using Visionapp 2010 with no issues, but upon adding the first clock and testing, we don't get the spinning connection, we get an Unhandled Exception error. This happens on all three boxes we have the application installed on.

We haven't had issues with any of the other connection types, only this one.
Reply
#17
Did you run the components check? We see in many installations that the VNC registration fails and has to be done manually again in Components Check
Regards/Gruss
Oliver
Reply




Users browsing this thread: 1 Guest(s)