Has anyone else run into this in the last few days? (like since last Tuesday)
I've had 10 or 12 Windows 7 Pro systems, so far, that have had their NIC IP address settings switched from manually configured to DHCP. At first I thought it was a fluke, but I keep finding more and more systems that this has happened to. And there was a forced reboot update from MSoft last week.
I'm not suggesting nefarious activity, just that I have never seen this happen before.
All of the systems are locked down with Admin accounts that use a password that is not available to anyone but myself and one other person. Some of the computers are running video display systems (kiosks)...not even touched by users.
The one thing they all have in common is Windows 7 pro.
Anything happening like that to anyone else?
Thanks!
Mike Copeland
I just checked several of our manually configured Win 7 Pro systems, and all of them remain manually configured after automatically installing the updates of 1/13. Sorry.
Mike
~~~~~~~~~~~~~~~~~~~~~~
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Mike Copeland Sent: Thursday, January 21, 2016 4:36 PM To: profoxtech@leafe.com Subject: [NF] Win 7 Update messing with network settings?
Has anyone else run into this in the last few days? (like since last Tuesday)
I've had 10 or 12 Windows 7 Pro systems, so far, that have had their NIC IP address settings switched from manually configured to DHCP. At first I thought it was a fluke, but I keep finding more and more systems that this has happened to. And there was a forced reboot update from MSoft last week.
I'm not suggesting nefarious activity, just that I have never seen this happen before.
All of the systems are locked down with Admin accounts that use a password that is not available to anyone but myself and one other person. Some of the computers are running video display systems (kiosks)...not even touched by users.
The one thing they all have in common is Windows 7 pro.
Anything happening like that to anyone else?
Thanks!
Mike Copeland
Thanks, Mike. Maybe I've got other gremlins in the soup...
The symptom that has been showing up is the "Set Network Location" prompt you get when you create a new network interface, where it asks you to select whether the new circuit is a Home, Public, or Work network. After making the selection, if you look at the IPV4 settings for the NIC it shows DHCP.
I know it's most likely just a bit flipped in the registry, but this is a first in my experience.
Thanks for the feedback!
Mike Copeland
Michael Glassman wrote:
I just checked several of our manually configured Win 7 Pro systems, and all of them remain manually configured after automatically installing the updates of 1/13. Sorry.
Mike
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Mike Copeland Sent: Thursday, January 21, 2016 4:36 PM To: profoxtech@leafe.com Subject: [NF] Win 7 Update messing with network settings? Has anyone else run into this in the last few days? (like since last Tuesday) I've had 10 or 12 Windows 7 Pro systems, so far, that have had their NIC IP address settings switched from manually configured to DHCP. At first I thought it was a fluke, but I keep finding more and more systems that this has happened to. And there was a forced reboot update from MSoft last week. I'm not suggesting nefarious activity, just that I have never seen this happen before. All of the systems are locked down with Admin accounts that use a password that is not available to anyone but myself and one other person. Some of the computers are running video display systems (kiosks)...not even touched by users. The one thing they all have in common is Windows 7 pro. Anything happening like that to anyone else? Thanks! Mike Copeland
[excessive quoting removed by server]
Hi, Mike:
Not seeing that symptom here, and web searches coming up empty, so I blame you ;)
Did you make any changes to the network that might have tripped this reaction? Maybe update a server, mess with your AD, fix a typo in the server name, domain name, take an old machine offline?
I've seen this on occasion when Windows decides I need a new network connection, despite the fact it's set up two ethernet connections and three wireless connections, all to the same LAN.
On Thu, Jan 21, 2016 at 8:29 PM, Mike Copeland mike@ggisoft.com wrote:
Thanks, Mike. Maybe I've got other gremlins in the soup...
The symptom that has been showing up is the "Set Network Location" prompt you get when you create a new network interface, where it asks you to select whether the new circuit is a Home, Public, or Work network. After making the selection, if you look at the IPV4 settings for the NIC it shows DHCP.
I know it's most likely just a bit flipped in the registry, but this is a first in my experience.
Thanks for the feedback!
Mike Copeland
Michael Glassman wrote:
I just checked several of our manually configured Win 7 Pro systems, and all of them remain manually configured after automatically installing the updates of 1/13. Sorry.
Mike
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Mike Copeland Sent: Thursday, January 21, 2016 4:36 PM To: profoxtech@leafe.com Subject: [NF] Win 7 Update messing with network settings? Has anyone else run into this in the last few days? (like since last Tuesday) I've had 10 or 12 Windows 7 Pro systems, so far, that have had their NIC IP address settings switched from manually configured to DHCP. At first I thought it was a fluke, but I keep finding more and more systems that this has happened to. And there was a forced reboot update from MSoft last week. I'm not suggesting nefarious activity, just that I have never seen this happen before. All of the systems are locked down with Admin accounts that use a password that is not available to anyone but myself and one other person. Some of the computers are running video display systems (kiosks)...not even touched by users. The one thing they all have in common is Windows 7 pro. Anything happening like that to anyone else? Thanks! Mike Copeland
[excessive quoting removed by server]
Ted,
The "blame me" line starts over there and extends around the corner...welcome!
Changes...that's hard to not have happen on a network that includes 4 buildings and nearly 400 pieces of 'stuff' that somehow access the same network, whether directly or via VPN, and a business that always seems to be churning.
But, no, nothing that I would expect to have caused this. The only change was that I removed two WIFI WAPs and isolated them on their own subnet with private routers and WAN IPs. In other words, they "went away" as far as the main data network was concerned. Other than that, people continue to bring their own tablets and cellphones and try to connect in whatever way they can dream up. (We seem to attract former Best Buy salespeople who are confident they know everything there is to know about computers.)
No AD is involved since none exists, all drive sharing is via Linux Samba (without AD). Everything is, or about 99% is, static IP, with a few devices (IP phones, laptops) using DHCP. No server name change, no domain name change/addition. Machines come and go every few days as they have problems (PSUs fail, UPS fail, case fans annoy and get shut down). With 300+ terminals it's "always something."
That's comforting to hear that you've at least seen this happen. I have convinced myself it isn't human intervention, and it's not infection. The one thing that is consistent is that all of the machines showing this behavior were rebooted on the same day, 1/13/16. But, there are also many other Win 7 Pro machines that were updated and rebooted on that date, that have not tripped over this problem.
My best guess is that this was some odd alignment of a particular flavor of NIC driver and updates kicking each other in the shins. Unless it continues, I'm pretty confident I've found and fixed all of the affected systems and I'm off to other issues. I just can't get rid of this nagging desire to want to understand why these electronic gizmos do what they do...
Many thanks for the confirmation/feedback!
Mike
Ted Roche wrote:
Hi, Mike:
Not seeing that symptom here, and web searches coming up empty, so I blame you ;)
Did you make any changes to the network that might have tripped this reaction? Maybe update a server, mess with your AD, fix a typo in the server name, domain name, take an old machine offline?
I've seen this on occasion when Windows decides I need a new network connection, despite the fact it's set up two ethernet connections and three wireless connections, all to the same LAN.
On Thu, Jan 21, 2016 at 8:29 PM, Mike Copeland mike@ggisoft.com wrote:
Thanks, Mike. Maybe I've got other gremlins in the soup...
The symptom that has been showing up is the "Set Network Location" prompt you get when you create a new network interface, where it asks you to select whether the new circuit is a Home, Public, or Work network. After making the selection, if you look at the IPV4 settings for the NIC it shows DHCP.
I know it's most likely just a bit flipped in the registry, but this is a first in my experience.
Thanks for the feedback!
Mike Copeland
Michael Glassman wrote:
I just checked several of our manually configured Win 7 Pro systems, and all of them remain manually configured after automatically installing the updates of 1/13. Sorry.
Mike
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Mike Copeland Sent: Thursday, January 21, 2016 4:36 PM To: profoxtech@leafe.com Subject: [NF] Win 7 Update messing with network settings? Has anyone else run into this in the last few days? (like since last Tuesday) I've had 10 or 12 Windows 7 Pro systems, so far, that have had their NIC IP address settings switched from manually configured to DHCP. At first I thought it was a fluke, but I keep finding more and more systems that this has happened to. And there was a forced reboot update from MSoft last week. I'm not suggesting nefarious activity, just that I have never seen this happen before. All of the systems are locked down with Admin accounts that use a password that is not available to anyone but myself and one other person. Some of the computers are running video display systems (kiosks)...not even touched by users. The one thing they all have in common is Windows 7 pro. Anything happening like that to anyone else? Thanks! Mike Copeland
[excessive quoting removed by server]
<snip>I just can't get rid of this nagging desire to want to understand why these electronic gizmos do what they do...</snip>
I think we all suffer with that!
Mike
~~~~~~~~~~~~~~~~~~
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Mike Copeland Sent: Friday, January 22, 2016 11:55 AM To: profoxtech@leafe.com Subject: Re: [NF] Win 7 Update messing with network settings?
Ted,
The "blame me" line starts over there and extends around the corner...welcome!
Changes...that's hard to not have happen on a network that includes 4 buildings and nearly 400 pieces of 'stuff' that somehow access the same network, whether directly or via VPN, and a business that always seems to be churning.
But, no, nothing that I would expect to have caused this. The only change was that I removed two WIFI WAPs and isolated them on their own subnet with private routers and WAN IPs. In other words, they "went away" as far as the main data network was concerned. Other than that, people continue to bring their own tablets and cellphones and try to connect in whatever way they can dream up. (We seem to attract former Best Buy salespeople who are confident they know everything there is to know about computers.)
No AD is involved since none exists, all drive sharing is via Linux Samba (without AD). Everything is, or about 99% is, static IP, with a few devices (IP phones, laptops) using DHCP. No server name change, no domain name change/addition. Machines come and go every few days as they have problems (PSUs fail, UPS fail, case fans annoy and get shut down). With 300+ terminals it's "always something."
That's comforting to hear that you've at least seen this happen. I have convinced myself it isn't human intervention, and it's not infection. The one thing that is consistent is that all of the machines showing this behavior were rebooted on the same day, 1/13/16. But, there are also many other Win 7 Pro machines that were updated and rebooted on that date, that have not tripped over this problem.
My best guess is that this was some odd alignment of a particular flavor of NIC driver and updates kicking each other in the shins. Unless it continues, I'm pretty confident I've found and fixed all of the affected systems and I'm off to other issues. I just can't get rid of this nagging desire to want to understand why these electronic gizmos do what they do...
Many thanks for the confirmation/feedback!
Mike
Ted Roche wrote:
Hi, Mike:
Not seeing that symptom here, and web searches coming up empty, so I blame you ;)
Did you make any changes to the network that might have tripped this reaction? Maybe update a server, mess with your AD, fix a typo in the server name, domain name, take an old machine offline?
I've seen this on occasion when Windows decides I need a new network connection, despite the fact it's set up two ethernet connections and three wireless connections, all to the same LAN.
On Thu, Jan 21, 2016 at 8:29 PM, Mike Copeland mike@ggisoft.com wrote:
Thanks, Mike. Maybe I've got other gremlins in the soup...
The symptom that has been showing up is the "Set Network Location" prompt you get when you create a new network interface, where it asks you to select whether the new circuit is a Home, Public, or Work network. After making the selection, if you look at the IPV4 settings for
the NIC it shows DHCP.
I know it's most likely just a bit flipped in the registry, but this is a first in my experience.
Thanks for the feedback!
Mike Copeland
Michael Glassman wrote:
I just checked several of our manually configured Win 7 Pro systems, and all of them remain manually configured after automatically installing the updates of 1/13. Sorry.
Mike
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Mike Copeland Sent: Thursday, January 21, 2016 4:36 PM To: profoxtech@leafe.com Subject: [NF] Win 7 Update messing with network settings? Has anyone else run into this in the last few days? (like since last Tuesday) I've had 10 or 12 Windows 7 Pro systems, so far, that have had their NIC IP address settings switched from manually configured to DHCP. At first I thought it was a fluke, but I keep finding more and more systems that this has happened to. And there was a forced reboot update from MSoft last week. I'm not suggesting nefarious activity, just that I have never seen this happen before. All of the systems are locked down with Admin accounts that use a password that is not available to anyone but myself and one other person. Some of the computers are running video display systems (kiosks)...not even touched by users. The one thing they all have in common is Windows 7 pro. Anything happening like that to anyone else? Thanks! Mike Copeland
-
Michael Glassman -
Mike Copeland -
Ted Roche