Not sure what you are trying to do but it works perfectly straight right out of the box. All the relevant programs are installed ny default.
Set initially the transfer seettings to the smallest to start with -- don't use screen resolutions that your LOCAL machine can't handle either.
My SUSE installations are also "Bog Standard" but with current online updates done.
1) On the local machine start ssl and connect to the remote machine.
2) on the console type vncserver and make a note of what display number you get
start another console session on the LOCAL machine and type vncviewer (or use KDE's menu doesn't matter). Try using the stand alone program vncviewer first instead of the KDE service as this will isolate the problem a bit --is it a vnc problem or a KDE defect.
You should get a prompt asking you for the server (if you typed vncviewer it will be a little window otherwise a kde screen will appear).
For testing - saves mucking about with DNS entries and other extra problems type in the ipaddress followed by the number of the display you got when starting the vnc server on the REMOTE machine
for example 192.168.1.5:1 ensure the display number is preceeded via a :
Enter your password / pass phrase depending on how you've set up your logon to the remote machine. Just start with normal methods i.e a password. You can do fancy things like adding keys and pass phrases later.
You should then see a blank X screen.
Start your X server --if you are using KDE type KDE START rather than STARTX.
You should see your REMOTE kde screen on your LOCAL machine.
If you want to logon to a Windows machine then type in RDP:/IP address. You don't need any extra info.
I'm running a Windows VM both on the Local and Remote Machine
Here's a screen shot of VNC showing the REMOTE KDE on the local machine.
http://www.1kyle.com/fstest1.jpg
And here's another screen shot showing the LOCAL Windows VM using RDP (Remote desktop) to the Remote Windows Machine which I've got running in full screen mode.
http://www.1kyle.com/fstest2.jpg
Both windows machines are running as Virtual Machines under VMWARE.
For testing I'd suggest you switch off all firewalls if you are testing over a local network.
Where you *might* have a problem is trying to connect remotely from a 64 bit machine to a 32 bit machine (or the other way around) - not sure how the video will work here.
Connecting via 32 bit machines or 64 bit machines works fine. I haven't tested "Mixed" architecture but in theory if the programs are obeying standard protocols it should work.
Cheers
-K
