I don't know how it could be related, but I just experienced something and would like to know if anyone has observed the same thing. I'd also like to know if anyone has any insight into how this is related.
I have a brand new computer that has been working fine for two days, until I installed "TeraByte Drive Image Backup and Restore Suite V3.64". Within minutes of installing it, my network connection completely failed. I rebooted, and it worked for a few minutes and failed again. Since this machine also has a WiFi adapter, I enabled it to see if that would work. It did work for a few minutes, then it also failed. I rebooted again, and the wired adapter worked for a few minutes and failed. I switched to the WiFi adapter, and it also worked for a few minutes, then failed. I repeated rebooting a few more times, and the results were always the same.
Since this all began as soon as I installed "TeraByte Drive Image Backup and Restore Suite V3.64", I uninstalled it, rebooted, and my network connection has been working again for over 45 minutes, without any trouble.
Does anyone have any idea why this might have occurred? I've had previous versions of TeraByte products on my old computer, and never had it cause anything like this. It seems to be this newer version, but how? Is it phoning home and possibly sending packets that are somehow jamming up the network stack or NIC? (I've had numerous occasions where malformed print jobs were causing HP printers to stop communicating over the network, so I assume this could also happen with a network adapter on the PC side, too.)
Thanks,
Carl
Loss of Network Access
-
- Posts: 3825
- Joined: Thu May 05, 2011 10:37 pm
Re: Loss of Network Access
The short direct answer is that the drive Image Suite does not affect the network at all. Which it does not.
The longer answer, while rare (especially since Vista or later), is that adding PHYLock (or such driver) to the driver stack may require adjusting the IRPStackSize.
See https://www.terabyteunlimited.com/kb/kb ... g-phylock/
The longer answer, while rare (especially since Vista or later), is that adding PHYLock (or such driver) to the driver stack may require adjusting the IRPStackSize.
See https://www.terabyteunlimited.com/kb/kb ... g-phylock/