Forum :: Seose :: Forcing global save, me too.

Ok, now mines doing it..  Great..  Any info?

From what I have witnessed so far, the Forcing Global Save problem is caused by, Incorrect binding (should probably just keep at 0.0.0.0) and the exact same seose with that bind port already running when you run another. those are one I myself have witnessed although, i would imagine that portforwarding to the incorrect ip can also lead to this malfunction.

---
Former EOSERV.net Administrator.