V
vince
it seems that if you try to use wntipcfg on w2k or wxp and you have a
dialup connection active (either modem or vpn) then you will always
get the enabledchp flag error. This has only appeared in w2k or wxp as
the same program wntipcfg works perfectly fine on nt4. It is as if
they have changed some registry settings for dialup that are
inconsistant with wntipcfg.
We us the program a lot for our end users to give us their ip address,
in a nice and easy way to use.
you can be consistant with users of all windows os's by renaming
wntipcfg to winipcfg and all works fine.
just as an afterthought has anybody found a fix for this yet or is it
yet again a bug that microsoft will not fix as it is not part of any
package
dialup connection active (either modem or vpn) then you will always
get the enabledchp flag error. This has only appeared in w2k or wxp as
the same program wntipcfg works perfectly fine on nt4. It is as if
they have changed some registry settings for dialup that are
inconsistant with wntipcfg.
We us the program a lot for our end users to give us their ip address,
in a nice and easy way to use.
you can be consistant with users of all windows os's by renaming
wntipcfg to winipcfg and all works fine.
just as an afterthought has anybody found a fix for this yet or is it
yet again a bug that microsoft will not fix as it is not part of any
package