pnethood - samba share mounter

[clarf]

Well, I´m using a modified code for the mount command.

Basically, I added to mount commands:

1. The iocharset=utf8 parameter when using cifs.
2. The workgroup=$DOMAINID parameter if user enabled Domain action (with and without cifs)

clarf

[Mark_C]

clarf

Would you know if Pnethood has some sort of limitation on the number of computers it can see on the network?
We have 19 computers at work and it will only see 17 of them.

The two it doesn't see are the last two I set up for new employees, I originally thought maybe I had done something wrong setting them up but they see the whole network and others can see them.
I then booted puppy 3 and Linneighborhood sees all 19 so I figure it is something in pnethood.


Mark

[disciple]

Can lameSMBxplorer see them?

[Mark_C]

I am pretty sure I tried LameSMBxplorer but I don't remember the results.
It either saw less or the same, I will have to try it again Monday and see what it does.

The strange thing is that some older Puppy versions with Pnethood only see 10 computers, even though they say they are the same version of Pnethood as in Lucid Puppy so there must be some difference.

I tried installing Linneighborhood in Lucid 5.1.1 and it works, except you cant mount the shares, it seems at some point Mtab was changed to a symbolic link and that messes up the mounting of shares. I tried changing Mtab to make it not a link and after that you can mount the shares but the system changes it back to a symbolic link on reboot.

[Sit Heel Speak]

Would you know if Pnethood has some sort of limitation on the number of computers it can see on the network?

Two years ago, I saw a network of 12 Windows XP machines on which PNethood would see only 11 unless the scan time was raised.

[Mark_C]

I set it to 30 seconds, which is the max on the menu, but it didn't make a difference, thank you for the tip though.

Would you know if Pnethood has some sort of limitation on the number of computers it can see on the network?

Two years ago, I saw a network of 12 Windows XP machines on which PNethood would see only 11 unless the scan time was raised.

[Mark_C]

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).

So I tried it in Fluppy and it sees 14 computers.

[rcrsn51]

Just out of curiosity, what happens if you run nbtscan from the command line. Can it see all the machines?

[Mark_C]

I ran nbtscan and it shows 17.
16 with names and 1 unknown.

Just out of curiosity, what happens if you run nbtscan from the command line. Can it see all the machines?

[rcrsn51]

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?

[disciple]

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

[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.

[Mark_C]

It wont see them, it comes back with with NT_STATUS_BAD_NETWORK_NAME

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?

[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.

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

[disciple]

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.

[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

[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

[clarf]

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?

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

[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

[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