pnethood - samba share mounter

[sheldonisaac]

Hi sheldonisaac,

Please try latest pnethood version 0.6.6 from here http://murga-linux.com/puppy/viewtopic.php?t=60672.

Thank you very much, Clarf.

If some share is seen, then mount them using "cifs".
If you still don´t find any shares, look the log and share file in /tmp/pnethood, for any error and post them here.

A lot of text like this:

Code: Select all

-------------------------
scanning network
Scan completed: 192.168.0.0/16
servers found=SHELDON

started probing SHELDON
init_iconv: Conversion from UTF-16LE to CP850 not supported
init_iconv: Attempting to replace with conversion from UTF-16LE to ASCII
init_iconv: Conversion from UTF-8 to CP850 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from ISO-8859-1 to CP850 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP850 to UTF-16LE not supported
init_iconv: Attempting to replace with conversion from ASCII to UTF-16LE
init_iconv: Conversion from CP850 to UTF-8 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP850 to ISO-8859-1 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP850 to UTF8 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP850 to UTF-16BE not supported
init_iconv: Attempting to replace with conversion from ASCII to UTF-16BE
init_iconv: Conversion from UTF8 to CP850 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from UTF-16BE to CP850 not supported
init_iconv: Attempting to replace with conversion from UTF-16BE to ASCII
init_iconv: Conversion from UTF-16LE to CP850 not supported
init_iconv: Attempting to replace with conversion from UTF-16LE to ASCII
init_iconv: Conversion from UTF-8 to CP850 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from ISO-8859-1 to CP850 not supported
...

init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from UTF-16BE to CP850 not supported
init_iconv: Attempting to replace with conversion from UTF-16BE to ASCII
Error connecting to 8.15.7.117 (Connection refused)
SHELDON still reports no shares, checking mount in case there are shares mounted already
Trying to contact SHELDON, no shares reported
finished probing 

Why is it trying to connect to 8.15.7.117 ?
My Win98SE computer is at 192.168.1.100

Please excuse if there's something I should have been able to fix on my own.

Also post the results from command:

smbclient -NL WIN98_IP

Seems similar, ends with

Code: Select all

init_iconv: Conversion from UTF-16BE to CP850 not supported
init_iconv: Attempting to replace with conversion from UTF-16BE to ASCII
Error connecting to 8.15.7.117 (Connection refused)
Connection to WIN98_IP failed (Error NT_STATUS_CONNECTION_REFUSED)

[/quote]

[sheldonisaac]

I booted Puppy 4.31 from frugal HDD, and installed the pnethood v0.66
It shows plenty of shared directories on the networked Win98SE computer.

Maybe this and the other info will enable clarf or someone to help me get it working with lucid Puppy 5.1.1

Thanks,

Sheldon

[clarf]

A lot of text like this:

Code: Select all

-------------------------


init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from UTF-16BE to CP850 not supported
init_iconv: Attempting to replace with conversion from UTF-16BE to ASCII
Error connecting to 8.15.7.117 (Connection refused)
SHELDON still reports no shares, checking mount in case there are shares mounted already
Trying to contact SHELDON, no shares reported
finished probing 

Seems an error related to libiconv library. Which Puppy version shows it? Does Pnethood 0.6.6 with UTF-8 support shows that error?.

Why is it trying to connect to 8.15.7.117 ?

What is the IP shown by the "ping" command for that machine. Please, type in terminal: "ping SHELDON".

My Win98SE computer is at 192.168.1.100

Pnethood is looking for that class C network:

Code: Select all

Scan completed: 192.168.0.0/16 

Please excuse if there's something I should have been able to fix on my own.

Also post the results from command:

smbclient -NL WIN98_IP

Seems similar, ends with

Code: Select all

init_iconv: Conversion from UTF-16BE to CP850 not supported
init_iconv: Attempting to replace with conversion from UTF-16BE to ASCII
Error connecting to 8.15.7.117 (Connection refused)
Connection to WIN98_IP failed (Error NT_STATUS_CONNECTION_REFUSED)

Don´t worry sheldonisaac, we are learning about samba stuff

Sorry for the misunderstand with the command, I think I didn´t explain myself good enough. The command "smbclient -NL WIN98_IP" in fact is "smbclient -NL your_win98_machine_IP". In your case is:

Code: Select all

smbclient -NL SHELDON 

Good to know that Pnethood 0.6.6 worked for you. It has UTF-8 support and also add the "guest" user and password when it search for shares, when no user and password is provided by the user... I think, that could make a difference for your system.

Greetings,
clarf

[rcrsn51]

To get rid of all the iconv errors, try installing this PET.

[sheldonisaac]

Seems an error related to libiconv library. Which Puppy version shows it? Does Pnethood 0.6.6 with UTF-8 support shows that error?.

5.1.1.
I am using Pnethood 0.6.6.

However,

To get rid of all the iconv errors, try installing this PET.
ibm850.pet

Thanks, rcrsn51, I did, and that did get rid of them.

What is the IP shown by the "ping" command for that machine. Please, type in terminal: "ping SHELDON".

I think it showed 8.15.7.117

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

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: Select all

smbclient -NL SHELASUS

and it says

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?

[clarf]

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: Select all

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

[clarf]

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

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: Select all

smbclient -NL SHELASUS

and it says

Code: Select all

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

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

[sheldonisaac]

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

(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

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

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]