Mick <[EMAIL PROTECTED]> writes: > I tried connecting to a MSWindows RealVNC server with krdc and I remember > that > I couldn't login. It could be latency across the pond, or network traffic > causing the login to time out. Eventually I ran out of patience/time and > decided to remove the login passwd and instead lock down access to the > RealVNC, MSWindows box and its network, from my IP address only.
Sounds like this is in the opposite direction from what I'm talking about. I'm not experiencing any problems connecting with linux client to windows server (tightvnc both ends). I'm not sure what `krdc' that you mention, is, but would suggest you try tightvnc on both ends. It worked for me with no problems. However trying to connect with windows (tightVnc) client to Linux (tightVNc) server fails for me without any log info or debug info whatever. Makes it hard to see how to debug the problem. -- gentoo-user@lists.gentoo.org mailing list
