Buffalo LS220DE NAS & SAMBA

[p***@gmail.com]

I've got a new Buffalo LS220DE network drive for backup, however, my ecs2.1 box seems to be unable to find it.
It is set to the same workgroup and has its IP and name in the HOSTS file
A nearby XP box can see and access it without problems
But it doesn't show up in EVFSGUI and neither is listed by netview of findsmb -X utilities

It is found by smbclient -L, though, and luckily I could mount it using Netdrive (which should use the same samba plugin as EVFSGUI), since, unlike EVFSGUI, it allows to enter the server name manually.

I did a complete unistall/install of Samba to be sure to have the last version.

the NAS sports UNIX and reports itself as Samba 3.6.19-60.osstech
In the settings, samba is reported as "SMB2 server, which I assumed would have been more os/2 friendly :-) but in fact has some changes in the messages sent during discovery, so I would guess that the problem is there.

I just wonder if anyone has similar problems, and if there is any difference between a remote drive mounted with Netdrive or EVFSGUI

thanks

Piersante

[Marcel Mueller]

Post by p***@gmail.com
I've got a new Buffalo LS220DE network drive for backup, however, my ecs2.1 box seems to be unable to find it.
It is set to the same workgroup and has its IP and name in the HOSTS file
A nearby XP box can see and access it without problems
But it doesn't show up in EVFSGUI and neither is listed by netview of findsmb -X utilities

Turn on the logging on the samba server. Log Level 8 or 10. Then restart
the samba server and have a look at the log files when eCS try to
examine the network. Usually there are helpful hints at which place the
communication breaks.
Don't forget to disable the logging afterwards as the files grow fast.

Post by p***@gmail.com
It is found by smbclient -L, though, and luckily I could mount it using Netdrive (which should use the same samba plugin as EVFSGUI), since, unlike EVFSGUI, it allows to enter the server name manually.

I don't know EVFSGUI, only IBM Peer and Netdrive. Maybe some kind of bug.

Post by p***@gmail.com
the NAS sports UNIX and reports itself as Samba 3.6.19-60.osstech

Not that new, but this should not be the problem.
Samba implementations of NAS boxes are often buggy with respect to not
that common clients. But mostly they are only misconfigured.

Post by p***@gmail.com
In the settings, samba is reported as "SMB2 server, which I assumed would have been more os/2 friendly :-)

More friendly? In contrast to what other options? SMB2 is a newer,
faster protocol level. Maybe not fully supported by Samba for OS/2.

Probably the NT1 protocol level is more reliable. But the protocol is
negotiated between client and server session start to the least common
denominator. So you should not downgrade the server to NT1. But you need
to set the /minimum/ protocol level (setting "min protocol") of the
server to at most NT1 (or LANMAN2 for IBM Peer clients). Otherwise the
server will only accept SMB2 connections.
If the client claims to support SMB2 (likely) but unreliable you should
set the "max protocol" of the Samba for OS/2 client to NT1. This will
downgrade only connections from this client.

Post by p***@gmail.com
but in fact has some changes in the messages sent during discovery, so I would guess that the problem is there.

Maybe. I don't know which changes are really done by this option.

Post by p***@gmail.com
I just wonder if anyone has similar problems, and if there is any difference between a remote drive mounted with Netdrive or EVFSGUI

Netdrive never worked reliable for me. It crashed from time to time when
running 24/7. Furthermore it did not correctly support extended
attributes required for the PMShell and OREXX. So I reverted to IBM Peer
for eCS clients. This requires LANMAN2 to be enabled on the server but
once configured it is solid as a rock for years. The only restriction is
no large file support (>2GB).
The other way around, when I need to connect from Linux to eCS (as
server) I ended up with the old NFS3 server (built in to OS/2 and eCS).
This was most reliable. It does not support EAs either, but Linux
clients normally don't care.


Marcel

[j***@nospam.com.au]

Post by p***@gmail.com
I've got a new Buffalo LS220DE network drive for backup

Can you share with us how you might restore to a new and blank hard drive.

[p***@gmail.com]

Post by j***@nospam.com.au

Post by p***@gmail.com
I've got a new Buffalo LS220DE network drive for backup

Can you share with us how you might restore to a new and blank hard drive.

I am using eBackUp (which is basically a GUI to rar32) http://www.wdsibyl.org/Downloads/sublevel/cid/21.
I never (yet) had the need to restore a full drive, but it would be a matter of unrar-ing back the archive, either with eBackUp or with rar32 itself. Of course the new drive should have been already formatted.

Note that eBackUp is unable to store open files, so you must take care to shutdown running programs such as apache if you want to store the current logs, and cannot backup a partition with the running SO. I boot from a different partition to backup the main boot partition.

I guess that backing up the full disk image with dfsee would be better for that.

Piersante