InstallShield claims this issue is fixed with their most recent release, at least for the majority of cases. It apparently happens when you're running on a network that doesn't use Microsoft's networking software. The next release will include an updated installer that should solve it.