Remote Desktop on KSS 8.6

You could compare KLIConfig.xml between your two installations. The port for RDP must be allowed and is blocked by default. This was also the case in V8.5. But maybe someone already opened the port inside your V8.5 in the past ...

Fubini

Quote

RDP feature was removed from 8.6 version. So strange desision.

Not really. Might be a problem with SPOC.

From version 8.6 and newer you need the option KUKA.RemoteSupportView for a proper RDP connection. This is what KUKA Germany told me and I can confirm that I was never able to connect via RDP with a KSS 8.6 (or newer) controller without having the above option.

For versions older than 8.6 it was always possible to connect with adapting the KLIConfig.xml.

Just as reminder:

kss v8.3 up to kss 8.5 used os win7

kss v8.6 and kss v8.7 using win10

Question:

what could be the difference causing your problem

its a question of selling software. why allowing free software if u can sell RemoteSupportView.

(wich works fine and the integration in WoV is nice and works for once too)

i was working on OPS running KSS8.6 earlier this week (translating some UserTech ).

I can confirm that RDP works the same way as on KSS8.5 (as far as i could tell...)

I think RemoteSupportView is causing something to lock up and require a reboot sometimes when I push updates but I haven't had time to verify that it's the cause. I've been trying to get RDP to work on KSS8.6, but it keeps timing out. I went through the suggested actions - the system is powered on, I can ping its IP address, and remote access is enabled as far as I can tell - but without any luck. I was able to RDP into a KSS8.5 robot when it was here a month ago with no problem. Panic mode is the first person I've seen so far who has been able to RDP into KSS8.6 successfully.

I'm commissioning my first KRC4 Compact with KSS8.6 these days. It can be reached using remote desktop when connected to X69, but not over X66. No idea why. Buuuuuuut... I've installed TightVnc, enabled "Connect to RDP sessions" from its settings panel, created an entry for it in kliconfig and we're back to KRC2 times!

Finally, got the success in making RDP work on KSS8.6.9. You have to modify 2 files on the robot controller:

KLIConfig.xml at KRC/Roboter/config/user/common

KagaConfig.xml at KRC/Roboter/Config/System/Cabinet/

Find the lines with the entry:

<NATRule>rdr [GlobalNatInterface] [addr] port 3389 -&gt; [host:WINDOWS] port 3389 tcp proxy RemoteIP</NATRule>

and replace it with:

<NATRule>rdr [GlobalNatInterface] [addr] port 3389 -&gt; [host:WINDOWS] port 3389 tcp</NATRule>

Please note that there are two entries in the file KagaConfig.xml.

Regards

happened to be near robots so just confirmed that this works on real robot controllers:

KRC4 with KSS 8.6

KRC5 with KSS 8.7

Quote from s2007.ravi

Finally, got the success in making RDP work on KSS8.6.9. You have to modify 2 files on the robot controller:

KLIConfig.xml at KRC/Roboter/config/user/common

KagaConfig.xml at KRC/Roboter/Config/System/Cabinet/

Find the lines with the entry:

Code

<NATRule>rdr [GlobalNatInterface] [addr] port 3389 -&gt; [host:WINDOWS] port 3389 tcp proxy RemoteIP</NATRule>

and replace it with:

Code

<NATRule>rdr [GlobalNatInterface] [addr] port 3389 -&gt; [host:WINDOWS] port 3389 tcp</NATRule>

Please note that there are two entries in the file KagaConfig.xml.

Regards

Display More

Thank you s2007.ravi!!

Just a small addition for future readers, In order for this configuration to register. A reboot with "Reload files" check box marked, need to be executed

I can confirm this works with a C5 micro with KSS 8.7.4

I can connect by using an RDP client with the following settings

host: <IP of robot>

name: KukaUser

pass: 68kuka1secpw59

I have an ethernet cable plugged into the XF5 / KLI port

Jumping on the thread, thanks everyone for the contributions, tried what @s2007.ravi suggested, it worked on the KR5 Micro. KSS 8.7.5