can't get kit to work with socks

[Bjorn H. <bjo...@hp...>]

I had kit working with SOCKS (I started it with "socksify kit").  Then I 
upgraded to KDE 2.2.0, and kit stopped working.  Unfortunately I don't 
know the exact version that used to work; I think it was KDE 2.1.x.

I'm using the Dante SOCKS client, and other applications still work fine 
(i.e., "socksify cvs update", "socksify ftp", etc, work).

When I start up kit with "socksify kit" and try to go online, kit dies and 
I get a message like this:

  $ socksify kit
  $ Aug 28 10:39:18 kit[766]: Rconnect(): 15.1.50.190.53

15.1.50.190 is a machine inside our firewall, but not my socks server.  
Not sure where that comes from.

When I configure SOCKS in KDE, the "Auto detect" and "Use Dante" options 
don't work (the Test button says SOCKS couldn't be loaded).  Maybe Debian 
puts Dante in a strange place.  When I specify a custom library path of 
/usr/lib/libdsocksd.so.0, the Test button says SOCKS was found and 
initialized correctly, but when I then try to start up kit, I get the 
following when trying to go online:

  $ kit
  $ Aug 28 10:45:35 KDE[773]: Rconnect(): 64.12.163.199.9898

Any suggestions or ideas of things to try would be greatly appreciated!

Bjorn