Page 14 of 15

Posted: Wed 29 Sep 2010, 04:58
by disciple
Mark_C wrote:Ok here are some things I tried today.
LameSMBxplorer doesn't seem to work in Lucid Puppy 5.1.1 it just scans and scans and locks up the network, I have to reboot the computer to free up the network(strange).
Interesting. I can't remember - does lameSMBxplorer use nbtscan? I have found that pnethood sometimes keeps scanning forever... if I run `killall nbtscan` it stops scanning and shows me all the shares :)

Posted: Wed 29 Sep 2010, 05:35
by pemasu
`killall nbtscan`
Nice find. For me pnethood scans forever in lucid puppies. I even posted about it in some version thread. The problem has persisted up to 5.1.1.
I tested pnethood in puppy 4.3.1. No problem in my wlan-lan home network. The search finished quickly and did find shares.

Posted: Wed 29 Sep 2010, 13:30
by Mark_C
It wont see them, it comes back with with NT_STATUS_BAD_NETWORK_NAME

rcrsn51 wrote:
I ran nbtscan and it shows 17.
16 with names and 1 unknown.
If you run

Code: Select all

smbclient -NL NAME
where NAME is the NETBIOS name of one of the other two machines, is it detected?

Posted: Wed 29 Sep 2010, 13:38
by Mark_C
I ran lameSMBxplorer and using the killall nbtscan twice it stopped and the network became usable again.
Although after it stopped it did not show anything listed in the network.



disciple wrote:
Mark_C wrote:Ok here are some things I tried today.
LameSMBxplorer doesn't seem to work in Lucid Puppy 5.1.1 it just scans and scans and locks up the network, I have to reboot the computer to free up the network(strange).
Interesting. I can't remember - does lameSMBxplorer use nbtscan? I have found that pnethood sometimes keeps scanning forever... if I run `killall nbtscan` it stops scanning and shows me all the shares :)

Posted: Thu 30 Sep 2010, 08:07
by disciple
Mark_C wrote:It wont see them, it comes back with with NT_STATUS_BAD_NETWORK_NAME
Oh. I've seen that error. It was quite hard to find the right answer (in my case) with Google :(
IIRC some causes of it may have been identified earlier in this thread though.

Posted: Fri 01 Oct 2010, 15:42
by Mobeus
I just installed pnethood 0.65 in a Debian KDE box and discovered something in the code that should probably be changed, even for Puppy. At about line 69

Code: Select all

 SUBNETS=`ifconfig | grep inet| grep -v "127.0.0.1" | grep -v P-t-P | sed 's/\ *inet 
should be

Code: Select all

 SUBNETS=`ifconfig | grep "inet "| grep -v "127.0.0.1" | grep -v P-t-P | sed 's/\ *inet 
The reason being that some ifconfig calls return a line that has Inet6 in it and that will render pnethood completely useless.

Regards,
Mobeus

Posted: Tue 05 Oct 2010, 14:35
by Mark_C
Finally figured out why Pnethood was not seeing all the shares.
My fault really, the two computers it would not see had their XP built in firewall turned on :)
I found a little program written by MU, close to the bottom of the page.
This runs from terminal and scans the network, the two showed up on the list but had an cli error, which go me to thinking about firewalls.

http://www.murga-linux.com/puppy/viewto ... ba884d4022

Posted: Fri 08 Oct 2010, 01:25
by clarf
Mark_C wrote:Finally figured out why Pnethood was not seeing all the shares.
My fault really, the two computers it would not see had their XP built in firewall turned on Smile
I found a little program written by MU, close to the bottom of the page.
This runs from terminal and scans the network, the two showed up on the list but had an cli error, which go me to thinking about firewalls.
Pnethood includes log connection files, your problem wasn´t show on them?
Mobeus wrote:I just installed pnethood 0.65 in a Debian KDE box and discovered something in the code that should probably be changed, even for Puppy. At about line 69

Code: Select all

 SUBNETS=`ifconfig | grep inet| grep -v "127.0.0.1" | grep -v P-t-P | sed 's/\ *inet 
should be

Code: Select all

 SUBNETS=`ifconfig | grep "inet "| grep -v "127.0.0.1" | grep -v P-t-P | sed 's/\ *inet 
The reason being that some ifconfig calls return a line that has Inet6 in it and that will render pnethood completely useless.

Regards,
Mobeus
Although major Puppy versions don´t have IPv6 enabled, your code is a fail save fix for customized kernel builds that include IPv6 and could be added in Pnethood.

Thank you
clarf

Posted: Mon 22 Nov 2010, 21:05
by sheldonisaac
Folks, please excuse: just installed Puppy lucid 5.11 on Acer Aspire One.
Actually on a USB "drive" plugged into the Aspire, which is Ethernet connected to my Windows 98SE desktop.

Pnethood finds no shares.

Is there any use of me, a rusty old amateur, trying to see the desktop's files from the Linux machine?

As I recall from months ago, using 4.31 ? , I was able to.
Maybe I'd used lameSMBexplorer?

Many thanks,

Sheldon Isaac

Posted: Thu 25 Nov 2010, 16:12
by clarf
Hi sheldonisaac,

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

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.

Also post the results from command:

Code: Select all

smbclient -NL WIN98_IP
Greetings,
clarf

Posted: Thu 25 Nov 2010, 17:35
by 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]

Posted: Thu 25 Nov 2010, 18:59
by 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

Posted: Sun 28 Nov 2010, 01:24
by clarf
sheldonisaac wrote: 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 
sheldonisaac wrote: 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

Posted: Sun 28 Nov 2010, 01:45
by rcrsn51
To get rid of all the iconv errors, try installing this PET.

Posted: Sun 28 Nov 2010, 03:30
by 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?

Re: pnethood mount options

Posted: Wed 08 Dec 2010, 02:23
by clarf
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: 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

Posted: Sat 18 Dec 2010, 13:03
by clarf
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: 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

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

Posted: Sat 18 Dec 2010, 16:35
by sheldonisaac
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
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]