Source
r/sysadmin•
cryohazard

Mass Winsock Resets Needed?!

Hello All,

I have an issue in a school district where a large number of machines are 'connecting' to the wireless, but only receiving a 169.x.x.x address. After a winsock reset all is good. What the hell happened to cause this? The only major change this summer was a DC was brought out of the infrastructure a little dirty, but I didn't think that would affect the clients network stack. Any thought?!

EDIT: https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/problems-connecting-to-the-internet/f121306e-fab5-411d-833f-e4490ecb8b5c

That might be playing into this.

EDIT 2: Assumptions were made that techs had rebooted. Techs assumed interns had rebooted. No one rebooted. Another set was reported and reboots were performed without winsock resets with success.

Current belief is these sets of laptops were imaged early in the summer and shut down until the students went to use them today. If that is the case, that would line up with when I had WSUS issues and it's possible these machines didn't receive the KB mentioned in the article linked above.

Posted Aug 30, 2017, 12:58 PM UTC · edited

511
OtisBSr. Sysadmin/Infosec•

How's DHCP looking? any BAD_ADDRESS entries or anything undesirable?

2
cryohazardOPSCCM Much?•

I made an "EDIT 2:" fwiw. Thanks for trying to help!

1
rowdychildren•

Note: This issue is limited to PCs running Windows 10 version 1607 that have not been restarted recently, and with network adapters unexpectedly showing an IP address in the 169.x.x.x range.

1
cryohazardOPSCCM Much?•

I made an "EDIT 2:" fwiw. Thanks for trying to help! They indeed did not restart.

1
williamp114One Man IT Department•

Could your DHCP server be running out of addresses? What's the IP range of your scope?

1
cryohazardOPSCCM Much?•

I made an "EDIT 2:" fwiw. Thanks for trying to help!

1
SengfengVMware Admin•

Had a customer laptop (HP) running 1703 that did that this week. No matter what sort of netsh resets I did, I couldn't get it working. I'd see it obtain a DHCP lease for a moment, then switch to a 169.x.x.x. Solution after 4 hours... Re-image.

1
cryohazardOPSCCM Much?•

I made an "EDIT 2:" fwiw. Thanks for trying to help!

1
usbeef•

I too have a feeling something is going on. I have had 5 or 6 corrupted Winsock's in the past few months. Both wired and wireless NICs were not able to obtain an IP address. I have been instructing remote users through a system restore which has resolved the issue. One of the machines was Windows 7.

1
cryohazardOPSCCM Much?•

I made an "EDIT 2:" fwiw. Thanks for trying to help!

1
djetaineSenior Sysadmin•

I have this too randomly on lenovo laptops. It's quite annoying because my users aren't admins so they can't do it themselves. Been happening for the past 8 months. I get about one a week.

1