[SOLVED] OPL, SMS, SMB and NAS

[doctorxyz]

Hi guys,

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)...

EDIT
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...

SMS.lng_EN

(...)
Login error (%d) (press \"cross\" to continue)...
(...)

SMS_Locale.c

(...)
static unsigned char s_pLoginError     [] __attribute__(   (  aligned( 1 ), section( ".data" )  )   ) = "Login error (%d) (press \"cross\" to continue)...";
(...)

.. but the related SMSMB.c code isn't understandeable by me.

Moreover, I haven't find the explanation for this (-16384) - apparently SMB error code anywhere on Web.

EDIT2
I also found this... Maybe someone can give me further guidance in order to find the root cause of my problem:

Update (24-DEC-2006)
--------------------
- 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
    settings);
  - 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);

Any kind of help would be appreciated! ;-)

BR,

[dlanor]

I have used the SMB support of SMS ever since Eugene implemented it, so I can confirm that it works fine with normal Win2K and WinXPpro computers with standard setups. But using a NAS is a different matter, and may have different limitations.

One significant difference is that SMS uses only port 139 to contact the server, while OPL normally uses port 445.

Windows systems normally listen to both ports but possibly your NAS unit does not.
Perhaps you must do some special configuration to make it do so.

Best regards: dlanor

[deba5er]

@doctorxyz

I could not get username with password to work with SMB on SMS so I use my NAS "everyone" permissions for read-only to my share folder and in the sms.smb file user guest with no password (blank line where password would be). I have no reason to write with SMS, and setting my NAS (QNAP TS-212) share for read only for everyone is not a problem for me in my local network. I use a username/password with OPL and have that account set to read/write for the same share folder on my NAS. Would this work for you too?

Regarding Windows OS support, I never was able to get Vista to work with SMB on SMS. Not a big deal since I moved everything to my NAS but I beat my head against it for awhile with Wireshark and since I didn't have the source code I replaced/forced the various authentication types (LANMAN, NTLM, etc.) in the binary ELF with interesting but in the end unsuccessful results.

I saw EEUG pop into the forums a couple months back noting that he might take a look at a rewrite of the drivers if he had any time away from his real life (lately I know how tough this is myself as I want to get a new SMB installer for PS2-Linux going now but can't find testing time). As only he and maybe a close friend or two has source code to SMS this surely would be the only hope for increased NAS compatibility.

EDIT - Just want to add that I have username/password SMB sharing to SMS working fine with Windows XP like dlanor, so it is a problem with my NAS that causes me to use the everyone/anonymous/guest share.

[doctorxyz]

Thank you very much dlanor and deba5er!

Based on your comments and a fully review of variables envolved, I made a lot of tests here and the problem has been solved... Now both OPL and SMS works with my NAS via SMB protocol!!!
Sometimes SMS doesn't recognise my NAS (giving that -16384 error previous mentioned by me), but wheneven this symptom occurs I simply power off both Console and NAS, wait 10 seconds, then I power on my NAS first and right after that I power on my Console. So following this "procedure" everything goes fine, I assume that this is a NAS issue that SMS isn't able to deal with (contrary to OPL, which always works)... But no problem since now I have this "procedure". ;-)

Here I'm sharing my personal environment settings to help users with the same symptoms... Who knows EEUG comes back here and figure out how to make into SMS the same adjustments made for OPL:

PS2
	IPCONFIG (mc0:/SYS-CONF/IPCONFIG.DAT)
		IP	192.168.1.10		
		Mask	255.255.255.0		
		Gateway	192.168.1.20		
	OPL	(mc0:/OPL/conf_opl.cfg)
		PS2
			See IPCONFIG.DAT	
		PC	IP	192.168.1.20
			Port	139
			Share	PS2SMB
			User	GUEST
			Password	
	SMS	(mc0:/SMS/SMS.smb)
		PC	IP	192.168.1.20
		PC	NAME	DIGITUS_NAS
		PS2	NAME	PS2
		PC	User	Guest
		PC	Password	
		PC	SMB server	Digitus NAS DN-7023
					
NAS
	Status
		System Information
			Host Name	DIGITUS_NAS	
			Group Name	WORKGROUP	
			FW Version	CR1618-1.15 LOADER 3.3	
		Network Information
			DHCP Server	Disable	
		Service Information
			Samba Service	Enable	
			FTP Service	Disable	
	IP Config
		Static IP
		IP		192.168.1.20	
		SubnetMask	255.255.255.0	
		Gateway		192.168.1.10	
		Primary DNS	192.168.1.10	
		Secondary DNS	0.0.0.0	
	SMB Server
		Account List
			User Name	Guest	
			Password
			Access		R/W (Read/Write)	
			En/Disable	Enabled	
			Sharing List
				PS2SMB	
				PUBLIC	
	HDD HM160HC
		PS2SMB
			CD		
			DVD		
			MOVIES		
			VMC		
		PUBLIC

BR,

OBS.: These settings are valid for Deal Extreme's 100M USB 2.0 NAS Adapter - Silver Grey - SKU 149316 ;-)

[E P]

The one main issue I kept having was using a computer name longer than thirteen characters. It would just never connect and it took quite sometime for me to figure that one out. Fortunately after I saw SMB correctly working off a Bart PE disc, I decided to rename my computer and then bingo.

[doctorxyz]

Well written!

[Rotosound_rb666]

I have SMB working for both OPL and SMS on NAS through my router's usb port, with my router flashed with DD-WRT. I needed a little help getting it set up, but it's doing great, now. And the ability to use any USB storage drive as NAS is also a bonus.