Hello,

It's not likely that it is a corrupt license file. One way to verify this is to launch a local Sesame client from the server itself, 18 times. Use "-client localhost" as your connection string.

What could be happening is either garbled communication from a Sesame client, or a connection from something that isn't a Sesame client, that is trying to connect to the Server that is tying up the connection process and causing additional clients to get the "too many clients" error message. On the server computer if you launch a port monitor(like TCPview or CurrPorts) you should see 2 connections for every Sesame client. One on the 20,000 port and another on the 20,001 port. If you have an odd number, either something else is trying to connect on those ports or one of a Client's ports has been closed by external forces(firewall, timeout settings, bad NIC, etc).

-Ray