Mon Apr 29, 2019 10:45 am by Manni
Sorry, didn't saw that little text and for me this is not a hack program if you use it like ISBoxer. And as long as Innerspace is not completely reliable and I don't get another solution then this is the only other option.
So I only got answers that I should not use this name here, so here my findings for others who have trouble and for Lax for optional bugsearch...
[x] Check with Advanced Port Scanner
-> no connection via port 10101
-> no connection via changed port 1024, 4899
-> possible bug: Innerspace does not change port number until closed and restarted
[no change] ISBoxer export into innerspace (PC3)
[no change] reboot of the system (countless times, after every change)
[no change] changed port number
[no change] fixed IP instead of DHCP
[no change] changed Innerspace 42xx, 43xx, 44xx
[no change] Innerspace: Admin mode
[no change] Innerspace: compatibility mode with Win7
[no change] Last Win10-Updates removed: KB4493509 for update 1809 deinstalled (changes since EQ-patch from the Windows side despite deactivated windows updates)
[no change] disabled DHCP/router after every system got his fixed IP to avoid interference + disconnected internet
[no change] changed physical ports of the switch (to avoid possible defects/problems)
[no change] included innerspace with all access rights explicitely, activated/deactivated firefall (useless, but an idea)
[x] installed Radmin-Server and client for testing
-> works on his usual port without problem -> ergo: port/innerspace problem
[no change] used some from port scanner as marked open ports (445)
[x] rebooted "old/never updated/full of installations" Win10 system, which made trouble a year ago -> connection with Advanced Port Scanner works on 10101 and 1024
[x] rebooted "newly installed EQ-only Win10 1809" + copied/replaced to version 6336 + started Innerspace with compatibility Win7 + admin mode + exported ISBoxer-config into Innerspace
-> Advanced Port Scanner can make a remote uplink but Innerspace cannot do it on themselves...arrrrg...
[does not work] started Innerspace on other system -> wrong port numbers accessed (10101) despite configuration of all Innerspace says portnumber 1024
[does not work] restarted ISBoxer and exported to Innerspace again.... still accessing at 10101 despite all systems show 1024... arrrrg..
[does not work] rebooted Win10 again, changed Innerspace (Win7 compatibility, admin mode), restarted - still connecting to 10101 while port scanner shows 1024... arrg...
[does not work] rebooted ALL PCs again
[does not work] replaced all Innerspace to version 6336
[export works -> connect through ISB is there] exported to all PCs from ISBoxer
[does not work] loading through Innerspace -> uses port 10101 despite Advanced Port Scanner uses 1024, ISBoxer can connect, only Innerspace is unable to make what he should!
[does not work] Deinstalled Innerspace/ISBoxer, reboot Win10, fresh install of ISB/IS to latest version, export config file to IS
-> no contact from ISBoxer over the net anymore
-> not even contact via Advanced Port Monitor after fresh install is possible....arrrg....
[does not work] reboot Win10 again
[x partly] renamed fresh installed ISB/IS V64xx and renamed/replaced with folder 6336
-> Innerspace is accessible through Advanced Port Monitor again at port 1024 (all are configured like that) = PC3
-> Innerspace tested on second PC (PC2) - connect from outside through Advanced Port Monitor at 1024 ok
[not working] Innerspace starting characterset -> want to connect through that darn port 10101 again ... ARRRRRG.. never had such a sturdy piece of software
[x] Reconfiguration of all Innerspace back to port 10101
-> Connect via Advanced Port Monitor works at 10101 on PC2 and PC3
-> Connect via ISBoxer works
-> Connect via Innerspace works now -> starting character set
I don't know how long that will work but after hours of wasting time with different tries, two PCs at least start to connect.
Innerspace has some serious issues sometimes.
I am staying at moment at V6336 and avoid updating again to V64xx. Hopefully that will solve it. Never change a running system - I should have known it.
But perhaps Lax can read something out of the above tries.
Changes:
- fixed IPs, no DHCP
- compatibility: admin mode & Win7 compatibility
- Version 6336
- Port 10101
Issues with questionmarks:
- cannot change port number (e.g. to 1024, was only for testing purposes, not necessary)
- strange sporadic non-connectivity while other software packs can use different ports and can even access Innerspace directly successfully
- innerspace seems to loose sometimes some information, after export from ISB it runs for a bit of time again