[eluser]RogerMore[/eluser]
Hi Ed,
If after shutting off all of the matching ip and useragent stuff it still doesn't work properly, you can take a look at the following:
When using the database for sessions, CI is still leaning heavily on cookies for sessions.
CI writes a cookie for session which contains you're session id. When CI is preparing the session it will look for the cookie and tries to match a session in the db with the sesion id found in the cookie. Maybe there is something wrong with your cookies because of privacy settings in your browser.
Maybe it is an idea to setup the logging function of CI, because if there is something wrong the session library writes all sorts of stuff to the log before killing a session.
Roger