Yes and No. By default the TCP/IP protocols wait max. 30 seconds before a connection is deemed bad and needs to be closed.
Assuming you use the default TCP/IP settings Microsoft has selected for your version of Windows, you can be waiting those 30 seconds.
Now I don't know if SSC tries to connect multiple times and if so, if it does this sequentially instead of parallel. Anyway, it doesn't take genius to figure out that all those waiting times add up.
Depending on the version of Windows that you use, different TCP settings can be adjusted...but only in the registry. This is done on purpose by Microsoft and they are right about that in my view.
Only if you really know what you are doing/have intimate knowledge about the inner workings of your network gear you can adjust the configuration. Or you can use the trial-and-error method of finding the settings that work best on your particular network setup. To do that, search 'TCP settings Windows registry' on the MSDN/TechNet sites from Microsoft.
The best solution?
Either become proficient in patience or make sure you set SSC to not automatically update. Please don't take this in a bad way, it is not intended as such. Your way of working does not allow for automatic updating of SSC or any other application really.
Personally, I don't like automatic updating at all. However, I am also at piece with the consequences of this mindset. So, if you need automatic updates, remain connected to the internet all the time...after all, the NSA could get bored out of their skulls if everyone would only connect to the internet when they need to