Scenario: for some ungodly reason, I am not able to reach a network resource even though I know I should be able to.

For the particular pc that this is in regard to, it is my programmer at work running win7-64. I have multiple machine networks with various ip groups, same basic subnet. I assign an ip to my adapter within each group to make sure I can reach the devices in each group and set static since the networks do not run dhcp at all.

When I click the adapter in the task bar and then "troubleshoot problems", why does win7 automatically assume that dhcp not being on is a problem? What it will do is reset the adapter, turn on dhcp (even though this absolutely cannot work) and shoot the ip structure you have built for the adapter.

Is there a way to lock this down, stop win7 from changing this? I have seen this before where it asks if you want to "make these changes" but win7 doesn't always tell you what it is going to do either. For me, this is a dumbed down version of "troubleshooting" and I can reset the adapter myself with a command prompt in no time without it. What I would like to see is a window pop up telling me that the ip addresses for xxx adapter are going to be reset to dhcp, do you agree?

I just had a utility pc that I have on the same network that is receiving backups of the 18 machine pc's, show me that they have not been able to get there because somehow that pc was set to dhcp and the ending ip address then didn't jive. Real issue and this should never happen.