Code: Select all
SUBNETS=`ifconfig | grep inet| grep -v "127.0.0.1" | grep -v P-t-P | sed 's/\ *inet
Code: Select all
SUBNETS=`ifconfig | grep "inet "| grep -v "127.0.0.1" | grep -v P-t-P | sed 's/\ *inet
Regards,
Mobeus
Code: Select all
SUBNETS=`ifconfig | grep inet| grep -v "127.0.0.1" | grep -v P-t-P | sed 's/\ *inet
Code: Select all
SUBNETS=`ifconfig | grep "inet "| grep -v "127.0.0.1" | grep -v P-t-P | sed 's/\ *inet
Pnethood includes log connection files, your problem wasn´t show on them?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.
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.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 69should beCode: 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.Code: Select all
SUBNETS=`ifconfig | grep "inet "| grep -v "127.0.0.1" | grep -v P-t-P | sed 's/\ *inet
Regards,
Mobeus
Code: Select all
smbclient -NL WIN98_IP
Thank you very much, Clarf.Hi sheldonisaac,
Please try latest pnethood version 0.6.6 from here http://murga-linux.com/puppy/viewtopic.php?t=60672.
A lot of text like this: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.
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
Seems similar, ends withAlso post the results from command:
smbclient -NL WIN98_IP
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)
Seems an error related to libiconv library. Which Puppy version shows it? Does Pnethood 0.6.6 with UTF-8 support shows that error?.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
What is the IP shown by the "ping" command for that machine. Please, type in terminal: "ping SHELDON".Why is it trying to connect to 8.15.7.117 ?
Pnethood is looking for that class C network:My Win98SE computer is at 192.168.1.100
Code: Select all
Scan completed: 192.168.0.0/16
Don´t worry sheldonisaac, we are learning about samba stuffsheldonisaac wrote: Please excuse if there's something I should have been able to fix on my own.
Seems similar, ends withAlso post the results from command:
smbclient -NL WIN98_IPCode: 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)
Code: Select all
smbclient -NL SHELDON
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?.
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".
Code: Select all
192.168.1.100 shelasus
Code: Select all
smbclient -NL SHELASUS
Code: Select all
Error connecting to 8.15.7.117 (Connection refused)
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.
Code: Select all
CIFS: Unknow mount option lfs
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)
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.
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
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)
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)