• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 5113 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

File Sharing (SMB) not working for WEC7 on DM3730

Zack Zadecki
Intellectual 745 points
Other Parts Discussed in Thread: DM3730, OMAP3530

All,

I have a problem with WEC7 on DM3730 – I cannot make File Sharing to work. At this point I still don’t know whether I’m missing some steps or this feature is not working for WEC7. 
I’m following my steps from Windows CE 6, which are:

1. I add the following components:

    Internet Connection Sharing (ICS)
    Windows Networking API/Redirector (SMB/CIFS)
    File Server (SMB/CIFS)
    File Server Customizable Web UI
    Web Server Administration ISAPI

2. I add/modify the following registry settings:

[HKEY_LOCAL_MACHINE\Ident]
    "OrigName"="MEBWinCE"
    "Name"="wec7meb"
[HKEY_LOCAL_MACHINE\Services\SMBServer]
    "AdapterList"="*"
[HKEY_LOCAL_MACHINE\Services\Smbserver\Shares]
    "UseAuthentication"=dword:0
[HKEY_LOCAL_MACHINE\Services\SMBServer\Shares\StorageCard]
    "Type"=dword:0
    "Path"="Storage Card"
    "UserList"="*"

With all these changes we were able to make the file sharing working on WinCE6, however it’s not working for WEC7.
For SMBServer, I can see all the other registry settings there:

[HKEY_LOCAL_MACHINE\Services\SMBServer]
    "DLL"="smbserver.dll"
    "Keep"=dword:1
    "Order"=dword:12
    "Prefix"="SMB"
    "Index"=dword:0

Also, the smbserver.dll is part of the image – I can see it in the Windows folder.
But… I cannot see the SMB service running when I type “services list” from the command line.

Could you please help me with that?
Thank you!!

Best regards,
Zack

 

  • 0
    Intellectual 745 points

    All,

    This is my debug output from starting the SMBServer service:

    189487 PID:400002 TID:5f200a2 OSAXST1: >>> Loading Module 'smbserver.dll' (0xC04B11A8) at address 0x42E00000-0x42EAD000 in Process 'NK.EXE' (0x849EFAD0)

    PB Debugger Loaded symbols for 'C:\WINCE700_VER2004_ZACK\OSDESIGNS\EVM_3530\EVM_3530\RELDIR\EVM_OMAP3530_ARMV7_DEBUG\SMBSERVER.DLL'

     189652 PID:59d0092 TID:5f200a2 OSAXST1: >>> Loading Module 'smbserver.dll' (0xC04B11A8) at address 0x42E00000-0x42EAD000 in Process 'servicesd.exe' (0xC0490E10)

     189654 PID:59d0092 TID:5f200a2 SMBSRV: DLL_PROCESS_ATTACH, hInst:0xC04B11A8

     189688 PID:59d0092 TID:5f200a2  FilterFolder::InitializeFilters load device filter at order 0

     189688 PID:59d0092 TID:5f200a2 SERVICES: Creating new service filter for service <Services\SMBServer>

     189691 PID:59d0092 TID:41600a6 +SMB_Init

     189691 PID:59d0092 TID:41600a6 SMB_SRV: **PASSWORDS DISABLED**

     189692 PID:59d0092 TID:41600a6 SMB_SRV: Server GUID not specified in registry -- creating a new one

     189694 PID:59d0092 TID:41600a6 SMB_SRV: Name value under HKLM\Services\SMBServer\SmbServerNameHardeningLevel is not there.

     189694 PID:59d0092 TID:41600a6 SMB_SRV: Server hardening level is not specified in registry -- using NO HARDENED

     189694 PID:59d0092 TID:41600a6 SMB_SRV: Workgroup reg value not set -- using WORKGROUP

     189695 PID:59d0092 TID:41600a6 SMB_SRV: Registering CName wec7meb

     189695 PID:59d0092 TID:41600a6 Loading Share: StorageCard

     189696 PID:59d0092 TID:41600a6 SMB_PRINT: Loading Registry: Services\SMBServer\Shares\StorageCard

     189696 PID:59d0092 TID:41600a6    -- Type: 0

     189696 PID:59d0092 TID:41600a6    -- Path: \Storage Card

     189697 PID:59d0092 TID:41600a6    -- ACL: *

     189697 PID:59d0092 TID:41600a6     --  NOT USING READ-ONLY ACL's!

     189697 PID:59d0092 TID:41600a6    -- Read-ONLYACL:

     189698 PID:59d0092 TID:41600a6 SMBSRV-CRACKER: cracker delay thread created 0x29e1403

     189955 PID:59d0092 TID:41600a6 SMBSRV:Starting TCP transport

     189955 PID:59d0092 TID:41600a6 SMBSRV:Starting NETBIOS transport

     189989 PID:59d0092 TID:41600a6 +SMBSRV:NetBIOSNotifyFunc: LANA=1, Idx=2, IPv4=cb40fea9

     189989 PID:59d0092 TID:41600a6   SMBSRV:InitLana:  NETBIOS LANA(1), IP4Addr=cb40fea9, name=VII

     189989 PID:59d0092 TID:41600a6    SMBSRV:AllowLana: All adapters are given access.

     190750 PID:59d0092 TID:41600a6 SMBSRV:InitLana: Starting NetBios at index: 1

     190751 PID:59d0092 TID:41600a6 -SMBSRV:NetBIOSNotifyFunc

     190751 PID:59d0092 TID:41600a6 +SMBSRV:NetBIOSNotifyFunc: LANA=0, Idx=1, IPv4=100007f

     190751 PID:59d0092 TID:41600a6   SMBSRV:InitLana:  NETBIOS LANA(0), IP4Addr=100007f, name=lclot

     190751 PID:59d0092 TID:41600a6    SMBSRV:AllowLana: All adapters are given access.

     190751 PID:59d0092 TID:41600a6 SMBSRV:Netbios - NCB Error 0x14

     190752 PID:59d0092 TID:41600a6   SMBSRV:InitLana: NCBADDNAME returned NRC_ADPTMALFN

     190752 PID:59d0092 TID:41600a6  SMBSRV:Error initing lana(0), IPv4=100007f!

     190752 PID:59d0092 TID:41600a6 -SMBSRV:NetBIOSNotifyFunc

     190752 PID:59d0092 TID:41600a6 -SMB_Init

     190758 PID:59d0092 TID:4a800a6 SMBSRV-LSTNTHREAD: Binding listen socket: 0x13

    It looks like the service starts, but there are some errors. Please let me know what can I do to fix them.

    Thank you!

    Zack

  • 0 in reply to Zack Zadecki
    Intellectual 745 points

    All,

    I've also built a CEPC version of our OS image and File Sharing works there.  So it looks like this is something wrong with our platform or/and some incompatibility between platform and OS. The platform is DM3730 with a custom board (similar to EVM).

    I'm still trying to figure it out.  Please let me know of you have any other ideas.

    Best regards,

    Zack

  • 0 in reply to Zack Zadecki
    Mastermind 9310 points

    I Hello,

    I tested the file server on my end on a two different BSPs to see if I could get the file server running and sharing a folder. I was able to get the service running and I could access the device from my desktop; however, I could not get a folder to be shared. In both BSPs, here are the steps I had taken to get the service running:

    1. Enable SYSGEN_REDIR

    2. Enable SYSGEN_SMB_FILE

    3. Enable SYSGEN_SMB_UI

    4. Added the following registry keys to the bottom of platform.reg to set up the server

    [HKEY_LOCAL_MACHINE\Ident]

       "OrigName"="test"

       "Name"="testname"

      

    [HKEY_LOCAL_MACHINE\Services\SMBServer]

       "AdapterList"="*"

       "UserAuthetication"=dword:0

     

    [HKEY_LOCAL_MACHINE\Services\SMBServer\Shares]

       "UserAuthetication"=dword:0

      

    [HKEY_LOCAL_MACHINE\Services\SMBServer\Shares\Windows]

       "Type"=dword:0

       "Path"="\\Windows"

       "UserAuthetication"=dword:0

       "UserList"="@*;"

      

    [HKEY_LOCAL_MACHINE\Services\SMBServer\Shares\HD1]

       "Type"=dword:0

       "Path"="\\Hard Disk"

       "UserAuthetication"=dword:0

      

    [HKEY_LOCAL_MACHINE\Services\SMBServer]

       "DLL"="smbserver.dll"

       "Keep"=dword:1

       "Order"=dword:85

       "Prefix"="SMB"

       "Index"=dword:0

       "UserAuthetication"=dword:0

      

    [HKEY_LOCAL_MACHINE\DebugZones]

       "SMBSERVER"=dword:FFFFF

    Although I do not see my share, the service did initialize properly and is still running. GIve these settings a try to see if they work.

  • 0 in reply to Adeneo Embedded support team
    Intellectual 745 points

    Adeneo Embedded suport team,

    Thank you for your response.  I've tried your settings (actually it's very similar to my previous ones, except ypu've added "UserAuthetication"=dword:0 in several places) and it was the same - the SMBServer didn't run.

    In the meantime I've created another test OS for my platform but without BinFS (we use BinFS not to waste so much RAM for another copy of the OS image) and the SMBServer worked there.  After that I tried to find out what module has to be in the NK region to make SMB working.  But I haven't found one.  I've moved all my network modules to the NK region, actualy I've moved there almost everything... It looks like the presence of the BinFS region causes SMB to fail.

    Do you think this is possible that the new implementation of SMBServer cannot work together with BinFS??

    We didn't have any problems with running both - SMB and BinFS on CE6.

    Please let me know.

    Best regards,

    Zack

     

  • 0 in reply to Zack Zadecki
    Intellectual 745 points

    All,

    I’ve figured out why file sharing was not working on our platform and I have it working now.  

    I don’t understand this dependency, but the file “locale.nls” has to be in the first region (NK).  If I move it to BinFS – file sharing doesn’t work.

    That's very interesting.

    Thank you very much for your help on this!

    Best regards,

    Zack

     

  • 0 in reply to Zack Zadecki
    Prodigy 175 points

    Zack Zadecki said:

    All,

    I’ve figured out why file sharing was not working on our platform and I have it working now.  

    I don’t understand this dependency, but the file “locale.nls” has to be in the first region (NK).  If I move it to BinFS – file sharing doesn’t work.

    That's very interesting.

    Thank you very much for your help on this!

    Best regards,

    Zack

     



    Zack, I dont understand, what have you done to run SMB?

  • 0 in reply to Denis Krasutski
    Intellectual 745 points

    Denis,

    My OS is divided into two regions: Regular NK and the second, based on BinFS. Initially my "locale.nls" file was placed in the second region (BinFS), and somehow it caused file sharing not to work.  This file has to be in the NK region.

    Best regards,

    Zack