ISB/Innerspace seems to have problems with multiple LANs
Posted: Sun Feb 02, 2020 4:09 pm
I stick to the v6336 for a long time because years ago I had only trouble with the newer version. The older have their issues too but at least I could run my 3 PC system for around 2 days until one stops working. Meanwhile two systems have an additional highspeed LAN direct connect. While unter Win10/Win7 I have now very high access between the two systems, ISB/Innercircle has now the more problems. I updated to the latest version but this makes no change. So I made my try and error. Result:
Deactivation of 2 of the 3 LAN ports: ISB recognizes the other PCs without problem
Activation at least 1 LAN with direct connect (high speed): ISB fails regularly and does not recognize each other
Activation of the standard LAN port (with no connection cable, empty slot): ISB fails from time to time, have to reboot and retry until ISB recoqnizes more PCs
Direct test via portscanners/3rd party tools show that Innerspace responds. But the ISBs of the 3 PCs do not interact in these cases.
It is really sad to deactivate all LAN ports only to get ISB communicating with the other systems.
Perhaps that will resolve also the problem that having ISB running 24/7 for around 2-3 days kicks Innerspace/ISB into "no connect mode".
Btw: extra boot system (SSD only connected for EQ), without ANY additional software, Win10 Enterprise 1896. Since around 6 months new hardware on Intel-9900KF-Basis (the same trouble). Because of the trouble years ago I simply exchange the boot SSDs to avoid any HD/SSD/M2 or other software to interfere because ISB/Innerspace/MQ2/EQBC seems highly sensitive to disturbances...
Any ideas how to solve that without disconnecting all other LAN-Ports?
Deactivation of 2 of the 3 LAN ports: ISB recognizes the other PCs without problem
Activation at least 1 LAN with direct connect (high speed): ISB fails regularly and does not recognize each other
Activation of the standard LAN port (with no connection cable, empty slot): ISB fails from time to time, have to reboot and retry until ISB recoqnizes more PCs
Direct test via portscanners/3rd party tools show that Innerspace responds. But the ISBs of the 3 PCs do not interact in these cases.
It is really sad to deactivate all LAN ports only to get ISB communicating with the other systems.
Perhaps that will resolve also the problem that having ISB running 24/7 for around 2-3 days kicks Innerspace/ISB into "no connect mode".
Btw: extra boot system (SSD only connected for EQ), without ANY additional software, Win10 Enterprise 1896. Since around 6 months new hardware on Intel-9900KF-Basis (the same trouble). Because of the trouble years ago I simply exchange the boot SSDs to avoid any HD/SSD/M2 or other software to interfere because ISB/Innerspace/MQ2/EQBC seems highly sensitive to disturbances...
Any ideas how to solve that without disconnecting all other LAN-Ports?