pnethood - samba share mounter
To get rid of all the iconv errors, try installing this PET.
- Attachments
-
- ibm850.pet
- (4.13 KiB) Downloaded 930 times
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
5.1.1.Seems an error related to libiconv library. Which Puppy version shows it? Does Pnethood 0.6.6 with UTF-8 support shows that error?.
I am using Pnethood 0.6.6.
However,
Thanks, rcrsn51, I did, and that did get rid of them.To get rid of all the iconv errors, try installing this PET.
ibm850.pet
I think it showed 8.15.7.117What is the IP shown by the "ping" command for that machine. Please, type in terminal: "ping SHELDON".
Well, I changed the name of the Windows 98SE computer to shelasus,
so now pnethood finds SHELASUS, but no shares.
Does this have anything to do with hosts, hosts.allow, and so on?
After getting your (clarf) message, and rcrsn51's,
I commented out the existing addresses in /etc/hosts, and added a line that says
Code: Select all
192.168.1.100 shelasus
Previously, something (a DNS server somewhere?) caused
ping shelasus to try to ping 8.15.7.117
Well, now I tried
Code: Select all
smbclient -NL SHELASUS
Code: Select all
Error connecting to 8.15.7.117 (Connection refused)
I apologize for my lack of knowledge.
Thanks to both of you.
Oh. Are there files I should look at (and maybe copy) from my frugal Puppy 4.3.1?
Re: pnethood mount options
Hi Adam,adamwheeler wrote:Another problem with accessing files > 2gb after mount can be resolved with the 'lfs' (large file support) option in samba/mount-FULL.
mount-FULL -t cifs "//${IP}/${SHARE}" "${MOUNTPOINT}" -o "${SERVERNETBIOSNAME}username=${USERNAME},password=${PASSWORD},iocharset=utf8,lfs" 2>>${TMP}log
I believe there was another mount-FULL line I also had to edit.
Perhaps an 'options' box is in order.
Adam.
I´m testing the "lfs" for the mount-FULL command in Puppy 4.3.2, 214X and Quirky. The remote share is mounted but the "lfs" option is not supported.
I get this kernel error in dmesg:
Code: Select all
CIFS: Unknow mount option lfs
Does the lfs worked for you?
Greetings,
clarf
Hi sheldonisaac,sheldonisaac wrote: After getting your (clarf) message, and rcrsn51's,
I commented out the existing addresses in /etc/hosts, and added a line that saysSo now when I ping shelasus, it works. time 0.3 ms.Code: Select all
192.168.1.100 shelasus
Previously, something (a DNS server somewhere?) caused
ping shelasus to try to ping 8.15.7.117
Well, now I triedand it saysCode: Select all
smbclient -NL SHELASUS
Code: Select all
Error connecting to 8.15.7.117 (Connection refused)
You could have a problem with your DNS configuration, you could try the following solution from this thread Windows ME & Pnethood 0.65 question
Please test this solution and reply.Sit Heel Speak wrote:This may or may not directly help, but I saw the same problem just yesterday. A Win98SE computer which Puppy had previously seen the shares on, now the computer could be seen by PNetHood but the shares could not be seen.
The only difference from before, was that I had tried (on the Puppy machine) adding OpenDNS and other open-source-community DNS IP's to /etc/resolv.conf, per the instructions in this thread.
Reverting /etc/resolv.conf to the single line
nameserver 192.168.2.75
where 192.168.2.75 is my DLink DI-604 router (through it, the two machines are connected), which has DNS functionality...restored the ability of PNetHood to see the Win98SE machine's shares.
Any combination in /etc/resolv.conf of the OpenDNS etc. servers, with or without the DLink's IP, no matter whether the DLink's IP was listed first, last, or in-between, resulted in PNetHood not being able to see the Win98SE machine's shares, even though PNetHood could see the Win98SE machine.
The only way to see the Win98SE machine's shares, was to put just the single line in /etc/resolv.conf.
Greetings,
clarf
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Thank you, clarf.clarf wrote: Hi sheldonisaac,
You could have a problem with your DNS configuration, you could try the following solution from this thread Windows ME & Pnethood 0.65 question
Please test this solution and reply.Sit Heel Speak wrote: (most snipped by Sheldon)
Reverting /etc/resolv.conf to the single line
nameserver 192.168.2.75
where 192.168.2.75 is my DLink DI-604 router (through it, the two machines are connected), which has DNS functionality...restored the ability of PNetHood to see the Win98SE machine's shares.
Greetings,
clarf
I booted frugal Puppy 5.11 on the netbook, and tried with Pnethood 0.66
So I checked /etc/resolv.conf and it had two nameserver lines in it,
so I replaced all that with 192.168.1.1 which is my Linksys router.
which I've long been able to ping.
And pnethood still found SHELDON server, but said
Then I did something else, maybe rebooted.Scan completed: 192.168.0.0/16
servers found=SHELDON
started probing SHELDON
Error connecting to 8.15.7.117 (Connection refused)
(and so on)
And again made the change in /etc/resolv.conf
Then when I did Pnethood
it said stuff like
I don't know whether that succeeded because I'd recently used lameSMBqmount?cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine SHELDON
(etc etc, but then)
share=J-BCP. mountpoint=/mnt/network/SHELDON/H-BCP
(etc etc)
I'll just send this message now, and reboot?
Thanks,
Sheldon
[/quote]