Opened 10 years ago
Closed 10 years ago
#243 closed defect (invalid)
connecting samba client to IBM requester
| Reported by: | KO Myung-Hun | Owned by: | |
|---|---|---|---|
| Priority: | Feedback Pending | Milestone: | Netdrive plugin 2.2.x |
| Component: | Samba Client Plugin | Version: | Client 2.1.x |
| Keywords: | Cc: |
Description
Hi/2.
I'm trying to connect samba client to IBM requester. But samba client cannot connect due to error code 54.
I'm using NDP 2.1.5.
Attachments (2)
Change History (4)
comment:1 by , 10 years ago
| Milestone: | → Netdrive plugin 2.2.x |
|---|---|
| Priority: | minor → Feedback Pending |
| Version: | → Client 2.1.x |
by , 10 years ago
| Attachment: | log.ndpsmb added |
|---|
by , 10 years ago
comment:2 by , 10 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Without having tried to do this recently (it worked several years ago doing the things described below), I doubt that it really does not work with a Samba 3.0.x or Samba 3.3.x based clients today, however it will definitely not work out of the box. The client MUST use a manuelly customized smb.conf in order to get that to work.
Several settings come to my mind where Samba uses defaults incompatible with LAN Requester:
- Password strength (IBM: only upper case, max 8 chars; Samba/Windows: Mixed case and possibly longer)
- Password transmission (IBM: plain; Samba/Windows: Encrypted)
- Browsing must me set to broadcast only.
- LM10 protocol must be negotiated.
All these may be configured properly for IBM LAN Requester in the Samba Client's smb.conf at least up to Samba 3.3 (some of the password related options were dropped around 3.5), however note that a Samba Client configured to behave properly for IBM LAN Requester will fail to connect to Windows boxes as these settings will be considered as security infringement by any Windows Server or even Samba itself.
Please add a client debuglog. How this is done is written in the help file.