btw disabling neoshare protocol and disabling neoshare on each file is making the whole thing more stable, for me atleast. i'm smoothly running 24/24 7/7 a.k.a intensive use. cheers.
ps: even if enabled neoshare is not working, so...
im running nl in the same way(24/24 7/7), there are no troubles but the 3 cases i listed in the previous post + 1 i just noticed while downloading a torrent folder with a lot of miedum/small files, with ed2k global option share automatically on, core got unstable (massively - i couldnt even change s...
the problem here (in my pc) it's not something new... here, i get firewalled each time core get busy for a long time, since when core is frozen for too long nl seems to move both tcp and udp ports to set port +1, those ports are not opened in my router=firewalled. here core geet often busy for sever...
i sometimes have ed2k firewalled due to neokad (moment of crazy usage of resources) core freezes and mulekad get firewalled, i usually fix this by killing both neokad and mulekad processes in task manager. otherwise close NL, check taskmanager for all NL related process to fade and restart, because ...
If NeoShare is on, it seems that getting into the summary starts a chain of failed nodes lookups (like letting a neokad search open), then a neokad disconnection followed by mulekad disconnection. I could only restart NL to fix it. NL to NL: there is no file transfer between myNLHome and myNLOffice(...
you maybe misunderstood last sentence. im not sure... i meant as long my nl is the ONLY complete source, the "tickets" won't decrease even in case of 5k requests.