My Digitus NAS DN-7023 works with OPL via SMB protocol.
But with SMS, not.
Even after following SMS documentation, tutorials/threads/discussions here and on other forums spread over Internet, I still wasn't able to make it work.
I tried many approachs, for instance:
- NAS connected to my Console via crossover ethernet cables, NAS connected to my Router and this last one with my Console via normal ethernet cables.
- I tried many logins (capitalised/not capitalised: GUEST, Guest, ADMIN, admin) with and without passwords.
- Starting network support automatically and manually (and also restarting SMS after applying changes).
(of course I entered on NAS setup, PS2 IP settings, and so far)...
Despite of reading my SMS.smb file, I can't notice any Network icon in upper SMS display area.
Contrary to this, I always got the same SMS login error message:
Login error (-16384) (press 'CROSS' to continue)...
I inspected the public SMS source code, using that link from the Eugene Plotnikov's home page (http://members.casema.nl/eugene_plotnikov/):
"SMS source code for version 2.1 (Rev.2) as WebSVN is available HERE"
repname=ps2ware&path=/trunk/SMS/&rev=0&sc=0]WebSVN - ps2ware - Rev 598 - /trunk/SMS/[/url]) in order to figure out from where that error code (-16384) arises...
Login error (%d) (press \"cross\" to continue)...
.. but the related SMSMB.c code isn't understandeable by me.
static unsigned char s_pLoginError  __attribute__( ( aligned( 1 ), section( ".data" ) ) ) = "Login error (%d) (press \"cross\" to continue)...";
Moreover, I haven't find the explanation for this (-16384) - apparently SMB error code anywhere on Web.
I also found this... Maybe someone can give me further guidance in order to find the root cause of my problem:
Any kind of help would be appreciated! ;-)
- added SMB/CIFS network protocol. Tested only on Windows XP Pro (SP2)
and Linux/Debian with recent Samba distribution. Only one server
connection is supported (though driver allows two). Network transfer
speed is comparable to host: protocol (if the server supports raw data
transfer (both XP and Linux do), otherwise it will be ~30% slower).
To use this feature perform following steps:
- create SMS.smb text file in a text editor. This file must contain
exactly 5 lines in the following order:
- IP address of the SMB server (ex. 192.168.0.3);
- name of the SMB server (ex. MyServer);
- name of the PS2 (arbitrary) (ex. MyPS2);
Note: I'm not 100% sure about it, maybe this name
must be listed in 'hosts'/'lmhosts' file;
- user name used for authentication (ex. eugene);
- user password used for authentication (ex. myPassword);
Note 1: blank password is not allowed;
Note 2: - "for individuals that think that harm is occurring, or
is going to occur, to him or her"
- "for individuals that think the persecutor has the
intention to cause harm"
PASSWORD IS ONE WAY ENCRYPTED BEFORE ITS TRANSMISSION TO
THE SMB SERVER ONLY IF THE SERVER SUPPORTS SUCH A FEATURE
(at least Windows XP Pro(SP2) and Samba on Libux/Debian do
support this (please, don't consider this as advertisement));
- make sure that IP address is correct;
- make sure that SMB server name is correct;
- make sure that SMB server allows connections (i.e. review firewall/router
- make sure that user whose credentials supplied in SMS.smb has appropriate
access rights to connect to the SMB server;
- copy this file to mc0:/SMS folder;
- start SMS; If 'autostart network' option is active, then
deactivate it, save settings and restart SMS;
- goto SMS menu -> Device settings;
- select SMB/CIFS network protocol;
- start network support;
New device icon shall appear as soon as connection to the server is
established (or error message if there's a problem with authentication
etc.). Normally this should occur in 0-10 seconds. There's no need to
start SMB server before SMS, as connection is made automatically (SMS tries
to establish connection to the server approximately each 5-10 seconds).
It's possible to shut down SMB server while SMS browser is active. In this
case SMB device icon will disappear and connection attempts are resumed again.
This can however cause hang, so use this functionaliy at your own risk;
In case of problems use 'ethereal'/'wireshark' software to trace activity on
the server's TCP port 139. New SMB device is browseable starting from share
level (note that shares with '$' suffix in their name (like 'C$', 'ADMIN$'
etc.) are explicitly disabled, so they won't ever appear in the file browser);