This is really NOT a Multiplicity issue but more of a compatibility one. When i have multiplicity running as my primary machine on the computer i use it as a server database. Connectivity (Sesame Database) from my other machines goes into a dead stop. Used to work fine with the previous version of Norton. Only solution i have found to date seems to be in Norton 360 settings: 1. exclude MultiplicityConfig.exe from scans and 2. remove Norton
1 Replies
1,727 Views