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?

Mark,

So, if I use port forwarding on my router, and add a printer to my remote workstation with the following printer address ( http://Router_Name:631/ipp/PrinterShareName ) in order to print remotely, am I putting my network at risk?

Thanks, Carl!  I'll check it out.

Sesame Client over Internet is getting disconnected if it remains idle for about 5 minutes. I know there has to be some timeout setting either for TCP-IP or UDP ports or Router firewall or software firewall on server. I am not able to find as to where do I change the setting of the timeout period. I will appreciate if someone guides me to setup longer timeout period.

Sesame client over the Internet is very fast as compared to Remote desktop or PCAnywhere. I like it a lot.

Thanks Mark.
Server End - Windows7, Linksys Router, AVG Firewall
Client End - Windows XP, Linksys Router and ZoneAlarm firewall

Sometimes Client side is used as Server and Server Side as Client depending on where I am.

Thanks Mark. I will do that and report to you the results. Router firewall will remain I guess. Is there any way to temporarily take that down? I believe that is hardware firewall.

BTW: it is likely that the problem is on the notify port, not the main port. Are you sure both ports are open through all the firewalls?

I suspect that the notify port is not open all the way through. Sesame server runs a "ping" through the notify port. If there is no activity on the main port and the ping cannot get through on the notify port (after quite a few tries), the server will disconnect the main port, under the assumption that that client is no longer actually there.

Bharat_Naik wrote on Jun 28^th, 2012 at 8:06pm:


Other than by going through every device between the client and the server and making sure all is set... check the sesame logs on the client and the server for a sesame disconnect error at the same time that the client disconnects. Look particularly for S_COM errors (communications). 510091 is especially popular if sesame's connection is timing out.

Linksys router often have a "max idle time" variable you can set in the configuration web page. I believe to turn it off, and be connected always, even when idle, you set it to 0. Setting connect on demand will not work with Sesame, in that Sesame wants a constant connection.

Bharat_Naik wrote on Jun 28^th, 2012 at 8:24pm:


510401?

That can happen if the notify port cannot be opened by Sesame, or if it has been opened but will not allow a message to pass through. Typically this would be the port on the server, though it could be at any point along the way to the client, if messages are being stopped.

Carl Underwood wrote on Jun 28^th, 2012 at 8:31pm:




I have no idea whether it is available in all connection types on all routers. But that screencap is very old. Look which browser it is. Maybe they got rid of an old feature?

Never mind, I just noticed that your firmware is from 2000! So, you obviously have a pretty old Linksys. I don't think the new ones have that feature.

Plus, I think that timeout is related to the PPPoE connection, isn't it? Because I do see a those radio buttons if I change my connection type to PPPoE, but they are not there with the "Automatic Configuration - DHCP" or "Static IP" settings.

Carl Underwood wrote on Jun 28^th, 2012 at 8:42pm:

You don't think that is related specifically to the PPPoE setting? It appears right below the PPPoE login.

Now my stupid router is not accepting my password. I was leaving the username blank and had to use password. It worked for years. Now it is asking for UserName and Password both. Thinking it might have reset to factory default, I used all combinations of admin and it still does not work. I think I will have to reset the router and open various ports and set max idle time.