RNDIS Support Via USB

      RNDIS Support Via USB

      Hi,

      Has anyone tried to use the RNDIS support vi USB as I am a bit confused on how to configure the USB Driver. I know that RNDIS is not currently operating as I have no virtual network device appearing on my desktop PC when I connect the PicoCOM4 device with the ip 192.168.55.101. If I try to resolve the host name "ppp_peer" is comes back as unresolvable.

      Looking on the web it is suggested that only USB Serial or USB RNDIS are possible at any instant and ActiveSync is operating correctly! How does ActiveSync connect?
      Should I loose ActiveSync once the PicoCom4 has been correctly configured?

      If anyone can help I would be very grateful.

      Regards
      Rick

      Re: RNDIS Support Via USB

      Hello,

      PicoCOM4 kernel does not support RNDIS (SYSGEN_USBFN_ETHERNET) at the time.
      It may work when you order a custom kernel, contact <!-- e --><a href="mailto:sales@fs-net.de">sales@fs-net.de</a><!-- e -->.
      F&S Elektronik Systeme GmbH
      As this is an international forum, please try to post in English.
      Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

      Re: RNDIS Support Via USB

      Thanks for the reply ZU,

      I have looked at your web page literature at <!-- m --><a class="postlink" href="http://www.fs-net.de/cms/index.php?id=picocom4&L=1">http://www.fs-net.de/cms/index.php?id=picocom4&L=1</a><!-- m -->
      and under the heading Windows Embedded 6 R3 a list of drivers includes the following with no indication that its an extra??

      Drivers:
      UART (COM1, COM2)
      I²C
      Digital I/ O (DIO)
      USB Host
      USB Device (Mass Storage, RNDIS, Serial)
      SD/ SD-HC/ MMC
      Display (2D, DirectDRAW)
      Ethernet
      CAN 2.0
      Audio incl. Mixer

      As you can see USB Device supports RNDIS out of the box??

      Please can you confirm and if required update your web site.

      Regards
      Rick

      Re: RNDIS Support Via USB

      Hello,

      ok your argument is unbeatable!
      I dont know why the SYSGEN was not set in the very first version, nevertheless i will update the kernel within this week.
      F&S Elektronik Systeme GmbH
      As this is an international forum, please try to post in English.
      Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

      Re: RNDIS Support Via USB

      ZU,

      Installed V1.14 kernel and change the registry setting:-

      HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers

      to a value of "RNDIS"

      rebooted pico and was promted to install new USB device as expected, if I let it install automatically no driver is found. I also tried to redirect to the folder:-

      C:\Program Files\Microsoft ActiveSync\Drivers

      But still the drivers could not be installed, can you help I am running Win XP SP3

      Cheers
      Rick

      Re: RNDIS Support Via USB

      Hello,

      it did not use RNDIS at all, so i have no experience. But i will try ... :
      Microsoft provides a driver for host side (Rndismp.sys). This driver should be already availabel on your PC (W7, XP -> search for it). Here msdn.microsoft.com/en-us/libra…re/ff569967(v=vs.85).aspx you will find some templates for the inf-files.

      Hope this helps (?)
      F&S Elektronik Systeme GmbH
      As this is an international forum, please try to post in English.
      Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

      Re: RNDIS Support Via USB

      ZU

      These are the steps I have completed to install the driver from ActiveSync when using NDIS.

      Change the registry values on PicoCOM4 as detailed below:-

      1) This will change the USB client driver on PicoCOM4 to be RNDIS

      [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers
      DefaultClientDriver = "RNDIS"

      2) This will allow ActiveSync to recognise the device and install the RNDIS host driver on PC

      [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\RNDIS]

      UseActiveSyncIds = 1

      Save these settings

      Reboot PicoCOM4 and plug in USB cable to PC, automatically install new driver.

      Open a terminal window and type ipconfig, you should now see a new LAN device

      ActiveSync will have recognised the device and will attempt to connect, on my PC this fails and trouble shooter does not find any issues.

      I can ping the LAN but not connect to the device web server through it.

      Can anyone test this facility on there PC setup and give feed back to me on the success or failures.

      ZU - I have seen an issue reported on WinCE6 R3 for Host RNDIS which drops the activesync connection and requires a hotfix to platformbuilder, do you apply hotfixes via a set procedure as routine?? Could you find out if there are any more fixes required for RNDIS as it does appear to have some issues on WinCE6.

      Regards
      Rick

      Re: RNDIS Support Via USB

      Hi,
      - hotfix concerning RNDIS (110803) is installed.
      - When i follow your steps above, without set HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\RNDIS]\UseActiveSyncIds = DWORD: 1 everything works fine. Means i can connect telnet, ftp, and http via RNDIS.
      - But i am not able to connect via ActiveSync, i dont know why until now. Did you checked msdn.microsoft.com/en-us/libra…76(v=winembedded.60).aspx?
      F&S Elektronik Systeme GmbH
      As this is an international forum, please try to post in English.
      Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

      Re: RNDIS Support Via USB

      Hm,
      i the meanwhile i checked several threads in the www. Seems that nobody get ActiveSync work over RNDIS under WCE only under WM!
      F&S Elektronik Systeme GmbH
      As this is an international forum, please try to post in English.
      Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

      Re: RNDIS Support Via USB

      ZU

      Are you able to ping hostname/ip define in the rndisfn1\param\tcpip registry keys??

      When I try they are not available, event turned off firewall. This is my network setup:-


      H:\>ipconfig /all

      Windows IP Configuration

      Host Name . . . . . . . . . . . . : xxxxxx
      Primary Dns Suffix . . . . . . . : xxxx
      Node Type . . . . . . . . . . . . : Hybrid
      IP Routing Enabled. . . . . . . . : No
      WINS Proxy Enabled. . . . . . . . : No
      DNS Suffix Search List. . . . . . : xxxxx

      Ethernet adapter Local Area Connection:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Intel(R) 82562V-2 10/100 Network Con
      nection
      Physical Address. . . . . . . . . : xxxxxxxx
      Dhcp Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      IP Address. . . . . . . . . . . . : 192.168.0.51
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . : 192.168.0.254
      DHCP Server . . . . . . . . . . . : 192.168.0.2
      DNS Servers . . . . . . . . . . . : 192.168.0.2
      Primary WINS Server . . . . . . . : 192.168.0.2
      Lease Obtained. . . . . . . . . . : 26 November 2013 16:43:12
      Lease Expires . . . . . . . . . . : 04 December 2013 16:43:12

      Ethernet adapter VirtualBox Host-Only Network:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapte
      r
      Physical Address. . . . . . . . . : xxxxxxxxxx
      Dhcp Enabled. . . . . . . . . . . : No
      IP Address. . . . . . . . . . . . : 192.168.56.1
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . :

      Ethernet adapter Local Area Connection 8:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Windows Mobile-based Device #2
      Physical Address. . . . . . . . . : xxxxxxxxxxx
      Dhcp Enabled. . . . . . . . . . . : No
      IP Address. . . . . . . . . . . . : 192.168.0.201
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . : 192.168.0.2

      H:\>ping 192.168.0.200

      Pinging 192.168.0.200 with 32 bytes of data:

      Request timed out.
      Request timed out.
      Request timed out.
      Request timed out.

      Ping statistics for 192.168.0.200:
      Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

      What OS are you on, this is XP SP3

      Regards
      Rick

      Re: RNDIS Support Via USB

      Hi Rick,

      Source Code

      1. Are you able to ping hostname/ip define in the rndisfn1\param\tcpip registry keys??
      Yes,

      i download kerel contains RNDIS feature and modify only:

      Source Code

      1. Welcome to the Windows CE Telnet Service on PicoCOM4
      2. Pocket CMD v 6.00
      3. \> ndcucfg
      4. NetDCU Config Utility Ready
      5. Version: 55
      6. Build from: Nov 30 2012
      7. Type help for commands
      8. !>reg open \drivers\usb\functiondrivers
      9. \: HKEY_LOCAL_MACHINE\drivers\usb\functiondrivers
      10. OK
      11. !>reg set value defaultclientdriver string RNDIS
      12. OK
      13. !>reg save
      14. OK
      15. !>reboot

      Then i get following

      Source Code

      1. Welcome to the Windows CE Telnet Service on PicoCOM4
      2. Pocket CMD v 6.00
      3. \> ipconfig
      4. Windows IP configuration
      5. Ethernet adapter [ETHNETA1]:
      6. IP Address ........ : 10.0.0.78
      7. Subnet Mask ....... : 255.255.255.0
      8. Default Gateway ... : 10.0.0.5
      9. Ethernet adapter [RNDISFN1]:
      10. IP Address ........ : 169.254.254.70
      11. Subnet Mask ....... : 255.255.0.0
      12. DNS Servers........ : 10.0.0.1
      13. 10.0.0.5
      14. \>

      and can ping from host

      Source Code

      1. Microsoft Windows [Version 6.1.7601]
      2. Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
      3. C:\Users\czutter.FS-NET>ping 169.254.254.70
      4. Ping wird ausgeführt für 169.254.254.70 mit 32 Bytes Daten:
      5. Antwort von 169.254.254.70: Bytes=32 Zeit=2ms TTL=128
      6. Antwort von 169.254.254.70: Bytes=32 Zeit=1ms TTL=128
      7. Antwort von 169.254.254.70: Bytes=32 Zeit=1ms TTL=128
      8. Antwort von 169.254.254.70: Bytes=32 Zeit=1ms TTL=128
      9. Ping-Statistik für 169.254.254.70:
      10. Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
      11. (0% Verlust),
      12. Ca. Zeitangaben in Millisek.:
      13. Minimum = 1ms, Maximum = 2ms, Mittelwert = 1ms
      14. C:\Users\czutter.FS-NET>ipconfig
      15. Windows-IP-Konfiguration
      16. Ethernet-Adapter LAN-Verbindung 3:
      17. Verbindungsspezifisches DNS-Suffix:
      18. IPv4-Adresse (Auto. Konfiguration): 169.254.167.16
      19. Subnetzmaske . . . . . . . . . . : 255.255.0.0
      20. Standardgateway . . . . . . . . . :
      21. Ethernet-Adapter LAN-Verbindung:
      22. Verbindungsspezifisches DNS-Suffix: fs-net.local
      23. Verbindungslokale IPv6-Adresse . : fe80::3c45:8f5f:c744:5f2e%13
      24. IPv4-Adresse . . . . . . . . . . : 10.0.0.73
      25. Subnetzmaske . . . . . . . . . . : 255.255.255.0
      26. Standardgateway . . . . . . . . . : 10.0.0.5
      27. Tunneladapter isatap.fs-net.local:
      28. Medienstatus. . . . . . . . . . . : Medium getrennt
      29. Verbindungsspezifisches DNS-Suffix: fs-net.local
      30. Tunneladapter LAN-Verbindung* 12:
      31. Medienstatus. . . . . . . . . . . : Medium getrennt
      32. Verbindungsspezifisches DNS-Suffix:
      33. Tunneladapter LAN-Verbindung* 9:
      34. Medienstatus. . . . . . . . . . . : Medium getrennt
      35. Verbindungsspezifisches DNS-Suffix:
      36. Tunneladapter isatap.{9ACEB9D5-F7AA-4ACD-AE03-102264A906C9}:
      37. Medienstatus. . . . . . . . . . . : Medium getrennt
      38. Verbindungsspezifisches DNS-Suffix:
      39. C:\Users\czutter.FS-NET>

      also i can connect "169.254.254.70" via telnet, ftp and http. So everything works, without ActiveSync:-(.

      Note, auto configuration of IP may take a while (at my system about 20s).
      F&S Elektronik Systeme GmbH
      As this is an international forum, please try to post in English.
      Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

      Re: RNDIS Support Via USB

      ZU

      Thanks for your support on this, I still cannot get my system to connect as the IP addresses are on different sub nets, I may need to remove the driver loaded on my PC to the PicoCOM Vid Pid values and retest but I have run out of time on this so will work round with wired Ethernet device for now. I still need Activesync capability when using RNDIS as I use RAPI calls over the USB connection for some of my applications so cannot run a system without ActiveSync.

      Regards
      Rick