Paul
Fri Mar 10 10:44:25 CST 2006
I understand. If it were me, I'd find out what the actual field problem is.
If it's DHCP, nothing you do to CE is going to fix it. CE assumes that you
know what you're doing with your DHCP server, so it's not going to give any
opportunity to choose a different address. If the user is entering it, he's
entering something that's clearly wrong, so you've got a training issue. At
that point, you can evaluate the benefits of cloning and modifying NETUI to
check the addresses entered by the user before returning them. Figure that
it will take about two weeks to get the component cloned, modified,
compiling as part of your platform, and properly replacing the Microsoft
version. You'd have to modify network.c, the function AdapterIPProperties()
(at least in CE 4.2, which is what's in front of me).
Paul T.
"anonymous" <anonymous@discussions.microsoft.com> wrote in message
news:E34A25AC-09E7-46D7-886E-7081298871B6@microsoft.com...
> I'm not sure what users are doing, but in CE 4.x, 127.0.0.1 wasn't checked
> and we've had boxes returned since the network was unavailable after it
> was
> set. I don't know if they have a bad DHCP setup or are trying to setup
> private networks and are just picking a number.
>
> Doesn't really matter. CE is not robust to a simple typo. Trying to figure
> out why netui has functions that appear to be correct that aren't getting
> called.
>
> "Paul G. Tobey [eMVP]" wrote:
>
>> Sounds like a bug in the UI. Why would you want to do that, though?
>> Those
>> address ranges are for various things (multicast groups, etc.) There's
>> no
>> reason to intentionally set your IP in one of those ranges that I can
>> think
>> of...
>>
>> Paul T.
>>
>> "anonymous" <anonymous@discussions.microsoft.com> wrote in message
>> news:2004232C-1C9F-4D54-826A-640525E40AFC@microsoft.com...
>> > In NetUI and ConnMC, there is a function CheckAddress which checks that
>> > an
>> > IP
>> > address a.b.c.d meets:
>> > a != 0, 127, 224-255
>> > d != 255
>> >
>> > These functions don't appear to be called by anything I can find. If I
>> > set
>> > the IP to 224.0.0.1 or a=224-255, the adapter disappears from the
>> > network
>> > control panel, and I have to erase the registry to get it back.
>> >
>> > Has anyone found this bug and worked out a fix to prevent a user from
>> > getting into this state of needing to reset the registry ?
>>
>>
>>