Testing indicates that there is no conflict between Sesame and Hamachi. OP is looking into other network configuration settings.

Is anyone else running Sesame v1.1.5 in server mode over a local network and also have Hamachi v1.0.2.2 running ?

We were having problems getting Sesame Client to talk to the Sesame Server on another PC (would not connect to server ever) and we followed all the Sesame instructions for checking the ports, specifying alternate ports, specifically instructing Windows (2003 Server in our case) to allocate specific ports for (Sesame) use and still no joy.

We were also running Hamachi v1.0.2.2 on both the Sesame Client and Sesame Server PC's and watching Active Ports to see which ports were listening or kicked into action when a call to the Sesame Server was made, and it showed that Hamachi !! was trying to handle the connecting between Sesame machines. Even if only 1 machine had Hamachi running we could not establish a Sesame connection.

When we stopped Hamachi on both the W2K3 Server and on the other PC, we had no trouble getting Sesame Client to talk to Sesame Server.

This is a big issue for us with remote access, as Hamachi is what allows us to have a simple RDP session to our work machines and we currently have to turn Hamachi off to allow Sesame to work !

Anyone else encountered this problem ?

Have not posted to the Hamachi Forum yet but will be doing so later today.

We've tried one method of "alternate ports" Bob (simply telling Sesame server and Client to use different ports but without telling W2K3 Server that the changed ports were for exclusive use) which didn't work, so we moved on to telling the W2K3 server that it was to allocate, for exclusive use, two ports for Sesame server. They were the standard 20000 and 20001.

We watched Active Ports (free program that I find quite useful) which shows all ports currently in use, whether listening, active, whatever, and at the moment we tried to access Sesame server, a single Hamachi port entry showed on 20000 for about 8-10 seconds, on the ports we had allocated for exclusive Sesame use, before disappearing and a bit later we would get the "failed to connect to server" message from Sesame on the client PC. Ports 20000 & 20001 were not showing as either "waiting" or "established connection" prior to attempting connection to the Sesame server either.

Our next step will be to change the ports from 20000/20001 to something higher, again mark them for exclusive use, and see whether Hamachi will pick up on those ports as well.

Haven't had the email response back from Hamachi Forums confirming my registration yet so have been unable to post to that forum. Haven't needed to post to them before as any query I've had has been answered by searching their posts. Not this time.

Hello SirKitry,

Open Network Connections
Click the Advanced toolbar at the top
Go to Advanced Settings
What order do the connections appear listed in the connections box?

-Ray

Ray,

The order of connections (on the W2K3 Server) is :

Server Local Area Connection
Network Connection
Hamachi
(Remote Access Connections)

Listed on 4 lines exactly as shown, on the "Adapters and Bindings" tab.

However, checked on the client PC as well and the order was :

Hamachi
Local Area Connection
(Remote Access Connections)

I have changed the order so that Local Area Connections is at the top and Hamachi is the next one down. Currently able to access Sesame from Client PC but not always 100%. About to reboot and will test access again.

Bob,

Checked the firewall situation re Windows Firewall and yes; the Windows Firewall is On, on the client PC. Some of the Exceptions entries are greyed out as they are under a Group Policy set by the login to the Domain and I cannot change those (locally, on the client PC that is. I can go to the permissions as set by GP on the W2K3 Server and alter if nec). Some of the entries in Exceptions are fully configurable on the client PC (as I have Administrator level access against my personal userid for the Domain. I rarely log in as Administrator itself on the client PC.)

I'd love to be notified if you find any basic incompatibility between hamachi and sesame.  I've been hired by a client to port their ancient Q&A dos flat database to something new and Sesame looks to be it.  Otherwise, the amount of custom programming to migrate their data would be quite ridiculous.  I was planning on using Hamachi and its wonderful and easy encryption to allow remote access to the Sesame server.  If there's an incompatibility (they'll be running Sesame 2 not 1.1) I'd like to know sooner rather than later. 

The issues, with Hamachi for us anyway is that Sesame server an client, uses the "network" adapter of hamachi not the local Network card, if you disable Hamachi and the adapter of Hamachi and then start the server version of Sesame it looks at the right network adapter for the client software also you have to disable Hamachi on the pc using the client software.

Once you have connected Sesame from the client to the server you can re enable Hamachi.

davcom-ewr wrote on Sep 21^st, 2007 at 3:31am:


I downloaded Hamachi 1.0.2.2 and I'm running it on two computers here. Hamachi is active, running and connected to a network and Sesame(1.1.5A) Server and Client both run fine on both computers with Hamachi running as well. I can even connect a third computer that is not running Hamachi to the Sesame Servers running on both machines.

The order of Network connections on both machines is

Local Area Connection
Hamachi
[Remote Access Connections]

I tried putting Hamachi first on both lists but it did not affect Sesame.

Can you ping the server computer from the client computer using a command line? What results do you get with Hamachi running and with Hamachi turned off?


-Ray

davcom-ewr wrote on Sep 24^th, 2007 at 7:09am:


No problem. If you get the situation again where you cannot connect a Sesame client to the Sesame Server that is running, One thing you can do is see if you can Ping the Client from the Server and see if you can ping the Server from the Client.

If you get a message saying that the host could not be found and to check the name and try again, then it might be a hardware problem, or possibly a Name Services problem. If you get a request timed out message then maybe have a look at firewalls and check if the IP address that it is trying to ping is the right one for the computer that you are trying to ping. Since Sesame communicates over TCP/IP, using Ping can help track down what the problem is between the computers.

-Ray