The time now is Thu 23 May 2013, 01:45
All times are UTC - 4 |
| Author |
Message |
clarf

Joined: 13 Jun 2007 Posts: 606 Location: The old Lone Wolf
|
Posted: Tue 07 Dec 2010, 22:23 Post subject:
Re: pnethood mount options Subject description: Additional option needed for large file support. |
|
| 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. |
Hi 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: |
CIFS: Unknow mount option lfs |
Seems like the cifs module should be compiled with lfs support enabled.
Does the lfs worked for you?
Greetings,
clarf
|
|
Back to top
|
|
 |
clarf

Joined: 13 Jun 2007 Posts: 606 Location: The old Lone Wolf
|
Posted: Sat 18 Dec 2010, 09:03 Post subject:
|
|
| sheldonisaac wrote: |
After getting your (clarf) message, and rcrsn51's,
I commented out the existing addresses in /etc/hosts, and added a line that says
| Code: |
192.168.1.100 shelasus |
So now when I ping shelasus, it works. time 0.3 ms.
Previously, something (a DNS server somewhere?) caused
ping shelasus to try to ping 8.15.7.117
Well, now I tried
| Code: |
smbclient -NL SHELASUS
|
and it says
| Code: | | Error connecting to 8.15.7.117 (Connection refused) |
|
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
| 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. |
Please test this solution and reply.
Greetings,
clarf
|
|
Back to top
|
|
 |
sheldonisaac
Joined: 21 Jun 2009 Posts: 287 Location: Philadelphia, PA
|
Posted: Sat 18 Dec 2010, 12:35 Post subject:
|
|
| 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
| 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.
|
Please test this solution and reply.
Greetings,
clarf |
Thank you, 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
| Quote: |
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)
|
Then I did something else, maybe rebooted.
And again made the change in /etc/resolv.conf
Then when I did Pnethood
it said stuff like
| Quote: |
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 don't know whether that succeeded because I'd recently used lameSMBqmount?
I'll just send this message now, and reboot?
Thanks,
Sheldon
[/quote]
|
|
Back to top
|
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|