on KRC4, vxworks controls the hardware for KLI hardware and therefore any messages sent by or arriving to KLI need to pass through vxworks. hence the need for NAT.
but i recall there is no need for that in KRC2 because there Ethernet hardware can be under control of Windows.
and like in all cases, when starting server on a windows machine, there will be firewall complaining so one would need to allow for it there.
On your KRC you have two network cards:
One is the shared memory (SMEM) with the following IP-Settings:
Windows: h=192.0.1.2
VxWorks: b=192.0.1.1
This is an internal network which can not be directly accessed from outside
(values must not be changed)
The second network card belongs to Windows and os the interface to other PCs (LAN)
The communication looks like this
KukaVarClient (PC) <-> KukaVarProxy <-> Cross3 <-> VxWorks (Base System)
It's better to put in a seperate network card (PCI).
We had some issues on Ed05 with the onboard network port using varproxy.
On older versions it's on the MFC, isa slot....
It's better to put in a seperate network card (PCI).
You need to be very careful about that. There was at least one particular case of Intel network cards whose drivers would conflict with VxWorks and bluescreen the robot, but only once every 100+ hours of uptime. Took forever to track down, and KUKA had to ship replacement 3COM cards out to every customer and do a replacement, b/c the Intel driver could not be fixed (or, more likely, Intel didn't want to bother changing their driver for such a small, niche market). In fact, the Intel driver could not be uninstalled -- replacing it required re-installing Windows and KSS from scratch. 
KUKA had approved secondary network cards for the KRC2. They were expensive, but buying a random ethernet card off Amazon or AliExpress is taking a risk. I would STRONGLY recommend making a full hard-drive backup image before adding any new hardware, just in case.
@ Skyfire
Yes sorry i should have mentioned making a backup/image first.
We never had that problem with the drivers.
Robots are running on 5.6.9
Network cards we used are realtek chipdset, not Intel.
I've successfully installed Kukavarproxy on my KRC2
Now let us go back to the roots:
Is it really a KR C2 or maybe a KR C2ed05?
What main board?
Windows 95 or WinXPe?
KSS Version?
@ SkyeFire
You are right there was a problem with the second ethernet card (Intel) for vxworks
For Windows the onbard ethernet should be used:
Intel® PRO/1000 CT Network Connection (Onboard)
(Driver: INTERNAT\TOOLS\DRIVERS\ETHERNET)
Starting with KSS V5.5.14 or rather KSS V5.6.5 the ethernet card
Intel® PRO/1000 GT Desktop Adapter (slot 6 requested)
(Driverr: INTRERNAT\TOOLS\DRIVER\Dummy\RtOsPnP_Pro1000GT_Drv.inf)
should be used for vxworks
We had some issues on Ed05 with the onboard network port using varproxy.
On older versions it's on the MFC, isa slot....
KR C2ed05 does not have any ISA slots
Thats what i said, on older versions (pre ED05)
