Yes, D Drive is set to sharing and projectbackup does exist. I've seen that using RDP and at the pendant. Comparing the ones that don't work to the ones that do work in the windows side shows no difference between the two in share settings and security settings. Another odd thing about this is these all seem to be grouped together. There are 4 lines. The first line, all of them work as expected. Half of the next line didn't work. None of them worked on the third line. The last line, they all worked. Sort of why we reloaded the image from scratch, to make sure that an integrator didn't have a corrupted program he was shuffling around. They are not running tomorrow, so I'll check the share settings again. 3rd times the charm?
Posts by D S (YouWillObey1975)
-
-
Hello, I have 150 kuka robots that are on my network. On 120 of these robots, I can type in the address in windows explorer and access the files. For example I type in '\\10.80.200.200\d\projectbackup' and it will bring up the files where I can copy out the backups remotely (after logging in). On 30 of these robots, this type of connection doesn't work. It comes back with telling me the folder doesn't exist. I can even go up a folder to just /d and it does the same. These problem robots, I can ping them, I can RDP into them, I can connect to them in WorkVisual, but they just refuse to file share. These 150 robots are all new, within the last 2 years. They are running v8.5 and have similar hardware. They do this problem locally when plugged into either the KONI or the KLI port to weed out a network issue. I've compared settings between one that works and one that doesn't and came up with nothing. I've even reloaded the entire hard drive with a fresh image with the same result. Its the strangest thing. Another odd thing is sometimes it will ask for a password, than say the folder doesn't exist. Like it tried but gave up. I've been working on this problem off and on for 6 months. I've already reached out to Kuka and had a kuka tech look at them and he's confused by it as well. It acts like the problem is in the windows side, not in the KSS. Has anyone ran into this before?
I do it this way, because this is how my VersionDog gets its backup automatically.