puppy shares WinXP files but not win98's nor the reverse

Message

canbyte · #16 Post by **canbyte** » Thu 05 Feb 2009, 01:30

Thanks for that little tip Whodo, i'll have to try to remember that - makes things a lot easier.

Here is the output, hopefully someone will see what's going wrong.

# smbclient -L win98
params.c:Parameter() - Ignoring badly formed line in configuration file: SMBCLIENT //win98/c -U -W
params.c:Parameter() - Ignoring badly formed line in configuration file: smbmount //win98/C /mnt/network
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 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
Connection to win98 failed (Error NT_STATUS_BAD_NETWORK_NAME)

Smb.conf is listed above/earlier post.

That little Geany app is nice to use.

rcrsn51 · #17 Post by **rcrsn51** » Thu 05 Feb 2009, 02:10

Code: Select all

# SMBCLIENT //hostname/dirname -U userid%password
SMBCLIENT //win98/c -U
smbmount //win98/C /mnt/network -o

These are lines that you would run from a console. They should NOT be in the smb.conf file.

You can ignore all the init_iconv errors.

If you are unsure of the Win98's exact machine name, try this:

Code: Select all

smbclient -NL aaa.bbb.c.d   (its IP address)

Read here for info on how to change the name of a Win98 computer.

canbyte · #18 Post by **canbyte** » Sat 07 Feb 2009, 04:18

hi rcrsn51,

here is the output of your command for the box named Win98 with the ipaddress of 192.168.0.3

session request to 192.168.0.3 failed (Called name not present)
session request to 192 failed (Called name not present)
session request to *SMBSERVER failed (Called name not present)

BTW, for some reason these responses are included in the output
params.c:Parameter() - Ignoring badly formed line in configuration file: SMBCLIENT //win98/c -U -W
params.c:Parameter() - Ignoring badly formed line in configuration file: smbmount //win98/C /mnt/network

The problem with these lines is that i had deleted smb.conf and replaced it with the original that Whodo sent me in the previous post. Even after a reboot, these commands are still somewhere in the system. Puppy is being stubborn!! I wonder where they came from - i hope not the backup file i made with those lines included. Will lines from a backup file execute (does not have a .conf extension)?

Anyway, just for reference, here is the output of that command for another box that puppy is happy to get files from (one way only) - an xp named Sarah ie # smbclient -NL 192.168.0.2

Domain=[SARAH] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment
--------- ---- -------
Assignments Disk
IPC$ IPC Remote IPC
SharedDocs Disk
print$ Disk Printer Drivers
ADMIN$ Disk Remote Admin
C$ Disk Default share
session request to 192.168.0.2 failed (Called name not present)
session request to 192 failed (Called name not present)
Domain=[SARAH] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
Server Comment
--------- -------
Workgroup Master
--------- -------

As far as i can tell, the sharing is set up by an app called pnethood Samba in the main menu of puppy 412. So where is that info stored - does not appear in smb.conf which seems to have only a few real instructions. Confusing. I'm way over my head !!!

Hope someone can make something out of all this.

Thanks.

rcrsn51 · #19 Post by **rcrsn51** » Sat 07 Feb 2009, 12:51

Try this command:

Code: Select all

nbtscan 192.168.0.0-9 -t 20000

Wait 20 seconds for the reply. Does that identify the Win98 box and give you its correct name? Is it "Win98"? Then try:

Code: Select all

smbclient -NL Win98

Does that identify the Share folder?

This item may be helpful.

Regarding the error messages: Use Pfind to locate your smb.conf file. In my Puppy, it's in /etc/opt/samba. Then check again for the bad lines.

canbyte · #20 Post by **canbyte** » Sat 07 Feb 2009, 17:30

Hi rcrsn51, good to hear from you again. Yes, Win98 is the box name

Here is the output from those commands, minus the 'init' junk.
# nbtscan 192.168.0.0-9 -t 20000
Doing NBT name scan for addresses from 192.168.0.0-9

IP address NetBIOS Name Server User MAC address
------------------------------------------------------------------------------
192.168.0.0 Sendto failed: Permission denied

# smbclient -NL Win98
params.c:Parameter() - Ignoring badly formed line in configuration file: SMBCLIENT //win98/c -U -W
params.c:Parameter() - Ignoring badly formed line in configuration file: smbmount //win98/C /mnt/network
<snip junk>
Connection to Win98 failed (Error NT_STATUS_BAD_NETWORK_NAME)

Sigh!

I just noticed your location, I'm in Hamilton, maybe its easier for me to bring puppy for a visit sometime???

Cheers

PS Just noticed these threads, tried their suggestions too, no luck.
http://www.murga-linux.com/puppy/viewto ... 06&t=38381
http://www.murga-linux.com/puppy/viewto ... 06&t=38415

output:

# pnethood 192.168.0.3
du: cannot access `/tmp/pnethood/log': No such file or directory
/usr/local/apps/pnethood/pnethood: line 18: [: too many arguments
smb mounting enabled
cifs mounting enabled
/usr/local/apps/pnethood/pnethood: line 1: 3196 Terminated gtkdialog3 --program=MSG_SCANNING_MACHINE --center

trying to get seamonkey to open that address also didn't work. Hmmmmp!

[/url]

HairyWill · #21 Post by **HairyWill** » Sat 07 Feb 2009, 20:12

rcrsn51 wrote:Try this command:
Code: Select all
nbtscan 192.168.0.0-9 -t 20000

should be

Code: Select all

nbtscan 192.168.0.0/16 -t 20000

be aware that you need to wait 20 seconds for it to complete

rcrsn51 · #22 Post by **rcrsn51** » Sun 08 Feb 2009, 00:20

Going back to the first page of this thread, are you able to successfully ping the Win98 machine?

Code: Select all

ping 192.168.0.3

eastler_dart · #23 Post by **eastler_dart** » Wed 11 Feb 2009, 20:23

Hello all,

first, sorry for my poor english.

There is another aspect, why XP and W98 go different ways - the password-transmitting.
There are differences in encryption of the passwords.

W98SE is able, to send encrypted passwords, but this didn't work really (my Tests).
XP with no change sends encrypted passwords, somewhere in services/security/local there is the possibility, "enable plain Text Passwords".

After a lot of tests, my result is:
My Old Samba-Server (Version is something like 1.9) acts by default with plain passwords.

The W98-Clients got a Registry-Hack with EnablePlainTextPassword=yes
and all are working fine with the Server.

The new Clients, with XP, I had enabled "Plain Text Passwords" in the services. From then on, they also act with the Old Server.
But in the logs of the XP-Clients on the Server, there are sometimes some lines, that XP wants something, which Samba 1.9 does not know.

So, I tried to build a second, newer Server=newer Samba.
With: "encrypt passwords = no" in the smb.conf,
it is possible, to act with plain passwords.
With additionaly "netbios name = Server2",
W98SE find this second, newer Server and act with him.
But the XPprof Clients, do not find them.

With "encrypt passwords = yes"
And re-disable "Plain passwords" on the XP-Clients, they are happy and act with the new Samba, but, the W98-Clients do not find something.

Thats why, I now try something like this:
Build a second server, share alle Diskspace via NFS to the first server, and this first server send these shares via (old) Samba on the Lan.
First tests are successful.
The End-Result should be, that in addition, the Old Server also shares all via NFS to the new one, so that the new one is also able, to give all stored files via smb to clients.
And in this situation, the XP-Clients could work with the new one (without errors in the logs), the W98-Clients keep working with the old Server.

And when the last W98-Client is death, the old server could go away.

Hope, you can understand, what I'm writing,
with newer Sambas seems there is no way,
to get W98 AND XP clients on a single Lan.
Or, I don't know all, and there are other ways, too.

hope it helps,

Eastler

canbyte · #24 Post by **canbyte** » Wed 11 Feb 2009, 23:23

Hi eastler_dart, hairyWill, rcrsn51,
I'll post the data from rxvt's response below but first eastler, welcome aboard! If i understand you correctly, you may have found a solution to a problem which is plaguing many folks around various fora - and that is to get hold of an old samba and throw out the new samba! The old samba shares with both Win98 and XP once all passwords are plain. Not being very familiar with messing with these things, i may need some coaching for such a changeover but firstly, ....

does anybody have an old samba (1.9) that can be inserted into puppy 412???

Or is such a thing even possible?

If it is, then wouldn't you be better off with the old one ie why are you pursuing trying to get the new samba to work?

I don't suppose that a simple solution - having no username or password at all - would be a solution?? ie- nothing to encrypt?

I shouldn't forget to mention that neither XP nor Win98 can share with puppy other than being able to ping the machine 192.168.0.5, although this is of less concern as i would like to make Puppy the 'master'! I hope 2 yr old Dakota, (our real puppy), won't get jealous!

A few times i've seen in this forum, folks suggesting that older machines/ systems should use an older puppy version. Your approach lends weight to that notion. If so, i hope puppy developers can somehow keep the old versions alive/supported/ updated as something older computers can/should be using (or make changing samba version easier through package manager.)

--------------------
Here's the data for any clues it may provide.

# nbtscan 192.168.0.0-9 -t 20000
Doing NBT name scan for addresses from 192.168.0.0-9
IP address NetBIOS Name Server User MAC address
------------------------------------------------------------------------------
192.168.0.0 Sendto failed: Permission denied
192.168.0.3 WIN98 <server> WIN98 00-14-2a-ad-70-40
192.168.0.2 SARAH <server> <unknown> 00-01-02-69-11-68

# smbclient -NL WIN98
params.c:Parameter() - Ignoring badly formed line in configuration file: SMBCLIENT //win98/c -U -W
params.c:Parameter() - Ignoring badly formed line in configuration file: smbmount //win98/C /mnt/network
init_iconv: Conversion from UTF-16LE to CP850 not supported
init_iconv: Attempting to replace with conversion from UTF-16BE to ASCII
Connection to WIN98 failed (Error NT_STATUS_BAD_NETWORK_NAME)

# nbtscan 192.168.0.0/16 -t 20000
Doing NBT name scan for addresses from 192.168.0.0/16
IP address NetBIOS Name Server User MAC address
------------------------------------------------------------------------------
192.168.0.0 Sendto failed: Permission denied
192.168.0.2 SARAH <server> <unknown> 00-01-02-69-11-68
192.168.0.3 WIN98 <server> WIN98 00-14-2a-ad-70-40
192.168.0.255 Sendto failed: Permission denied

# ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3): 56 data bytes
64 bytes from 192.168.0.3: seq=0 ttl=128 time=4.397 ms
64 bytes from 192.168.0.3: seq=1 ttl=128 time=0.377 ms
^Z
[2]+ Stopped ping 192.168.0.3

Thanks for all your suggestions.

eastler_dart · #25 Post by **eastler_dart** » Mon 16 Feb 2009, 21:16

hello all, hello canbyte,

i try to answer some of your questions:

1) Old Samba: I had a look of my old Install-CDs of Suse 6.00,
the packages are called:
samba-2.0.0-0.i386.rpm Date 16 jan 1999 Size: 2475 K
samba-2.0.0-0.src.rpm Date 16 jan 1999 Size: 2075 K
it seems, that should work. If the i386 pre-compiled rpm dosn't do, what we want, there are also the sources

.
But I'm not familar with compiling something in Linux !
That should not be a problem, here are enough specialists.

Is here anyone, who can explain me, what happens to me, if I put this both files on my www.space for downloading?
Got I hanged up?

2) Why I try to use the new Samba:
The old server writes log-files with infos of every contact from Clients to the server. In this log-files I can read, that the XP-Clients are asking Samba something, and Samba 2 doesn't know, what they want.
Additionally, the XP-Clients got sometimes wired, do mystical things (greetings from Bill?).
I think now, this could be, because Samba2 dosn't answer all questions. That's why, I want to test with newer Samba, if the XP-Machines then don't get a little wired.
But, all in all, I can start Word, Excel, Access and co. on the XP-Clients, load files from the Samba2-Server, edit them, and save them back to the Server. I am able, to play on XP-Clients music, stored on the old server, or take a look on pictures, stored on the server.
No file errors ore something else, only the Logs, that some questions from the XP-Clients coultn't be understand.
So its only my Sherlock Holmes-thinking, to test a newer Samba, what is about the unrecognized Questions, allthough all goes well.

3) usernames - groupnames.
you write something like "without usernames".
If I understand it right, you think, there are no posibilities of creating additional usernames or groupnames in Puppy? There are !
In a terminal there are commands, called adduser and addgroup !. And you need this both, if you want to give Samba-Shares only to group-members or to an specially user.
(Shure, thats not enough, to login on the Servers Keyboard with such an additional username, but that is not what we want or need)

4) ...as i would like to make Puppy the 'master'!
My Server isn't a Master of anything! And, if I remember right, Samba2 as a Master(Local or/and Domain) dosn't understand a W98-Machine!

your Datas in Quotes didn't say enough at the moment, but first, we shoulb be able, to get Samba2 to run on Puppy. After that (successful), it make sense, of checking all of the other things.

OK, first I have to know, if I got hanged up

then I can post the files
then someone here can try, to build an sfs-file with Samba2
to add this old samba to Puppy

see you later

Eastler

Aitch · #26 Post by **Aitch** » Mon 16 Feb 2009, 22:43

canbyte

I hope its not an obvious oversight, like not having enabled windoze file sharing as per:-

http://www.wellesley.edu/Computing/File ... n98me.html

As I recall any settings changes on a Win98 box need a reboot, too

sharing always was a bit tricky, IIRC

I found using Slampp live CD works everytime, including W98, so maybe some tips there?

http://slampp.abangadek.com/wiki/wikka. ... a=HomePage

Aitch

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

puppy shares WinXP files but not win98's nor the reverse

Old Samba anyone?