Hello i cant download hamachi its doing it in multiple programs i dont know why.
I just click on ok and nothing happens.

Hello

I have a problem when I'm trying to log in, because i can't use my Hamachi anymore without logged account. It always says "You may have started a new session in another tab or window.". I've tried everything. I was reinstalling Hamachi, turning everything off (every window, every process in backup). Please tell me how to fix that simple problem.

it seend very hard to find out how to delete an account here, seens i don't whant to be here any more, so please, suport guys, can you delete my accout??

I have a friend who wishes to connect to me over the web with an older P2P-based software. We had trouble doing this and found out he's under symmetric NAT that randomly picks an available port to talk on. We tried port-forwarding the P2P software ports, we tried DMZ, and we tried VPN tunneling to another location. After this failed, I did research on symmetric NAT and found his situation pretty hopeless. Is there a way to get Hamachi to succeed here? Just a shot in the dark. Thanks!

I've been using Hamachi on a BeagleBone Black as it's a great way to make a small portable device externally accessible. Specifically I'm using the latest ARM Beta version, logmein-hamachi_2.1.0.203-1_armhf.deb.

With hamachi running, its IP routing entries (via route command) are simply:

25.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 ham0
link-local      0.0.0.0         255.255.0.0     U     0      0        0 ham0

On a few occasions though I have had it add an additional route show up:

default         0.0.0.0         0.0.0.0         U     0      0        0 ham0

This supersedes the default internet route out the devices Ethernet connection, making it go to the Hamachi connection instead which isn't providing internet access (only a mesh network between devices). By trying to put internet communication through the Hamachi network all internet access fails, including to Hamachi servers, and so the device drops from the Hamachi network and has to be fixed by manually adding the default Ethernet route back in (route add default gw [gateway_port] eth0).

This looks like an odd bug in the current beta version. I'm not familiar enough with Linux routing to understand if there's a way I can stop this from happening, so for now I've just made a workaround script to remake my internet route if Hamachi tries to take over.

Hi Everyone

I have three computers that are using logmein hamachi at the moment. Two of them are at my home, but one of them is at my workplace which i access using remote desktop connection. Whenever I lock the screen on any of the computers or end my remote desktop connection session, the connection drops out. Is this a routing issue at my home, workplace or is this a feature with the free version of hamachi? I'm currently using the free version? To prevent this issue do i need to have the paid version of hamachi since i heard with the free version you can't run it in the background. 

Everything was going wonderfully until I upgraded two machines on my network from kernel 5.7.6 to 5.7.7 .

Rolling the kernel back solved the problem.  Looks like the new kernel breaks Hamachi.  It runs and lists members of the network.  It appears that I can login successfully  but I can't connect to other machines.  If I am running 5.7.6 it looks as if machines running 5.7.7 are not on the network.  Looks like we'll need a new release of Hamachi to fix this unless subsequent kernel releases undo whatever problem(s) have been created.

I just downloaded hamachi in order to play some games with my friends and when i start the application everything goes fine, i enter the network ID and password and then it sends me to the log in screen. Sometimes it is all white, sometimes just the left part of the text and other times it just freezes

https://imgur.com/a/sXPEx1e

My friend loses the connection upon turning on hamachi. Windows 10

Hi, I configured a network on Hamachi and I know how to chat on my PC with other PC, so I added my smartphone on the network too and I would like to know if there are any way to use the Hamachi chat on smartphone. On my PC the option to send a message apears, but on my smartphone I don't receive anything. It's a Android.

I found some LAN chat apps, but I don't know if they work with hamachi, and they ask to put a port and I don't know which network port Hamachi use.

Há algum tempo eu tenho tido esse problema com um amigo meu, toda vez que nós criamos uma rede, ele fica com a bolinha azul que ao passar o mouse mostra a mensagem "encapsulamento transmitido".

His name appears with a blue dot with that name, can someone help me?

First I live in korea, and I'm sorry for my scarce english.

I just filled in my card number and cvc code, but it declined my payment.

But I can't know what's the problem.

Can you help me?

Hello. I have problem: iam creating new worl copy ipv4 adress and open to lan world of course with connect hamachi. And my friend when paste the adress can see my world . But when he is trying to connect after joining world he see white screen and after the time he were kicked from the server . plese help

P.S. we have premium minecraft.

Context: I run a small server on Linux Manjaro 20 for a small group of friends using the free version of hamachi. Peer to Peer networking is preferable over port forwarding because my home network is rather large with a lot of devices, and the people in my house who pay for the internet don't want to give me the router access keys to enable port forwarding.

So, I installed hamachi using the Arch User Repository, built all the packages using makepkg and was able to successfully start the Hamachi Daemon, log in, create networks, and my friends are able to connect to my server. I had originally installed hamachi using the beta Debian packages as well previously with the same problems a while ago, but this is now my current setup.

Problem: After a while, my friends will lose connection to my server and get a green dot online indicator with a yellow triangle exclamation next to my hostname in the Peer to Peer network which says "relayed tunnel" when it is moused over. I have some logs associated with what I think the cause of these relays are, but I have no idea how to fix it. The logs will be at the very bottom of this post.

What I've tried as a workaround for now: Basically, I have created a python discord bot that runs on my friend's chat server which, when sent a couple commands, runs a few scripts on my computer to sudo hamachi logoff, sleep for 10 seconds, and then sudo hamachi logon. It's not a great or rather safe solution, but it fixes it temporarily for the most part, sometimes being difficult and providing random issues like "Logging In.... failed" for some reason, which prompts me to have to restart the hamachi service locally myself.

I've also tried reinstalling, recreating networks, and the like trying to get around this problems but I just can't figure out how to do this myself. Any help will be greatly appreciated.

Logs:

07.13 12:59:22.603 xhg: creating new sa ..
07.13 12:59:22.603 xhg: now have (old, cur) (6bee b4aa, 3532 a169)
07.13 12:59:22.603 xhg: completed
07.13 12:59:22.603 xhg: query of remote test versions ..
07.13 12:59:22.603 tun: servicing [243-455-703] tunnel
07.13 12:59:22.817 tun: promoting new sa
07.13 12:59:22.817 xhg: new_sa_used
07.13 12:59:22.817 xhg: completed
07.13 12:59:22.817 xhg: query of remote test versions ..
07.13 12:59:22.817 tun: servicing [243-455-703] tunnel
07.13 13:00:01.664 tun: peer 243-455-703 missed a keep-alive on 0x9deac0, zombi 1
07.13 13:00:01.664 ses:   [ON ] link 0x9e0c00, type 3, tid_o 0e82d6d7
07.13 13:00:01.664 tun: servicing [243-455-703] tunnel
07.13 13:00:08.363 tun: peer 232-839-440 missed a keep-alive on 0xa02ab0, zombi 1
07.13 13:00:08.363 ses:   [ON ] link 0xa20970, type 3, tid_o 0de0d910
07.13 13:00:08.363 tun: servicing [232-839-440] tunnel
07.13 13:00:17.528 ses:   [off] link 0xa20970, type 3, tid_o 0de0d910
07.13 13:00:17.528 tun: servicing [232-839-440] tunnel
07.13 13:00:17.528 tun: 232-839-440, sending ka because of possible rx loss, want 35, have 66
07.13 13:00:23.625 ses:   [off] link 0x9e0c00, type 3, tid_o 0e82d6d7
07.13 13:00:23.625 tun: servicing [243-455-703] tunnel
07.13 13:00:23.625 tun: 243-455-703, sending ka because of possible rx loss, want 16, have 20
07.13 13:01:06.527 tun: peer 243-455-703 missed a keep-alive on 0x9deac0, zombi 1
07.13 13:01:06.527 ses:   [ON ] link 0x9e0c00, type 3, tid_o 0e82d6d7
07.13 13:01:06.527 tun: servicing [243-455-703] tunnel
07.13 13:01:12.416 tun: peer 232-839-440 missed a keep-alive on 0xa02ab0, zombi 1
07.13 13:01:12.416 ses:   [ON ] link 0xa20970, type 3, tid_o 0de0d910
07.13 13:01:12.416 tun: servicing [232-839-440] tunnel
07.13 13:01:29.527 tun: peer 243-455-703 missed a keep-alive on 0x9deac0, zombi 2
07.13 13:01:29.527 tun: (asking server to rebuild the tunnel)
07.13 13:01:35.416 tun: peer 232-839-440 missed a keep-alive on 0xa02ab0, zombi 2
07.13 13:01:35.416 tun: (asking server to rebuild the tunnel)
07.13 13:01:52.527 tun: peer 243-455-703 missed a keep-alive on 0x9deac0, zombi 3
07.13 13:01:52.527 tun: deleting link, type 1, peer 243-455-703
07.13 13:01:52.527 dbg: link [0x9deac0] destroy
07.13 13:01:52.527 tun: servicing [243-455-703] tunnel
07.13 13:01:58.416 tun: peer 232-839-440 missed a keep-alive on 0xa02ab0, zombi 3
07.13 13:01:58.416 tun: deleting link, type 1, peer 232-839-440
07.13 13:01:58.416 dbg: link [0xa02ab0] destroy
07.13 13:01:58.416 tun: servicing [232-839-440] tunnel
07.13 13:02:22.974 ses: >> msg_h13_tun, [243-455-703], rc 1
07.13 13:02:22.974 tun: servicing [243-455-703] tunnel
07.13 13:02:22.974 ses: >> msg_h13_tun, [232-839-440], rc 1
07.13 13:02:22.974 tun: servicing [232-839-440] tunnel
07.13 13:02:23.007 dbg: >> msg_udp_ping, id 5e708341, peer 71.59.153.195:60713
07.13 13:02:23.063 ses: >> msg_udp_preq
07.13 13:02:23.063 dbg:   len 72, dst 24.225.82.27:65328, ttl 64, spi 859a54d6, rc 72, err 11
07.13 13:02:23.063 ses: >> msg_udp_preq
07.13 13:02:23.063 dbg:   len 72, dst 71.59.153.195:60713, ttl 64, spi b513ccf9, rc 72, err 11
07.13 13:02:23.156 ses: >> msg_h2_peer, [232-839-440], rc 1
07.13 13:02:23.156 dbg: link [0xa02ab0] create for tunnel [0xa0d3e8]
07.13 13:02:23.156 ses:   new link [direct udp 4ec6ec30 78ee6871]
07.13 13:02:23.157 ses:   [off] link 0xa20970, type 3, tid_o 0de0d910
07.13 13:02:23.157 ses:   [ON ] link 0xa02ab0, type 1, tid_o 4ec6ec30
07.13 13:02:23.157 tun: servicing [232-839-440] tunnel
07.13 13:02:23.491 dbg: >> msg_udp_ping, id 4246dcb3, peer 24.225.82.27:65328
07.13 13:02:23.538 ses: >> msg_h2_peer, [243-455-703], rc 1
07.13 13:02:23.538 dbg: link [0x9deac0] create for tunnel [0xa1e398]
07.13 13:02:23.539 ses:   new link [direct udp fab8246d 57bd3ffc]
07.13 13:02:23.539 ses:   [off] link 0x9e0c00, type 3, tid_o 0e82d6d7
07.13 13:02:23.539 ses:   [ON ] link 0x9deac0, type 1, tid_o fab8246d
07.13 13:02:23.539 tun: servicing [243-455-703] tunnel
07.13 13:03:10.151 tun: 232-839-440, sending ka because of possible rx loss, want 5245, have 5247
07.13 13:03:10.737 tun: 232-839-440, sending ka because of possible rx loss, want 5286, have 5290
07.13 13:03:30.493 tun: 232-839-440, sending ka because of possible rx loss, want 6926, have 6930
07.13 13:04:23.449 tun: 232-839-440, sending ka because of possible rx loss, want 13764, have 13810
07.13 13:04:28.403 tun: 232-839-440, sending ka because of possible rx loss, want 14711, have 14713
07.13 13:04:31.107 tun: 232-839-440, sending ka because of possible rx loss, want 15348, have 15350
07.13 13:05:05.809 tun: 232-839-440, sending ka because of possible rx loss, want 20486, have 20487
07.13 13:05:29.736 tun: 232-839-440, sending ka because of possible rx loss, want 26362, have 26365
07.13 13:05:52.140 tun: 232-839-440, sending ka because of possible rx loss, want 27455, have 27459
07.13 13:06:12.181 tun: 232-839-440, sending ka because of possible rx loss, want 28652, have 28654
07.13 13:06:42.622 tun: 232-839-440, sending ka because of possible rx loss, want 31038, have 31042
07.13 13:07:02.873 tun: 232-839-440, sending ka because of possible rx loss, want 32675, have 32676
07.13 13:07:22.902 tun: peer 243-455-703 missed a keep-alive on 0x9deac0, zombi 1
07.13 13:07:22.902 ses:   [ON ] link 0x9e0c00, type 3, tid_o 0e82d6d7
07.13 13:07:22.902 tun: servicing [243-455-703] tunnel
07.13 13:07:28.744 tun: peer 232-839-440 missed a keep-alive on 0xa02ab0, zombi 1
07.13 13:07:28.744 ses:   [ON ] link 0xa20970, type 3, tid_o 0de0d910
07.13 13:07:28.744 tun: servicing [232-839-440] tunnel
07.13 13:07:45.902 tun: peer 243-455-703 missed a keep-alive on 0x9deac0, zombi 2
07.13 13:07:45.902 tun: (asking server to rebuild the tunnel)
07.13 13:07:51.744 tun: peer 232-839-440 missed a keep-alive on 0xa02ab0, zombi 2
07.13 13:07:51.744 tun: (asking server to rebuild the tunnel)
07.13 13:08:08.902 tun: peer 243-455-703 missed a keep-alive on 0x9deac0, zombi 3
07.13 13:08:08.902 tun: deleting link, type 1, peer 243-455-703
07.13 13:08:08.902 dbg: link [0x9deac0] destroy
07.13 13:08:08.902 tun: servicing [243-455-703] tunnel
07.13 13:08:14.744 tun: peer 232-839-440 missed a keep-alive on 0xa02ab0, zombi 3
07.13 13:08:14.744 tun: deleting link, type 1, peer 232-839-440
07.13 13:08:14.744 dbg: link [0xa02ab0] destroy
07.13 13:08:14.744 tun: servicing [232-839-440] tunnel
07.13 13:09:26.119 tun: 218-378-392, sending ka because of possible rx loss, want 132, have 133
07.13 13:09:56.107 ipc: user bbont denied
07.13 13:10:14.204 tun: 218-378-392, sending ka because of possible rx loss, want 379, have 381
07.13 13:10:20.796 tun: 218-378-392, sending ka because of possible rx loss, want 423, have 424
07.13 13:11:58.092 ipc: 009ed480 add client 11
07.13 13:11:58.093 cfg: save()
07.13 13:11:58.095 cfg: hks: [0] [2048]
07.13 13:11:58.095 cfg: hkc: [0] [2048] [2048]
07.13 13:11:58.095 ses: go_offline, keep_tunnels 0, login_on_relaunch 0, actual state 17 ..
07.13 13:11:58.095 ses:  logout sent
07.13 13:11:58.097 dbg: del network [android1332]
07.13 13:11:58.097 tun: deleting link, type 3, peer 218-378-392
07.13 13:11:58.097 dbg: link [0xa0e0c0] destroy
07.13 13:11:58.097 tun: deleting link, type 1, peer 218-378-392
07.13 13:11:58.097 dbg: link [0xa13280] destroy
07.13 13:11:58.097 ses: set tunnel -> setup vpn peer
07.13 13:11:58.097 ses: [218-378-392], tunnel reset
07.13 13:11:58.097 dbg: del member [218-378-392] -- [mc1-15-2-1]
07.13 13:11:58.097 dbg: del peer [218-378-392]
07.13 13:11:58.097 dbg: peer [0xa1a390] destroy
07.13 13:11:58.097 dbg: link [0xa1a4c8] destroy
07.13 13:11:58.097 dbg: del member [220-048-380] -- [mc1-15-2-1]
07.13 13:11:58.097 dbg: del peer [220-048-380]
07.13 13:11:58.097 dbg: peer [0x9ec280] destroy
07.13 13:11:58.097 dbg: link [0x9ec3b8] destroy
07.13 13:11:58.097 tun: deleting link, type 3, peer 232-839-440
07.13 13:11:58.097 dbg: link [0xa20970] destroy
07.13 13:11:58.097 ses: set tunnel -> setup vpn peer
07.13 13:11:58.097 ses: [232-839-440], tunnel reset
07.13 13:11:58.097 dbg: del member [232-839-440] -- [mc1-15-2-1]
07.13 13:11:58.097 dbg: del peer [232-839-440]
07.13 13:11:58.097 dbg: peer [0xa0d2b0] destroy
07.13 13:11:58.097 dbg: link [0xa0d3e8] destroy
07.13 13:11:58.097 dbg: del member [235-209-810] -- [mc1-15-2-1]
07.13 13:11:58.097 dbg: del peer [235-209-810]
07.13 13:11:58.097 dbg: peer [0x9d16a0] destroy
07.13 13:11:58.097 dbg: link [0x9d17d8] destroy
07.13 13:11:58.098 dbg: del network [mc1-15-2-1]
07.13 13:11:58.098 dbg: del member [222-977-245] -- [mc1-15-2-2]
07.13 13:11:58.098 dbg: del peer [222-977-245]
07.13 13:11:58.098 dbg: peer [0x9f85f0] destroy
07.13 13:11:58.098 dbg: link [0x9f8728] destroy
07.13 13:11:58.098 dbg: del member [225-460-312] -- [mc1-15-2-2]
07.13 13:11:58.098 dbg: del peer [225-460-312]
07.13 13:11:58.098 dbg: peer [0xa1c450] destroy
07.13 13:11:58.098 dbg: link [0xa1c588] destroy
07.13 13:11:58.098 dbg: del member [229-782-113] -- [mc1-15-2-2]
07.13 13:11:58.098 dbg: del peer [229-782-113]
07.13 13:11:58.098 dbg: peer [0x9e47e0] destroy
07.13 13:11:58.098 dbg: link [0x9e4918] destroy
07.13 13:11:58.098 tun: deleting link, type 3, peer 243-455-703
07.13 13:11:58.098 dbg: link [0x9e0c00] destroy
07.13 13:11:58.098 ses: set tunnel -> setup vpn peer
07.13 13:11:58.098 ses: [243-455-703], tunnel reset
07.13 13:11:58.098 dbg: del member [243-455-703] -- [mc1-15-2-2]
07.13 13:11:58.098 dbg: del peer [243-455-703]
07.13 13:11:58.098 dbg: peer [0xa1e260] destroy
07.13 13:11:58.098 dbg: link [0xa1e398] destroy
07.13 13:11:58.098 dbg: del network [mc1-15-2-2]
07.13 13:11:58.098 pnp: term()
07.13 13:11:58.098 pnp: clear() ports.size=1 active.size=0 queue.size=0
07.13 13:11:58.098 pnp:   clearing UDP/41803 ..
07.13 13:11:58.098 pnp: 009f0600 new (del udp/41803)
07.13 13:11:58.098 pnp: cancel(009d40d0)
07.13 13:11:58.098 pnp: 009f0600 deleting udp/41803 ..
07.13 13:11:58.098 pnp: submitting request 009d40d0
POST /upnp/control/WANIPConnection0 HTTP/1.0
Content-Type: text/xml; charset="utf-8"
User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows 9x)
Host: 10.0.0.1:49152
Content-Length: 362
Connection: Keep-Alive
Pragma: no-cache
SOAPAction: "urn:schemas-upnp-org:service:WANIPConnection:1#DeletePortMapping"<s:Envelope    xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"    s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><meletePortMapping xmlns:m="urn:schemas-upnp-org:service:WANIPConnection:1"><NewRemoteHost></NewRemoteHost><NewExternalPort>41803</NewExternalPort><NewProtocol>UDP</NewProtocol></meletePortMapping></s:Body></s:Envelope>
------
07.13 13:11:58.098 tcp: http socket 7
07.13 13:11:58.098 pnp: cancel(009d40d0)
07.13 13:11:58.098 pnp:  1 active requests, waiting 2000 ms ..
07.13 13:11:58.136 pnp: received 00000000 response part, 503
07.13 13:11:58.136 pnp: received 00000000 response part, 503
07.13 13:11:58.136 pnp: received 00000000 response
HTTP/1.0 200 OK
CONTENT-LENGTH: 274
CONTENT-TYPE: text/xml; charset="utf-8"
DATE: Mon, 13 Jul 2020 20:11:58 GMT
EXT:
SERVER: Linux/3.14.28-Prod_18.1, UPnP/1.0, Portable SDK for UPnP devices/1.6.22
X-User-Agent: redsonic<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><ueletePortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"></ueletePortMappingResponse></s:Body> </s:Envelope>
------
07.13 13:11:58.136 pnp: 009f0600 request completed
07.13 13:11:58.136 http: delete http_io: [009cc7f0]
07.13 13:11:58.195 pnp: term() completed
07.13 13:11:58.197 ipc: 009ed480 del client
07.13 13:12:08.481 ipc: 00a10ef0 add client 12
07.13 13:12:08.481 cfg: save()
07.13 13:12:08.483 cfg: hks: [0] [2048]
07.13 13:12:08.483 cfg: hkc: [0] [2048] [2048]
07.13 13:12:08.483 sys: connmgr_go_online, reconnect 0
07.13 13:12:08.488 ses: on_conn_state(connected, 0x0)
07.13 13:12:08.488 ses: select conn mode 'dns lb'
07.13 13:12:08.488 ses: go_offline, keep_tunnels 1, login_on_relaunch 0, actual state 4 ..
07.13 13:12:08.492 sys: go_online, reconnect 0
07.13 13:12:08.494 ses: resolving hamachi-data-center.logmein-gateway.com ..
07.13 13:12:08.510 ses: resolving hamachi-list.12.logmein-gateway.com ..
07.13 13:12:08.554 ses: selected (216.219.115.12, 7236)
07.13 13:12:08.554 ses: trying last-known connection type
07.13 13:12:08.554 ses: selected 01 connection type
07.13 13:12:08.557 ses: resolving 216.219.115.12 ..
07.13 13:12:08.561 ses: connecting to 216.219.115.12:12975 ..
07.13 13:12:08.607 ses: connection is established
07.13 13:12:08.609 ses: control connection is bound to 10.0.0.243
07.13 13:12:08.609 ses: << msg_helo ..
07.13 13:12:08.660 ses: >> msg_helo, rc 1
07.13 13:12:08.669 ses: << msg_auth.pwd ..
07.13 13:12:08.858 ses: >> msg_auth, 1
07.13 13:12:08.863 ses: bound new udp sock 10 to 10.0.0.243:41566
07.13 13:12:08.863 ses: bound new icmp sock 11 to 0.0.0.0:0
07.13 13:12:08.863 pnp: init(10.0.0.243)
07.13 13:12:08.863 pnp: m-search sent
07.13 13:12:08.863 ses: upnp 1 1 0
07.13 13:12:08.863 pnp: 009f7a30 new (add udp/41566 -> 10.0.0.243:41566)
07.13 13:12:08.863 pnp: cancel(0097cfb8)
07.13 13:12:08.868 pnp: recvfrom(m-search) received 497 bytes
07.13 13:12:08.868 pnp: received 497 bytes from 10.0.0.1:51682
07.13 13:12:08.868 pnp:
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=1800
DATE: Mon, 13 Jul 2020 20:12:08 GMT
EXT:
LOCATION: http://10.0.0.1:49152/IGDdevicedesc_brlan0.xml
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 2ba6c110-c023-11ea-9ee6-b1a73d6ba099
SERVER: Linux/3.14.28-Prod_18.1, UPnP/1.0, Portable SDK for UPnP devices/1.6.22
X-User-Agent: redsonic
ST: urn:schemas-upnp-org:service:WANIPConnection:1
USN: uuid:ebf5a0a0-1dd1-11b2-a93f-3c9a77ef5136::urn:schemas-upnp-org:service:WANIPConnection:1


------
07.13 13:12:08.868 pnp: dev_addr - have 10.0.0.1, loc 10.0.0.1
07.13 13:12:08.868 pnp: m-search, device 10.0.0.1:49152, ttl 1800, schema /IGDdevicedesc_brlan0.xml
07.13 13:12:08.868 pnp: quering schema..
07.13 13:12:08.868 tcp: http socket 13
07.13 13:12:08.877 pnp: received schema/response
HTTP/1.1 200 OK
CONTENT-LENGTH: 2971
CONTENT-TYPE: text/xml
DATE: Mon, 13 Jul 2020 20:12:08 GMT
LAST-MODIFIED: Tue, 07 Jul 2020 07:26:27 GMT
SERVER: Linux/3.14.28-Prod_18.1, UPnP/1.0, Portable SDK for UPnP devices/1.6.22
X-User-Agent: redsonic
CONNECTION: close

Hello!

I'm playing BL3 with a friend on the other side of the world, cross platform, and the Shift servers are just terrible to play on. Sometime, it'll work just fine, and then suddenly some attrocious lags for the non host, and it just doesn't stop.

So we decided to try to use Hamachi to play instead, problem is, I have absolutely no idea how to configure it properly. There is a couple guides around, but I couldn't find any accurate enough for Windows 10, and even less for BL3. Is there someone around that could help me configurate it properly? I would be extremely grateful for that.

With my thanks!

So basically, I downloaded Hamachi to create a private server for me and my friends. It worked for the first 2 days, but then one of my friends had a relay tunnel issue, which I never found out how to fix. Then, after trying every single thing I could find to fix it, another issue which is even worse happened, where my IP became 0.0.0.0. I have no idea what to do, I've tried every fix given to me online, none have worked. I have reinstalled LogMeInHamachi, possibly around 25 times. Nothing has worked at all. Save me whoever owns this, all I want to do is be with my friends. 

Hi,

I have set up a gateway network with 2 computers. 1 is located is Saskatchewan, and the other in Ontario (definitely on 2 diferent isps). I can successfully access the target network, but all of the devices are under the network of 10.40.1.x where on the host side they are 192.168.1.x . When I ping a device name, my client computer successfully looks up the IP of the device, but it is of course at 192.168.1.x rather 10.40.1.x so it fails to ping. 

What could I have set up wrong? Online discussions mention that 10.40 appears when your two devices are on the same local network. That is not the case. 

On my client, the wifi uses the 192.168.1.x network, is hamachi using 10.40 to avoid a conflict? How can I resolve this?

Thanks.

Hello!

I'm playing BL3 with a friend on the other side of the world, cross platform, and the Shift servers are just terrible to play on. Sometime, it'll work just fine, and then suddenly some attrocious lags for the non host, and it just doesn't stop.

So we decided to try to use Hamachi to play instead, problem is, I have absolutely no idea how to configure it properly. There is a couple guides around, but I couldn't find any accurate enough for Windows 10, and even less for BL3. Is there someone around that could help me configurate it properly? I would be extremely grateful for that.

With my thanks!

As the title says, I can ping my friends but they can't ping me back. I'm able to join one of my friend's Minecraft server but none of my friends can join mine. Any help?

Pls help