There could be a variety of things wrong such as Server name, Start In directories of icons, Port settings in firewalls, Incompatibility of the old version(very old in the case of 1.1.4) of Sesame with Windows 10, etc.

Let's ignore the client machines for a moment and focus just on the server computer.

Do you get any error messages when you start up the Sesame Server program on the Server?
How many Client connections does it say you are allowed?
Can you launch a Client from the Server computer?
If not can you launch a Client on the server machine if you change the arguments in the client icon from "-client Server2:20000:20001" to "-client localhost:20000:20001"?

-Ray

There is no 2.2 version of Sesame so I'm not sure what version of Sesame you actually have.

When you say "it will not point to the mapped directory.", are you referring to the Data directory of the Sesame2 folder on the C drive of the Server? That does not need to be a mapped network drive. But I think what you might be running into is an issue with the start in of the Sesame Server. If you right click on the Sesame Server icon, and bring up properties, is the Start In: set to "C:\Sesame2\Program\"? If so you will need to change that to "C:\Sesame2\" which is where the rootdirs.ini file should be located, which is what tells Sesame what directories the Sesame Server can access.

-Ray