KRDC no longer connects to RDP over VNC-connection

There have been several updates to krdc since you reported this bug. Does it still occur with the latest version?

Yes, it does. Using a Hardy installation, it works.

I tried to connect using gnome-rdp, but tehre I get other errors, so I'm no longer absolutely convinced that the error lies with KRDC. Maybe it's KVPN that erroneously reports a VPN-connection, which doesn't exist.

Is there any (easy) way I can verify, whether the VPN-connection atually exists?

I tried a lot in the past hours and it seems that the problem was not (only?) KRDC but rather (also?) related to KVPNC, NetworkManager and/or resolv.conf.

This is surprising given that KRDC recognized whether the server I wanted to connect to within the VPN exists, so the connection as well as the name resolution must have worked in some way. Maybe someone could give me a clue on what I could do to triage this further?

Anyway, I didn't change anything within KRDC. First I created /etc/vpnc.conf and added all the details. If this missing file caused a problem, there must be a bug within KVPNC.

Then I also edited /etc/resolv.conf and added the nameserver within the VPN as new nameserver and also added "search my.vpn.com" (where my.vpn.com is replaced by the acctual domain).

After all these changes, the connection worked.

A restart or new connection will, unfortunately, destroy the resolv.conf so it needs to be restored every time.

I'm using network-manager-gnome for connecting with my USB-modem (since knetworkmanager is currently busted), but connecting through ppp and the command line will require the same workaround. My VPN- connection is established through KVPNC.

In any case, the connection works "out of the box" under Hardy (install KVPNC, configure, connect through KRDC) and it also did so in the early stages of Intrepid. So there's definitely a bug. Is it resolv.conf? Is it the missing vpnc.conf? Or both?

Could anyone help me out how to triage this further? Are there any files worth attaching?

The problem was solved after removing the package resolvconf.

The root of the problem seems to be that resolvconf and network-manager conflict in writing to /etc/resolv.conf. resolvconf seems to get priority here but does not seem to have all relevant information, which network-manger obviously has, even though I connect through KVPNC.

It's strange, but this seems to be the only logical explanations, since network-manager has always produced a correct /etc/resolv.conf after the removal of resolvconf.

I've also switched from network-manager-gnome to network-manager-kde once it has been adapted to the new API. However, the problem persisted until I removed resolvconf.

So is this a bug in resolvconf, kdenetwork, both or something else entirely? Someone with more understanding of the matter should please correct the affected package, if necessary.

This is a bug in KVPNC. I confirmed it both on Ubuntu Hardy / Intrepid and the Nokia N810 (ARM architecture).

Reported to be a bug in krdc rather than in resolvconf.

Just a comment about the earlier alleged bug in resolvconf. If resolvconf and NetworkManager are fighting over resolv.conf then the solution is to make NetworkManager use resolvconf rather than fight it.