Puppy Linux Discussion Forum

[HairyWill]

[RobertB]

I got out of 2am system checks because I didn't have a Windows box at home, but my sympathy for my co-workers got the better of me. I tried the Cisco VPN client in Pizzasgood's PCPuppyOS, but it didn't connect to the work server at all. Luckily, our guy who requests IDs suggested searching on PPTP, which led to this thread!

From the internal network, RemoteDesktopClient (and RDesktop) work great! It's already clear that I'll be able to connect to my Windows workstation after all. There are some access issues on the server side, but we're working on those.

But outside of the internal network, I need to use PPTP. The packages from HairyWill do everything promised... I installed the pptpconfig.pup and his version of the "IP" command, and it runs with diagnostic messages in a window and everything.

But he admits one problem: this process doesn't update /etc/resolv.conf with the nameserver of the host system. I was able to make RemoteDesktopClient work by using an IP address I spotted in the output from ifconfig, but I can't get to the in-network Intranet -- that's the main thing I need to be able to do at 2am.

HairyWill suggests putting the nameserver in resolv.conf manually, and I'll try that tonight if I get a chance.

But what would be better for converting my Windows friends would be a way to automatically get the information. Isn't there some existing protocol for finding out the nameservers? Without that information, I may not be able to access the system at 2am. Help me be overworked *and* underpaid!

[rarsa]

This thread is just for the Remote Desktop client which assumes you already have a connection to the network where the windows computer is.

I would recommend starting a new thread for those questions and adding your comments to one of the VPN threads. You may get more comments and responses that way.

[RobertB]

[RobertB]

Ok, I'm ready to ask a RemoteDesktopClient question.

I've got it working on my laptop, which is great. Mucho happiness from my co-workers who don't have to take my place because of my non-"standard" home setup. But I can't seem to get RemoteDesktopClient to work on my desktop, which has a much bigger screen.

The worst part is not knowing what's wrong. If you hit "Connect" and the connection fails, then the GUI dialogs just go away. I'm running from the command line, but no messages are reported back there, either -- in fact, it seems to return to the # prompt whether the connection is successful or not. The only diagnostic on the console is about an apparently unrelated icon that it can't find.

I'm about to leap forward to the 1990s and get a high-speed Internet connection, so I expect to use Remote Desktop more and more. It would be nice to be able to do so on the big screen, instead of pulling out the laptop every time -- and worse yet, hoping that it works, since if it stops working I won't know why!

(Note: both the laptop and the desktop are running Puppy 2.17)

[HairyWill]

could you post whatever arguments you are using for the rdesktop command

[RobertB]

[HairyWill]

ahh I see
the remote desktop gui just builds an rdesktop command string
http://linux.die.net/man/1/rdesktop
even running rdesktop from the commandline doesn't produce any useful error messages.

I tend to use something like
rdesktop -f -k en-gb -a 15 192.168.1.2
-f fullscreen to exit this mode you need to use CTRL-ALT-RETURN
-k en-gb keyboard map
-a 15 15 bit colour depth

[kittu]

I have the remote desktop client installed and the GUI, and all the dependencies. It runs, but when I connect and log in immediately everything disappears. When the remote machine finish loading all the programs I am allow to connect again and I can remain connected until some instance like an Update from Windows begins. Any idea what i could do to make it stabler?

[HairyWill]

sorry no,
rdesktop used in dingo keeps crashing for me as well, I can't find any error messages

[paulh177]

Can I just drop into theis thread to ask -- Will, does your pptpconfig dotpup work ok with Dingo? Also have you got round to (or are you planning to) updating it to a .pet ?

paul

[HairyWill]

the php-gtk bindings are gtk1

If you want pptpconfig in puppy 4.00 you will need to install the stuff needed to make gtk1 apps work. I think all you need to do is switch the package manger to the puppy 3 repository and install gtk+12-1.2.10 I think this pulls down a couple of dependencies as well.

The lack of gtk1 was the push I needed to learn how to setup my vpn connection manually. Getting the interface up was fairly easy by hand though I think Gpptp on the network menu should do it as well. The tricky bit for me was getting the routing right. this might have been made more complicated by the fact that the machines I wanted to connect to already have public IP addresses but are firewalled to block direct ingoing connections.

[paulh177]

I've got the vpn tunnel up and running OK under 4.1 Alpha 4 (pptpconfig messes with the routing for local stuff though) in a Lin'n'Win "frugal" install .
But:

[HairyWill]

Good to know that rdesktop works in the latest alpha, that is a driver for me to test it and upgrade, I wonder what has changed?

If you want rarsa's gui then you could try installing the tcl and gnocl pets from the puppy3 repository using the package manager.

[rode]

I have got a Problem. I installed the Remotedesktopclient from this thread and when I start it, I can only see a second an then it is gone. What can I do. With the older Puppy it works perfect.