DHCP BAD_ADDRESS

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I upgraded my build environment to FP2007 and upgraded my Target Designer
configuration. The new runtime produces BAD_ADDRESS entries on our DHCP
servers (W2K3). I tried a lot of things found in newsgroups like enabling
DHCP conflict detection, disabling EWF completely

Now I found this:
http://support.microsoft.com/default.aspx/kb/830993/

This should be already fixed in FP2007 or not? File version of my runtime is
5.1.2600.2912.

I tried 3 different devices with the same runtime image and all of them
produces DHCP errors I never had before I upgraded to FP2007. Anyone else has
problems with DHCP and FP2007 or can give me additional tipps?

thanks
Jens
 
If you haven't already, it is a good idea to review all of the component
settings in Target Designer after upgrading to FP2007.
This is because FP2007 resets a lot of them to default values.
 
I found that EWF might cause the error. Here the way I got it fixed:
- in Settings of "Enhanced Write Filter" unchecked "Start EWF Enabled"
- added FBA Generic Command to Extra Resources to enable EWF as the very
last step of FBA

FBA Generic Command Details:
- FilePath: %11%\cmd.exe
- Arguments: /c %11%EWFMGR.EXE D: -enable
- Phase: 65535 (last one possble!)
- everything uses default values

I don't know why EWF blocks something it didn't do in my pre-fp2007 runtime
but with above settings I got it working.
 
Back
Top