(old)Puppy Linux Discussion Forum

Posted: **Thu 17 Jan 2013, 15:31**

Hi.
I'd like some help on accessing shared folders using pnethood.

When I try "rescan network", the PC server (named x-pc) is found, but with "no shares".

I can access the shared folders from another windows pc.

The environment is:
Puppy 5.3.3
pnethood 0.6.9

Server:
windows 7

See attached the log error.

I appreciate any help.

Posted: **Thu 17 Jan 2013, 17:40**

have the same problems

pnethood can find my 2 PCs but impossible to share

toutou LINUX 4.3.1
PC - Windows 8
PC - MSH 2010

Posted: **Thu 17 Jan 2013, 17:59**

@martigej:

Have you been doing some upgrading? I checked in Slacko 533 and it has Pnethood 0.6.8.

Also, your error message shows that smbclient is missing libldap. But in my Slacko, no such dependency is required.

Posted: **Thu 17 Jan 2013, 18:25**

@frorgaba

Instead of Pnethood, try YASSM. It works for me in Puppy 4.3.1 with Win7 shares.

However, there have been no reports on how it works with Win8, so this may take several tries. Please report back.

Posted: **Thu 17 Jan 2013, 23:29**

Thank you for the replies.
I solved the problem simply installing "AGAIN" the packets:
- samba_mount_cifs-3.0.37-s131 and
- samba_client-3.0.37

I can't understand, because pnethood has worked some days ago....

Now I'm fighting to get "RemoteDesktop RDP client" to work...
When I click on it, nothing happens...

Any suggestion?

Thanks.

Posted: **Thu 17 Jan 2013, 23:45**

Run the executable from a console.

Posted: **Fri 18 Jan 2013, 00:12**

I don't know what is the command to run.
I tried
# rdp
return: command not found

So, I have two questions:
- What is the command for this app?
- How can I find the command for the apps installed?

Thanks.

Posted: **Fri 18 Jan 2013, 00:25**

If it's rdesktop you've got there, I'm guessing the exec's tsclient..

Posted: **Fri 18 Jan 2013, 00:47**

I ran the rdesktop from console and got the errors on image attached.

[/img]

Posted: **Fri 18 Jan 2013, 00:56**

Hmm.. that might be something rcrsn51's seen. Can you choose between rdp4, five or six on your Windows end?

Maybe check: http://www.yolinux.com/TUTORIALS/LinuxTutorialMicrosoftWindowsNetworkIntegration.html#RDP

Posted: **Fri 18 Jan 2013, 15:26**

No good Semme, but thanks. I'm still not sure what to try.

@rcrsn51, do you have any further suggestions for me?

Posted: **Sat 19 Jan 2013, 01:35**

Sorry. I don't know anything about remote desktop.

Posted: **Sat 19 Jan 2013, 06:13**

rdesktop runs with just that, rdesktop [-options]

Code: Select all

# rdesktop -help
rdesktop: A Remote Desktop Protocol client.
Version 1.7.1. Copyright (C) 1999-2011 Matthew Chapman et al.
See http://www.rdesktop.org/ for more information.

Usage: rdesktop [options] server[:port]
   -u: user name
   -d: domain
   -s: shell
   -c: working directory
   -p: password (- to prompt)
   -n: client hostname
   -k: keyboard layout on server (en-us, de, sv, etc.)
   -g: desktop geometry (WxH)
   -f: full-screen mode
   -b: force bitmap updates
   -L: local codepage
   -A: enable SeamlessRDP mode
   -B: use BackingStore of X-server (if available)
   -e: disable encryption (French TS)
   -E: disable encryption from client to server
   -m: do not send motion events
   -C: use private colour map
   -D: hide window manager decorations
   -K: keep window manager key bindings
   -S: caption button size (single application mode)
   -T: window title
   -N: enable numlock syncronization
   -X: embed into another window with a given id.
   -a: connection colour depth
   -z: enable rdp compression
   -x: RDP5 experience (m[odem 28.8], b[roadband], l[an] or hex nr.)
   -P: use persistent bitmap caching
   -r: enable specified device redirection (this flag can be repeated)
         '-r comport:COM1=/dev/ttyS0': enable serial redirection of /dev/ttyS0 to COM1
             or      COM1=/dev/ttyS0,COM2=/dev/ttyS1
         '-r disk:floppy=/mnt/floppy': enable redirection of /mnt/floppy to 'floppy' share
             or   'floppy=/mnt/floppy,cdrom=/mnt/cdrom'
         '-r clientname=<client name>': Set the client name displayed
             for redirected disks
         '-r lptport:LPT1=/dev/lp0': enable parallel redirection of /dev/lp0 to LPT1
             or      LPT1=/dev/lp0,LPT2=/dev/lp1
         '-r printer:mydeskjet': enable printer redirection
             or      mydeskjet="HP LaserJet IIIP" to enter server driver as well
         '-r sound:[local[:driver[:device]]|off|remote]': enable sound redirection
                     remote would leave sound on server
                     available drivers for 'local':
                     alsa:	ALSA output driver, default device: default
         '-r clipboard:[off|PRIMARYCLIPBOARD|CLIPBOARD]': enable clipboard
                      redirection.
                      'PRIMARYCLIPBOARD' looks at both PRIMARY and CLIPBOARD
                      when sending data to server.
                      'CLIPBOARD' looks at only CLIPBOARD.
   -0: attach to console
   -4: use RDP version 4
   -5: use RDP version 5 (default)

It works fine for me with XP and Win7.

Posted: **Sat 19 Jan 2013, 12:05**

I'm using the following line code, but the system returns with ERRORS.
Is the line code correct?

Code: Select all

sh-4.1# rdesktop -u martigej2 -p edson1 -g 1200x950 192.168.1.104
ERROR: modulus len 0x108
ERROR: send: Connection reset by peer
ERROR: Connection closed

Thank you.

Posted: **Sat 19 Jan 2013, 12:09**

Start with small steps, leave off the -p (you will be prompted for password) and -g options. Be sure that the windows user is allowed to accept remote connections. The last part is critical.

Posted: **Sat 19 Jan 2013, 12:25**

I've ran without -p and -g options but got the same errors.

Another info:
If I run from Terminal Server Client I get the same errors too.

Code: Select all

sh-4.1# rdesktop -u martigej2 192.168.1.104
ERROR: modulus len 0x108
ERROR: send: Connection reset by peer
ERROR: Connection closed

Posted: **Sat 19 Jan 2013, 13:19**

Be sure that the windows user is allowed to accept remote connections. The last part is critical.

Yes, the user is allowed.
I can access RDP from another Windows machine.

Posted: **Wed 17 Jul 2013, 23:28**

rcrsn51 wrote:@frorgaba

Instead of Pnethood, try YASSM. It works for me in Puppy 4.3.1 with Win7 shares.

However, there have been no reports on how it works with Win8, so this may take several tries. Please report back.

I have not been able to get pnethood to find a share on my Window8 PC from my Precise 5.6.1 laptop. However, using 'YASSM Samba share login' from the network menu works. Like rcrsn51 says, it took a couple of tries to find which of the 3 YASSM menu options does what I wanted.

Edit to comment - since writing the above I followed the link to the YASSM thread and was enlightened.

Posted: **Wed 17 Jul 2013, 23:37**

Thanks for that. There haven't been many reports of Puppy trying to access Win8 shared folders.

Do your Windows shares require authentication? This can be a problem with pnethood.

Posted: **Thu 18 Jul 2013, 22:13**

rcrsn51 wrote:Do your Windows shares require authentication? This can be a problem with pnethood.

No - I connect as 'Guest'. I have the share access set to 'everyone'.

I did not use the 'homegroup' nonesense, and instead tried to set up normal sharing (as in the way it was in XP and earlier).

Edit to add: I think pnethood found the shares in Slacko 5.5 - I have not used that for a while so I forget (70 next birthday, so I'm allowed)

(old)Puppy Linux Discussion Forum

pnethood can't access shared folders

pnethood can't access shared folders

same with toutoulinux in french