Yet Another Samba Share Mounter

Configuration wizards, scanners, remote desktop, etc.
Message
Author
User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#21 Post by rcrsn51 »

sheldonisaac wrote:Version 1.3 gave the "No connection to xxx-share!"
I may have to set up a Win98 machine to test this properly. :wink:

Since v1.1 worked, can you do one more test with v1.3? In the Options box, type dom=WORKGROUP. That's the only significant difference between the two versions and maybe the Win98 server needs it.

sheldonisaac
Posts: 902
Joined: Mon 22 Jun 2009, 01:36
Location: Philadelphia, PA

#22 Post by sheldonisaac »

rcrsn51 wrote:
sheldonisaac wrote:Version 1.3 gave the "No connection to xxx-share!"
I may have to set up a Win98 machine to test this properly. :wink:

Since v1.1 worked, can you do one more test with v1.3? In the Options box, type dom=WORKGROUP. That's the only significant difference between the two versions and maybe the Win98 server needs it.
I guess that it's been found to work with such as Windows 2000, XP, etc

OK, I will try the dom=WORKGROUP later this afternoon.

Thanks.

(I'm posting from Opera 10.63 on the "Windows" box, under Puppy '214X-top5')

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#23 Post by rcrsn51 »

Just to be clear - are you testing with Lupu or with 214x?

Also, could you do a test by putting some dummy data in the Username and Password fields?

sheldonisaac
Posts: 902
Joined: Mon 22 Jun 2009, 01:36
Location: Philadelphia, PA

Testing the YASSM

#24 Post by sheldonisaac »

rcrsn51 wrote:Just to be clear - are you testing with Lupu or with 214x?

Also, could you do a test by putting some dummy data in the Username and Password fields?
Will try.

I've been, and will, test with Lupu, Puppy 5.11 from the netbook, to Win98se on _this_ box

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

(a little later)

I _think_ I'm using ver 1.3

The log-in worked with only the share and server (in CAPS). I think it did before? Maybe it was only the Samba share selector which didn't work.

Not sure whether this is what you meant, rcrsn51 ? I did the log-in with dom=WORKGROUP, also worked.

Next: filled in dummy data in the Username and Password fields, but left options blank. Worked.

Next: same as above, but with dom=WORKGROUP. Worked.

Will do one more try, with lower case server and share. Doesn't work.

==============

Tried the Samba share selector with the following .dat,worked.

Code: Select all

#1# Don't change the first nine lines of this file!
#2# The data starts on Line 10.
#3# Each line of data describes a network share.
#4# There are six fields separated by commas. See the sample data below.
#5# The fields are: description, username, password, share, server, workgroup
#6# If the share does not require a login, leave the username and password fields blank.
#7# The workgroup field is optional.
#8# The last line of the file must be EOF.
#9#
BCP,guest,xxx,H-BCP,SHELDON,dom=workgroup
Sources,guest,xxx,SOURCES,SHELDON,dom=WORKGROUP
EOF
Not sure this is version 1.3?
Can you tell from the file dates etc, at bottom?
ls -alt
total 44
drwxr-xr-x 3 root root 4096 2010-12-19 16:56 .
-rw-r--r-- 1 root root 551 2010-12-19 16:56 samba-shares.dat
-rw-r--r-- 1 root root 547 2010-12-19 16:55 samba-shares.dat~
-rw-r--r-- 1 root root 614 2010-12-19 16:43 dec19-samba-shares.dat
drwxr-xr-x 2 root root 4096 2010-12-19 16:17 saved
-rwxr-xr-x 1 root root 2372 2010-12-19 12:03 samba-shares
-rwxr-xr-x 1 root root 2999 2010-12-19 12:02 samba-login
-rw-r--r-- 1 root root 50 2010-12-19 08:06 samba-login.set
-rw-r--r-- 1 root root 2853 2010-10-16 13:20 samba-menu.xpm
drwxr-xr-x 3 root root 4096 2010-10-13 11:48 ..
-rw-r--r-- 1 root root 3563 2010-10-08 18:51 samba-login.png

User avatar
davids45
Posts: 1326
Joined: Sun 26 Nov 2006, 23:33
Location: Chatswood, NSW

#25 Post by davids45 »

G'day,
I have been trying your Samba-TNG pet and been happily surprised that it works with three different XP computers on my home network using \\pupserver.

Is the package you've offered in this thread different to those Samba-TNG pets in a way you could outline? I'll be trying this one anyway when I get the chance.

Re the Samba-TNG, I think when I've tried it as a server on my main desktop, when I shut down that Pup, it takes many seconds longer to close - is there be something I should be doing to get the normal quick Puppy close? I found this prolonged shutting down with two Pups (4.2 and 2.4.6) which on re-start and not starting Samba both closed quickly as normal.

Thanks for your excellent dancing lessons,

David S.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

Re: Testing the YASSM

#26 Post by rcrsn51 »

sheldonisaac wrote:Not sure this is version 1.3?
I really should have numbered these better. The new versions have an Options field and the old ones have Workgroup. So your Samba share selector example above is an old version.

Can you confirm that your samba-login test was with a new version? It sounds like the key is to use upper case server and share names.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#27 Post by rcrsn51 »

davids45 wrote:Is the package you've offered in this thread different to those Samba-TNG pets in a way you could outline?
The Samba-TNG thread has the samba-tng-rcrsn-client-1.4.pet, which also contains the samba-login and samba-shares programs. Those versions were designed primarily to access the Samba-TNG server.

The versions here are a bit more general so they can work in situations like sheldon's Win98 filesharing machine. If you have a client machine with samba-tng-rcrsn-client-1.4.pet installed, you can install this samba-share-mount-1.3.pet over top of it.
Re the Samba-TNG, I think when I've tried it as a server on my main desktop, when I shut down that Pup, it takes many seconds longer to close - is there be something I should be doing to get the normal quick Puppy close? I found this prolonged shutting down with two Pups (4.2 and 2.4.6) which on re-start and not starting Samba both closed quickly as normal.

I have seen slow shutdowns on client machines when I didn't first unmount a share. If the problem is on the server machine, just run samba-stop before quitting.
Last edited by rcrsn51 on Mon 20 Dec 2010, 00:07, edited 1 time in total.

sheldonisaac
Posts: 902
Joined: Mon 22 Jun 2009, 01:36
Location: Philadelphia, PA

Re: Testing the YASSM

#28 Post by sheldonisaac »

rcrsn51 wrote:
sheldonisaac wrote:Not sure this is version 1.3?
I really should have numbered these better. The new versions have an Options field and the old ones have Workgroup. So your Samba share selector example above is an old version.

Can you confirm that your samba-login test was with a new version? It sounds like the key is to use upper case server and share names.
I'm pretty sure the tests were with ver 1.3, but will check again.

Sorry, I realized after I sent the above that I'd used a .dat modified from the one I'd used with ver 1.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

Re: Testing the YASSM

#29 Post by rcrsn51 »

sheldonisaac wrote:I'm pretty sure the tests were with ver 1.3, but will check again.
It sounds like v1.3 is good, except that the share and server names must be in upper case. (A Win XP server doesn't care.)

If you can confirm this, I'll make another version that automatically converts them to caps.

Version 1.3 now works in Puppy 2.14X on my system with an XP share. Perhaps you can test this sometime with your Win98 share.

sheldonisaac
Posts: 902
Joined: Mon 22 Jun 2009, 01:36
Location: Philadelphia, PA

Re: Testing the YASSM

#30 Post by sheldonisaac »

rcrsn51 wrote:
sheldonisaac wrote:I'm pretty sure the tests were with ver 1.3, but will check again.
It sounds like v1.3 is good, except that the share and server names must be in upper case. (A Win XP server doesn't care.)

If you can confirm this, I'll make another version that automatically converts them to caps.
I used the Puppy Package Manager to uninstall all the versions.
Then installed 1.3
And pasted into the .dat the two lines for my Win98 shares.

Code: Select all

# more  /usr/local/samba/client/samba-shares.dat
#1# Don't change the first nine lines of this file!
#2# The data starts on Line 10.
#3# Each line of data describes a network share.
#4# There are six fields separated by commas. See the sample data below.
#5# The fields are: description, username, password, share, server, options
#6# If the share does not require a login, leave the username and password fields blank.
#7# The options field is optional. Multiple options MUST be separated by semicolons.
#8# The last line of the file MUST be EOF.
#9#
BCP,guest,xxx,H-BCP,SHELDON,dom=workgroup
Sources,guest,xxx,SOURCES,SHELDON,dom=WORKGROUP
Meghan's WinXP Share,,,share,acer
Music Collection,public,public,music,pupserver,iocharset=utf8;dom=MYGROUP
EOF
# 
I see that "workgroup" is in lower as well as upper case.
It works, both for the Samba share login and for the Samba share selector.
Version 1.3 now works in Puppy 2.14X on my system with an XP share. Perhaps you can test this sometime with your Win98 share.
I may be able to.
Thanks again.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#31 Post by rcrsn51 »

@sheldonisaac: And thank you for all your testing. Yours is one of the worst-case scenarios, so I am happy that we have resolved it.

I think that I will leave v1.3 alone for now. I will put a note in the how-to warning Win9X users that the share and server names are case-sensitive.

Bill

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#32 Post by rcrsn51 »

YASSM v1.5 is now available above. It has a new feature for hiding passwords in the samba-select share database.

There may be rare situations where samba-login cannot locate a share by its name. But the share should still be mountable using the option ip=aaa.bbb.ccc.ddd.

I am still looking for people who can test YASSM with Vista or Win7 shares.

Thanks.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

samba-login with Windows Xp/7 public

#33 Post by shinobar »

Tested samba-login of YASSM-1.5.pet.
  • Windows 7, Users
  • Windows Xp, SharedDocs
Both set up open for public, everyone required no password.
Both successfully mounted without username, pasword nor Options.
I only input Server name and Share name.
Test performed on Lupu-517.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

UTF-8 file names

#34 Post by shinobar »

shinobar wrote:Tested samba-login of YASSM-1.5.pet.
  • Windows 7, Users
  • Windows Xp, SharedDocs
Both set up open for public, everyone required no password.
Both successfully mounted without username, pasword nor Options.
I only input Server name and Share name.
Test performed on Lupu-517.
Tested a textfile with Japanese file name on Windows Xp.
It is shown in the Rox-Filer after mounting with samba-login of YASSM-1.5.pet.
But it cannot copy to the local disk, 'ERROR: No such file or directory'. :(
This does not occur with pnethood.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

Re: UTF-8 file names

#35 Post by rcrsn51 »

shinobar wrote:Tested a textfile with Japanese file name on Windows Xp.
It is shown in the Rox-Filer after mounting with samba-login of YASSM-1.5.pet.
But it cannot copy to the local disk, 'ERROR: No such file or directory'. :(
This does not occur with pnethood.
Did you include the option iocharset=utf8?

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: UTF-8 file names

#36 Post by shinobar »

rcrsn51 wrote:
shinobar wrote:Tested a textfile with Japanese file name on Windows Xp.
It is shown in the Rox-Filer after mounting with samba-login of YASSM-1.5.pet.
But it cannot copy to the local disk, 'ERROR: No such file or directory'. :(
This does not occur with pnethood.
Did you include the option iocharset=utf8?
Tried the option iocharset=utf8, but seems ignored.
I am now on LupQ-511 + lang_pack_cjk, so pnethood mount shows japanese file names correctly(they are not windows now but samba on Vine linux box).
But the samba-login of YASSM-1.5.pet with or without iocharset=utf8 option, they are all showing '??' and cannot access.

EDIT: It was my fault. The ROX-Filer needed 'refresh'.
No problem found with iocharset=utf8 option :D
Last edited by shinobar on Tue 28 Dec 2010, 13:43, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#37 Post by jamesbond »

shinobar, is your LOCALE set to enable utf8? I found out that even with iocharset=utf8, if your locale not set to utf8, then winxp shared folders with unicode filenames will not properly. In my case, I had to ensure that my LANG setting is en_AU.utf8 instead of just en_AU.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

UTF-8 file names

#38 Post by shinobar »

jamesbond wrote:shinobar, is your LOCALE set to enable utf8?
Thanks. Yes, i am shure with utf8( really, UTF-8 ).
LupQ-511 + lang_pack_cjk, so pnethood mount shows japanese file names correctly.

BTW, Samba on my remote Linux box and Windows share can be different.
I may need another test with Windows...
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

UTF-8 filename OK

#39 Post by shinobar »

Sorry, the ROX-Filer needed to refresh.
No problem with Japanese file names if i add iocharset=utf8 option. :D
Local: LupQ-511 + lang_pack_cjk
Remote: Both Samba on Linux, Windows Xp

Hope iocharset=utf8 option as the default.
Pnethood has iocharset=utf8 option for years and seems harmless.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

Re: UTF-8 filename OK

#40 Post by rcrsn51 »

shinobar wrote:No problem with Japanese file names if i add iocharset=utf8 option.
Excellent. Thank you for testing this.

Post Reply