[Samba] OS/2 Warp 4 Access Issues - Samba

This is a discussion on [Samba] OS/2 Warp 4 Access Issues - Samba ; Sometime not too long ago, I installed a new security release of samba on my debian box. Shortly after, I realized that my OS/2 Warp 4 box was no longer able to access the shares on my debian box. The ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: [Samba] OS/2 Warp 4 Access Issues

  1. [Samba] OS/2 Warp 4 Access Issues

    Sometime not too long ago, I installed a new security release of samba on my
    debian box. Shortly after, I realized that my OS/2 Warp 4 box was no longer
    able to access the shares on my debian box. The OS/2 system is still able to
    access shares on other (Win9x) machines.

    I asked around about this issue on an OS/2 list. Although no one there was
    sure what might have caused it to quit working, they suggested that there
    was possibly a security issue with one of the older protocols which allowed
    OS/2 to access the shares. They suggested that OS/2 uses drivers not updated
    since the NT 3.x days, and that one might now be turned off by default by Samba,
    and that there might be a setting I could re-enable that would allow OS/2 to
    regain access to the shares.

    Is this a known "issue"? If so, does anyone know what the work-around is, if
    any?

    Thanks!

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  2. [Samba] Re: OS/2 Warp 4 Access Issues

    Michael Powell wrote:
    > Sometime not too long ago, I installed a new security release of samba on my
    > debian box.


    What version of Samba were you running? What version did you upgrade to?

    I would be willing to test against Sarge and Simo's packages of 3.0.24... What sort of "access issues" were you seeing?

    --
    Michael Lueck
    Lueck Data Systems
    http://www.lueckdatasystems.com/

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  3. Re: [Samba] OS/2 Warp 4 Access Issues

    On 2007/06/30 10:29 (GMT-0400) Michael Powell apparently typed:

    > Sometime not too long ago, I installed a new security release of samba on my
    > debian box. Shortly after, I realized that my OS/2 Warp 4 box was no longer
    > able to access the shares on my debian box. The OS/2 system is still able to
    > access shares on other (Win9x) machines.


    > I asked around about this issue on an OS/2 list. Although no one there was
    > sure what might have caused it to quit working, they suggested that there
    > was possibly a security issue with one of the older protocols which allowed
    > OS/2 to access the shares. They suggested that OS/2 uses drivers not updated
    > since the NT 3.x days, and that one might now be turned off by default by Samba,
    > and that there might be a setting I could re-enable that would allow OS/2 to
    > regain access to the shares.


    > Is this a known "issue"? If so, does anyone know what the work-around is, if
    > any?


    Problems between OS/2 and Samba have been the rule rather than the
    exception since Samba 3 replaced Samba 2. Most issues are resolved in
    the latest versions, but to really be able to help you'll probably need
    to provide more information on your versions, kernel, Debian and Samba,
    plus Samba configuration.

    My SUSE box is running 3.0.26pre1 compiled from SVN plus a recompiled
    kernel that includes SMBFS, as CIFS remains broken for use with OS/2. I
    stay out of trouble by mounting all OS/2 shares ro, and using only OS/2
    to move or copy files from Samba shares to OS/2.
    --
    "Respect everyone." I Peter 2:17 NIV

    Team OS/2 ** Reg. Linux User #211409

    Felix Miata *** http://mrmazda.no-ip.com/
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  4. Re: [Samba] OS/2 Warp 4 Access Issues

    OK, here are the versions:

    OS/2 Warp 4.50
    Debian Etch
    Samba 3.0.24-6etch4
    linux kernel 2.6.18

    I actually started having problems before upgrading to etch. Then, I was on a
    2.4 kernel, and had upgraded to what was then the latest security fix for
    samba for the debian "stable" version previous to etch. I was hoping that
    upgrading to etch might fix the problem, but it did not. FWIW, I did a
    "clean" upgrade to etch, using the netinstall CD, so all of the previous
    binaries and config files were over-written (nothing left behind to cause
    problems).

    As for the problem... on the OS/2 box, the shares on the debian box are
    displayed (just as the shares on the Win9x box are), but when I "click" on
    any of the debian shares, OS/2 reports that "No objects were found that
    match the specified find criteria." So, none of the files that reside
    in the shared folders are displayed. It is as if the shares have no files
    in them (but they do!).

    OS/2 does appear to access the "PDF Printer" share OK, and acts as
    though it is printing to it, but I have no idea where the PDF files that
    it is "printing" are being saved. ;-) It cannot access any of the
    disk shares.

    Here is the smb.conf config file (with certain bits replaced with 'X'):

    [global]
    netbios name = XXXXXX
    server string = debian
    workgroup = XXXXXX
    hosts allow = 127. 192.168.X.
    #printcap name = /etc/printcap
    printcap name = cups
    load printers = yes
    printing = cups
    cups options = raw
    guest account = smbguest
    log file = /var/log/samba/samba.log
    max log size = 1000
    security = user
    username level = 8
    password level = 8
    username map = /etc/samba/smbusers
    add user script = /usr/sbin/useradd -d /dev/null -g sambamachines -c 'Samba Machine Account' -s /dev/null -M '%u'
    smb passwd file = /etc/samba/smbpasswd
    encrypt passwords = yes
    unix password sync = no
    passwd program = /usr/bin/passwd '%u'
    passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*success fully*\n
    null passwords = no
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    interfaces = 127.0.0.1/8 192.168.X.X
    remote browse sync = 192.168.X.255
    remote announce = 192.168.X.255
    local master = no
    os level = 33
    domain master = no
    preferred master = no
    time server = no
    domain logons = no
    logon drive = m:
    logon home = \\%L\homes\%u
    logon path = \\%L\profiles\%u
    logon script = %G.bat
    name resolve order = wins lmhosts bcast
    wins support = no
    msdfs root = yes

    wins proxy = no
    dns proxy = no
    preserve case = no
    winbind use default domain = yes
    idmap uid = 16777216-33554431
    idmap gid = 16777216-33554431
    template shell = /dev/null

    [homes]
    comment = Home Directories
    path = /home
    read only = no
    available = yes
    browseable = yes
    writable = yes
    guest ok = no
    public = no
    printable = no
    share modes = no
    locking = no

    [netlogon]
    comment = Network Logon Service
    path = /home/netlogon
    read only = no
    available = yes
    browseable = yes
    writable = no
    guest ok = no
    public = no
    printable = no
    share modes = no
    locking = no

    Thanks for your assistance!

    On Sat, 30 Jun 2007 17:33:51 -0400
    Felix Miata wrote:

    > Problems between OS/2 and Samba have been the rule rather than the
    > exception since Samba 3 replaced Samba 2. Most issues are resolved in
    > the latest versions, but to really be able to help you'll probably need
    > to provide more information on your versions, kernel, Debian and Samba,
    > plus Samba configuration.
    >
    > My SUSE box is running 3.0.26pre1 compiled from SVN plus a recompiled
    > kernel that includes SMBFS, as CIFS remains broken for use with OS/2. I
    > stay out of trouble by mounting all OS/2 shares ro, and using only OS/2
    > to move or copy files from Samba shares to OS/2.
    > --
    > "Respect everyone." I Peter 2:17 NIV
    >
    > Team OS/2 ** Reg. Linux User #211409
    >
    > Felix Miata *** http://mrmazda.no-ip.com/
    > --
    > To unsubscribe from this list go to the following URL and read the
    > instructions: https://lists.samba.org/mailman/listinfo/samba



    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  5. Re: [Samba] OS/2 Warp 4 Access Issues

    Am Donnerstag, 5. Juli 2007 22:38 schrieb Michael Powell:
    > OK, here are the versions:
    >
    > OS/2 Warp 4.50
    > Debian Etch
    > Samba 3.0.24-6etch4
    > linux kernel 2.6.18
    >
    > I actually started having problems before upgrading to etch. Then, I was on a
    > 2.4 kernel, and had upgraded to what was then the latest security fix for
    > samba for the debian "stable" version previous to etch. I was hoping that
    > upgrading to etch might fix the problem, but it did not. FWIW, I did a
    > "clean" upgrade to etch, using the netinstall CD, so all of the previous
    > binaries and config files were over-written (nothing left behind to cause
    > problems).
    >
    > As for the problem... on the OS/2 box, the shares on the debian box are
    > displayed (just as the shares on the Win9x box are), but when I "click" on
    > any of the debian shares, OS/2 reports that "No objects were found that
    > match the specified find criteria." So, none of the files that reside
    > in the shared folders are displayed. It is as if the shares have no files
    > in them (but they do!).
    >
    > OS/2 does appear to access the "PDF Printer" share OK, and acts as
    > though it is printing to it, but I have no idea where the PDF files that
    > it is "printing" are being saved. ;-) It cannot access any of the
    > disk shares.
    >
    > Here is the smb.conf config file (with certain bits replaced with 'X'):
    >
    > [global]
    > netbios name = XXXXXX
    > server string = debian
    > workgroup = XXXXXX
    > hosts allow = 127. 192.168.X.
    > #printcap name = /etc/printcap
    > printcap name = cups
    > load printers = yes
    > printing = cups
    > cups options = raw
    > guest account = smbguest
    > log file = /var/log/samba/samba.log
    > max log size = 1000
    > security = user
    > username level = 8
    > password level = 8
    > username map = /etc/samba/smbusers
    > add user script = /usr/sbin/useradd -d /dev/null -g sambamachines -c 'Samba Machine Account' -s /dev/null -M '%u'
    > smb passwd file = /etc/samba/smbpasswd
    > encrypt passwords = yes
    > unix password sync = no
    > passwd program = /usr/bin/passwd '%u'
    > passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*success fully*\n
    > null passwords = no
    > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    > interfaces = 127.0.0.1/8 192.168.X.X
    > remote browse sync = 192.168.X.255
    > remote announce = 192.168.X.255
    > local master = no
    > os level = 33
    > domain master = no
    > preferred master = no
    > time server = no
    > domain logons = no
    > logon drive = m:
    > logon home = \\%L\homes\%u
    > logon path = \\%L\profiles\%u
    > logon script = %G.bat
    > name resolve order = wins lmhosts bcast
    > wins support = no
    > msdfs root = yes
    >
    > wins proxy = no
    > dns proxy = no
    > preserve case = no
    > winbind use default domain = yes
    > idmap uid = 16777216-33554431
    > idmap gid = 16777216-33554431
    > template shell = /dev/null
    >
    > [homes]
    > comment = Home Directories
    > path = /home
    > read only = no
    > available = yes
    > browseable = yes
    > writable = yes
    > guest ok = no
    > public = no
    > printable = no
    > share modes = no
    > locking = no
    >
    > [netlogon]
    > comment = Network Logon Service
    > path = /home/netlogon
    > read only = no
    > available = yes
    > browseable = yes
    > writable = no
    > guest ok = no
    > public = no
    > printable = no
    > share modes = no
    > locking = no
    >
    > Thanks for your assistance!
    >


    Hi Michael,

    add the following to the [global] section of smb.conf:

    ea support = yes

    Cheers, Guenter
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  6. Re: [Samba] OS/2 Warp 4 Access Issues

    Thanks! That did the trick!

    On Thu, 5 Jul 2007 23:42:36 +0200
    Guenter Kukkukk wrote:

    > Am Donnerstag, 5. Juli 2007 22:38 schrieb Michael Powell:
    > > [...snip...]
    > > As for the problem... on the OS/2 box, the shares on the debian box are
    > > displayed (just as the shares on the Win9x box are), but when I "click" on
    > > any of the debian shares, OS/2 reports that "No objects were found that
    > > match the specified find criteria." So, none of the files that reside
    > > in the shared folders are displayed. It is as if the shares have no files
    > > in them (but they do!).
    > > [...snip...]

    > Hi Michael,
    >
    > add the following to the [global] section of smb.conf:
    >
    > ea support = yes
    >
    > Cheers, Guenter
    > --
    > To unsubscribe from this list go to the following URL and read the
    > instructions: https://lists.samba.org/mailman/listinfo/samba


    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

+ Reply to Thread