Puppy Linux Discussion Forum

ejb · Joined: 23 Sep 2009 Posts: 12

Patriot,

Thanks for the reply. I did some additional digging into the naslite logs
last night. I think my problem relates to the old version of naslite I was using.
I downloaded the current version, installed it and everything is now working
perfectly.

Sorry for the fire drill. Thanks for a great tool.

moonguard12 · Joined: 25 Mar 2010 Posts: 5

This is working on eeepc 700 with Lighthouse connecting to local network Vista Public share, no user no pwd. Pnethood was not seeing the share. Thank you.

toomuchcomputertime · Posted: Mon 12 Apr 2010, 10:12 Post subject:

This looks very interesting, did I miss the download link? Where can I download the latest version? I saw the alpha in an earlier post, but you are talking about a beta version?

Thanks.

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

toomuchcomputertime · Posted: Mon 12 Apr 2010, 14:02 Post subject:

Thanks, I have downloaded the most recent version. Pnethood has not been working for me. I used to use Linethood (I think) but that has not been working either.

Thanks

technosaurus · Joined: 18 May 2008 Posts: 3843

I recompiled the main samba binaries (3.0.37) and cut the size about in half, but don't have a way to test them at the moment

... just expand the tarball in the /opt/samba/bin directory (if for some reason it doesn't work just get the originals from /initrd/pup_ro2/opt/samba/bin)

Firewave · Joined: 19 May 2010 Posts: 21

I ran into a few issues with lameSMBqmount on Quirky:
- trying to mount the root share (equivalent to \\machinename in Windows) using "/" isn't working (I had this working with another Linux system at a time)
- you cannot remove that non-working "/" entry from the list of shares
- when you loose your network connection it will start to hang in a loop it seems and eats up CPU until you fix your network connection. It also prevents the shutdown of the machine (share set on automount)

gcmartin · Joined: 14 Oct 2005 Posts: 2631 Location: Earth

@Firewave, Just saw your request and though i'd offer a simple explanation.

Currently, you CANNOT create and share a folder or a file from Puppy ton any Windows machines using Microsoft/IBM CIFS technology (that what SAMBA does) because Samba appears to have been inadvertently broken in a prior release.

This is one of the drawbacks with Puppy on a LAN network that also has Windows machines.

It is my understanding that this will be addressed as soon as the current version 5 products are upgraded over the next month or 2..

Once this is done, Puppies will have FULL functionality comparable to and beyond any Windows desktop.

This post, by me, to help you, is NOT to be construed as an official statement...but, from a couple of sources, this is my understanding.

I, too, am waiting for an upcoming release that does NOT contain the current crippled version of SAMBA (that instead, has the fully working version of SAMBA that has not had its guts ripped out),so that I can begin work in this area to build a "howto" document for those who want to share information from Puppy with the LAN users including Windows as well as Linux LAN users.

disciple · Posted: Fri 30 Jul 2010, 20:31 Post subject:

gcmartin - are you sure Firewave's problem has anything to do with yours? It sounds like their problem is specifically with mounting a particular samba share from Puppy using lameSMBqmount, whereas your problem is with sharing folders in the first place (although I'm not even sure from your description whether your problem is only with Windows clients, or with Linux ones as well).

Anyway:

disciple · Posted: Fri 30 Jul 2010, 20:43 Post subject:

rcrsn51 · Posted: Fri 30 Jul 2010, 21:39 Post subject:

@gcmartin: While you are waiting, perhaps you should test the samba server package that BarryK built for you. It's here.

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

Geoffrey · Posted: Fri 06 Aug 2010, 00:20 Post subject:

Having a problem with lameSMBxplorer v0.2.1 beta browser in gray's Quirky NOP 1.2, it don't seem to scan long enough to find anything no matter what I do, the quick connect works fine if I tell it the connections, I ran it from terminal to see if that would give me some clue as to what was happening, here is the result.

# lameSMBxplorer
ScanNBT:
ScanNBT: 127.0.0.1|<unknown>||<unknown>|
127.0.0.2|<unknown>||<unknown>|
127.0.0.3|<unknown>||<unknown>|
127.0.0.4|<unknown>||<unknown>|

and the list goes on, finds nothing, my network is setup to use ip addresses in 10.1.1.1 - 255 range subnet of 255.0.0.0, is there anything I can change that will get it to work Question

Pnethood use to work ok if the scan time was set to 3, any less it would fail to find anything, any help would be appreciated.

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

This bugfix release corrects a couple of issues with the network address parser.

changelog for lameSMBxplorer v0.2.2 beta:
- bugfix (lameSMBxplorer): properly exclude localhost IP address
- bugfix (lameSMBxplorer): correctly assign private netmask classing (A/B/C)

The above logic errors was discovered based on the bug report posted by Geoffrey.

@Geoffrey,
Kindly test the latest beta and let me know how it goes.

Rgds

Geoffrey · Posted: Fri 06 Aug 2010, 10:44 Post subject:

Patriot,
Still no luck, I ran it from the terminal but this showed no output at all this time, the scan run for about 2 seconds then brings up the GUI which finds nothing, this seems quick to me, tried this on two pc's running Quirky NOP 1.2, both the same result, pnethood always took some time to find connections which are all static ip address's on all pc's and nas, is there a way to make it scan the network for a longer period the same as pnethood does.

lameSMBqmount still works fine, mounts all the shares instantly, is there anything else I can do that will give a indication of what is happening to help sort out this problem.

Geoffrey