none
Device is not getting IP address by DHCP RRS feed

  • Question

  • We recently updated our Windows Embedded Compact 7 development environment with the monthly update of February 2013 (last update Nov. resp July 2012). After re-building and loading the new OS image we faced the problem that the device did not get any IP address by DHCP anymore. We found that the problem somehow was introduced starting with the monthly update of December 2012 and it persists through the January and February updates. The problem seems to be related to the release build whereas when loading the debug build of the OS it works fine. We could also isolate the problematic dll's - afd.dll and tcpipreg.dll. If we replace them with those from the November update everything works fine.

    Did anybody else face this problem?

    Has anybody any idea what could be wrong?

    Could the problem be related to some registry settings?

    Any sort of help or hint is really appreciated. Thanks!

    Rico

    Monday, April 15, 2013 7:26 AM

All replies

  • Is your registry settings proper ? Can you share the registry settings ?

    Best Regards,

    Rakesh.

    Tuesday, April 16, 2013 5:29 AM
  • Sounds like a good case for a Microsoft Support Incident.

    There are 2 free support incidents with your purchase of Platform Builder (or at least this used to be the case until WCE6, can anybody confirm this is still true for WEC7?)


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Wednesday, April 17, 2013 9:02 PM
    Moderator
  • We use the Toradex Colobri T20 module, which has an ASIX AX88772B ethernet controller on it.
    Following are the registry settings regarding TCPIP:

    [HKEY_LOCAL_MACHINE\Comm\AX88772B]
       "DisplayName"="ASIX AX88772B USB 2.0 Fast Ethernet Driver"
       "Group"="NDIS"
       "ImagePath"="AX88772B.dll"
    
    [HKEY_LOCAL_MACHINE\Comm\AX88772B\Linkage]
       "Route"=multi_sz:"AX88772B1"
    
    [HKEY_LOCAL_MACHINE\Comm\AX88772B1]
       "DisplayName"="ASIX AX88772B USB 2.0 Fast Ethernet Driver"
       "Group"="NDIS"
       "ImagePath"="AX88772B.dll"
    
    [HKEY_LOCAL_MACHINE\Comm\AX88772B1\Parms]
       "BusNumber"=dword:0
       "BusType"=dword:1       
    ; AX88772B driver parameters:
       "ConnectionType"=dword:0
       "FlowControl"=dword:3
       "WakeUp"=dword:0
       "WakeUpFrameType"=dword:3
       "VlanEnable"=dword:0
       "VlanId"=dword:0
       "AutoDetach"=dword:2
       "WolLinkSpeed"=dword:1
       "Checksum"=dword:1
        
    [HKEY_LOCAL_MACHINE\Comm\AX88772B1\Parms\TcpIp]
       "AutoCfg"=dword:1
       "EnableDHCP"=dword:1
       "UseZeroBroadcast"=dword:0
    

    Problem still not solved.

    Regards, Rico

    Thursday, April 18, 2013 9:57 AM
  • Additon: Configuring a static IP address is not working either.

    [HKEY_LOCAL_MACHINE\Comm\AX88772B1\Parms\TcpIp]
       "EnableDHCP"=dword:0
       "IpAddress"="192.168.0.173"
       "DefaultGateway"="192.168.0.2"
       "Subnetmask"="255.255.255.0"
       "DNS"="192.168.0.23"

    Any idea?

    Rico

    Thursday, April 18, 2013 11:33 AM
  • Get a wireshark trace and see if you can figure out exactly what goes wrong.

    Then open a support incident with MS. If you can make it work by replacing the older version of afd.dll and tcpipreg.dll (as you said), then surely the update is the problem and MS should fix it. If its a bug, it won't count against your free support incidents.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Thursday, April 18, 2013 12:13 PM
    Moderator