20000 and 20001 are the default ports.

You will need to consider the firewall in the router and any firewalls that may be running on the server computer itself.

Just to clarify, its not a beginning port and ending port in the sense of a range of ports. It is simply two ports with different numbers. So, for example, should you use ports 20000 and 20020, Sesame will not use ports 20001 through 20019. It will just use 20000 and 20020.

Can I assign the ports to sesame to use that I know are open both in router firewall and software firewall?  I had opened up 8080, 3386, 5631 and 5632 for other software. I am not using them that much. Can I assign those ports to Sesame? How do I do that?  Do I write Port 8080 as 08080 or just 8080? I am also using LAN so, I do not want to see that interfering with LAN. I do have enough licenses, so I believe that should not be a problem.

Bharat_Naik wrote on Jun 5^th, 2012 at 9:36pm:


You will need to open those ports on both the Firewall on the router and on the server(which should already be open). Also depending on how you are set up you may also need to tell the router to forward ports 20,000 & 20,0001(or the ports you use) to your server computer. There should be a section in the Router admin page that says Port Forwarding or maybe just Forwarding where you can do this.

Bharat_Naik wrote on Jun 5^th, 2012 at 9:40pm:


You say you are not using them that much, that means you are using them some. If you assign those ports to Sesame, Sesame is going to try to handle ALL communication on those ports, which means it's going to try to answer what those other programs are asking. My advice is to just open ports 20000 and 20001 in the firewall and leave those other ports for the other programs. Also I may be wrong on this, and Mark will correct me if I am, but you should always have Sesame's second port 1 number higher than the first port, so use consecutive numbers.

-Ray

Yes, I would also love it if the Sesame client over the internet could use the Sesame server's printers

Bharat,

I assume when you mention "resources" you are talking about resources available from SBasic. Most of the "resources-in-general" that Sesame uses, are used on the server already. For example, when you open an application, you are scanning the file-system on the server, not the client, for application files.

But, SBasic usually runs in the client so that it can have access to the form from which it was invoked. We can't give SBasic free reign over resources on the server because that would allow the end user a tremendous amount of power over a computer that everyone shares. Sesame server is often invoked by someone with administrative authority over that computer. Sesame "inherits" that authority. So, should we hand SBasic that same power, it would be relatively trivial for someone to write a small mass-update that can do big damage to the server computer's file-system. This is why there are special entries in the sesame.ini file for the server just dealing with SBasic running on the server, for those rare cases (retrieve specs and mass-update-on-server) when SBasic can be run on the server.

Otherwise, you can access any resource available to the client, which may very well be the server's printer or file-system. I would not, though, recommend that you expose either to the Internet.

So, regarding printing from a remote Sesame client to a main location printer, I guess what Bharat and I are really wanting is a little client/server print server?