Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #88036

Download Hamachi Windows 7 64 Bit

Show all headers | View raw

workstation restarts, due to windows operating system update, environment power condition, etc, and once everything restarts, hamachi is in the "powered off" condition. Then we are screwed, because there is no remote access, and now a human being has to make a physical trip to the workstation to click on "power on".



download hamachi windows 7 64 bit

Download File https://hasbaltempho.blogspot.com/?we=2x5hR9 






So, I've figured out a way to deal with this. I wrote a windows service that monitors the logmein service and it's power on status. If either get turned off my service restarts them. So far has been working very well and ended the random shutdowns that can happen.


For some reason on a new computer that I installed Hamachi on, it seems to randomly decide not to auto-connect (aka "Power" on) and it would be offline, requiring me to press the power button on its UI. Other times it would auto-connect just fine. Apparently this is controlled via a config file some place but the fact that it isn't being consistent was something I found odd. So what I did was create a task run in Task Scheduler to execute that previous command (hamachi-2 --cli logon) set to run "At Startup", set it to run with Administrative privileges whether a user is logged in or not, and set a Condition for it to run after getting a Network Connection with the device that provides internet access. This way Hamachi is already connected to the VPN before anyone logs on (assuming the person doesn't log in fast enough to get ahead of it). From now on I won't have to deal with the randomness of it not auto-connecting or worry about its configuration set to do so.


Basically the service I wrote polls that file every so often, if it finds the state powered off, it stops the service, changes that line, and then restarts the service. It also checks to make sure the service is running and also starts it up if the service is stopped. I also keep the hamachi in "do not self update" mode...






I created a batch file that turns on hamachi and enables a network on startup. To get it to run subtletly on startup I created a shortcut to the file and changed the properties so it starts minimized.


I briefly inspected the action Hamachi is doing. From what I found there, the Hamachi service (named Hamachi2SVC, running hamachi-2.exe) seemed to actively detect the Windows logoffs and ask their server what to do; in OP's case, the server instructs the client to disconnect.

To take around this mechanism, a way is to patch the program not to check for the logoffs. For Hamachi version 2.3.0.78, changing byte 0x10122E 0x85 to 0x31 (instruction test to xor) in C:\Program Files (x86)\LogMeIn Hamachi\x64\hamachi-2.exe works as expected, though not sure about other versions.


Local results:

 Adapter configuration: OK

 Traffic test: OK

Peer results: [255-123-905]

 Adapter configuration: OK

 Traffic test: Inbound traffic blocked, check firewall settings



I have tried making inbound and outbound rules for Hamachi in my windows firewall. I have tried disabling my anti virus and firewall. I have tried allowing Hamachi to communicate through Windows Defender Firewall. I've tried disabling protection for Hamachi under Domain, Private and public profile. I've tried reinstalling Hamachi, restarting Windows and then reinstalling Hamachi. I also tried running it as an admin. Last I tried joining my phones hotspot.

I am unable to port forward due to my living situation / not allowed access to the Router and such. My friends are able to join if I host a server for whatever game it maybe, the experience is terrible, as in they appear to be 10-60 seconds behind.

I can't seem to find any solutions to my problem online after working on this all day yesterday.



I've exported my system informations and attatched it to this post.


Hamachi's outgoing ports may very well be intentionally blocked by your system administrator, and can occasionally be mistakenly blocked due to some malicious applications sharing TDP 12975, 32976 and UDP 17771. Hamachi will fall back to SSL/non-SSL TCP 443 if it is unable to use these ports. See -ports-and-protocols-does-logmein-hamachi-use for more information.


When you ping an address through hamachi, you are actually sending UDP packets to it. So if you want to know if UDP communication will work through hamachi, try to ping someone with the console (type "ping [his IP]"). If it works, then any UDP packet with he correct address should travel correctly, including the ones emitted by your gamemaker app.


Thank you for you input, I can ensure you we are not using a cracked copy of the game.

We are using hamachi because we see it as a security risk to open up ports at our routers.

But the in-game mechanisms didn't work but Hamachi did.



If we run it via the in-game mechanisms arma 3 wants to set up those ports and it can't for some reason after some research we found out that we have to change those ports so arma can use them.

Since the release of arma 3 and before that with arma 2 we always used hamachi for some time even evolve.


Fixed, the issue was caused by a stupid windows thing.

If you go to your windows settings/useraccounts/sign-in or login options and you scroll down to the last checkbox something like: "Save the status and the informations form the last known time a programm was used" and uncked it.



Here as Link:



 -10-disable-reopening-programs-after-restart-startup/1296139#1296139


->Nakama running inside virtualbox.

->VirtualBox forwards the appropriate ports to localhost (127.0.0.1).

->Me and my friend are on the same hamachi network ( already checked that a local express server works and they can see it).

->They should use my hamachi ipv4 to make a request to nakama (look at the developer console for example, just for testing or even later on sign up, log in, enter charooms, multi-player and so on).


 novabyte, I wanted to host the server from my local machine and expose it to my friend to be able to connect to it just for development purposes. Btw, Ngrok worked great! (still a bit weird that hamachi didnt work tho, probably something i missed). thank you for your reply c:


Another option would be to network the two computers as many have suggested. If both machines have access to the internet, connect them with LogMeIn Hamachi (it is free for a few computers). Once connected, Remote Desktop into the machine with printer from your own machine, transfer the original file there again using Remote Desktop and then print. I am assuming both machines are windows and that you can Remote Desktop into the machine with printer.

 35fe9a5643

Back to comp.lang.javascript | Previous | Next | Find similar | Unroll thread

Thread

Download Hamachi Windows 7 64 Bit Jenine Izaguirre <izaguirrejenine@gmail.com> - 2024-01-08 04:20 -0800

csiph-web