Host Engineering Forum

General Category => Do-more CPUs and Do-more Designer Software => Topic started by: lyndonschroeder on November 07, 2013, 12:12:40 PM

Title: Haveing problem using NetEdit to set a DoMore H2-DM1E Static IP Address
Post by: lyndonschroeder on November 07, 2013, 12:12:40 PM

Hi,

I have setup 3 system before, but this time when I try to set the IP address using NetEdit I keep getting an error message saying 'Error 0x8006 in WriteGeneral while writing DT_IP_ADDRESS!'. I was able to set the IP address for the H2-EBC100 slave on this same system no problem. Any ideas on what else I can try?

Thanks,
Lyndon

Title: Re: Haveing problem using NetEdit to set a DoMore H2-DM1E Static IP Address
Post by: Greg on November 07, 2013, 01:31:47 PM

This error (0x8006) is basically a timeout message. A few things that can cause this:
- Network is too busy (try multiple times).
- Your Host Ethernet device is too busy (stop things from talking to it besides NetEdit).
- Your Windows firewall is ON (turn it OFF).
- You have multiple NICs (disable the one(s) you are not using, or reprioritize them).

Title: Re: Haveing problem using NetEdit to set a DoMore H2-DM1E Static IP Address
Post by: lyndonschroeder on November 07, 2013, 05:20:49 PM

I connected using USB and found the network mask was set to something strange. I set the network parameters from the USB connection and that allowed to DoMore to appear online.

Title: Re: Haveing problem using NetEdit to set a DoMore H2-DM1E Static IP Address
Post by: Greg on November 07, 2013, 05:24:25 PM

...or that  :D

Title: Re: Haveing problem using NetEdit to set a DoMore H2-DM1E Static IP Address
Post by: BobO on November 07, 2013, 05:44:35 PM

Quote from: lyndonschroeder on November 07, 2013, 05:20:49 PM

I connected using USB and found the network mask was set to something strange. I set the network parameters from the USB connection and that allowed to DoMore to appear online.

Later version of Windows aren't friendly to network configs that aren't valid for the PC. Once a unit gets a bad config, it either has to be cleared, or as you discovered, use another connection to set it up. We added that config option specifically because of these issues.