Wednesday, January 2, 2019

Win10 machine wont access a network device after rebooting computer. Running ipconfig /release -> /renew makes it work again...need help, please.

So, this may be slightly convoluted but, I will do my best to be as concise as possible. There's a Win10 machine that is connected to the company network which should be connected to a USRP device, also connected to the network but, that connection doesn't work after the computer has been restarted. The work around we've found is, that if we connect the device to the computer via a gigabit to USB 2.0 adapter and run ipconfig /release and then /renew, the device works. It gets weirder...If the USRP is then unplugged and connected to the network again, it works. But, If I restart the computer back to square 1 we go. It is definitely not a device issue as it has been running on other computers for over a year and has been retested on them with no such issues. I have tried resetting the network settings in Windows. We've scoured the AV logs to see if it is getting blocked, and nothing. Another weird artifact that may be a clue is, in the IPv4 settings in the network adapter for the computer, even though the settings are set to configure automatically, the default gateway still has an address in it. I've tried deleting it, and running netsh winsock reset catalog to no avail. Any ideas what is happening? Thanks for your time!



No comments:

Post a Comment