I was told there was no outage, but I know for a fact that is not the truth.
Gateway server going back into relay mode, bouncing all over, confirmed with my ISP and Data Center there are no issue on there end. I understand that a lot of things happen between gateway servers and the LMI NOC but please at least us see where the issue is. I cannot tell C level people to just sit and wait...
Yeah I had the same issue you did and was not able to login to central either. I hate it when they don't give any responses and then later like 2 hrs or more then they post ok there was an outage, but it is now resolved. Well DUH i told you that already.
There is still something going on I am not able to connect and I am still having issues loging into central this is ridiculous. I have done all the tricks I know and still unstable right now
всем привет все комне 
I'm successfully able to connect to the remote machine and browse it's files and folders.
However all file icons in the browser have a small lock icon in the lower left corner and I cannot access them. I checked the file permissions and there's full access for Everyone, yet teh files are still locked.
What could be the problem?
Note: this does not happen wehn accessing the remote computer through physical LAN. In that case the file access works just fine.
Thank you.
After installing Hamachi network card did not get installed in windows server 2008
Windows 10 updated overnight and now peer names have warning triangles and I can't connect to any peer. All pings time out. Running [Diagnostic Tool] produces a tunnel problem only the details of which claims "VPN domain's tap device is down".
Short of uninstalling and reinstalling (which may not work anyway) how do I get functionality back? I use Hamachi in a consulting business and this is costing me money so please fix quickly.
Regards,
David Barrett.
I am doing this exact thing. Have you been able to get it working and what did it take? Thanks.
I would like to RDP thru Hamachi on Ubuntu 16 on Raspberry Pi hardware.
I downloaded and installed logmein-hamachi_2.1.0.165-1_armhf.deb on the Raspberry Pi version of Ubuntu 16.04.1 LTS
The following establishes that hamachi is installed and seems to be working...
root@TimeFlies:~# hamachi
version : 2.1.0.165
pid : 851
status : logged in
client id : 205-447-603
address : 25.73.124.220 2620:9b::1949:7cdc
nickname : TimeFlies
lmi account: acm@mendac.com
I didn't find any place to enter my Service Password, but it let me join my pre-existing Hamachi network after I gave it my Network ID and Network Login Password.
I can ping the Pi from other Hamachi clients.
I can ping other Hamachi clients from the Pi.
I can even connect to another Hamachi client on the same LAN using either the LAN address or its Hamachi address.
But I can't connect to 'Non Local' Hamachi clients via RDP.
What am I doing wrong?
At the office we are using Resilio Sync to avoid a dedicated network drive and the possibility of working remotely. Now I will be setting up an AWS server in the cloud to do syncing and running licensing servers, and I was wondering if there were some kind of recommended configuration for doing this when the server is also running Hamachi?
My guess is that the config should do this:
Anything else?
I would like to have an AWS server connected with my other coworkers computers being acessible without messing with the /etc/hosts file on each computer. How should I configure a DNS server running on AWS to be used by the other Hamachi clients, without it ruining network performance? I am a programmer so I know the bare essentials of networking, and quite comfortable with Linux, but don't know not too much about DNS configuration.
Essentially I would just like the client to lookup local (hamachi) ip-to-hostnames on the private DNS, and use the "normal" DNS (that they get from whatever router they are connected to) for everything else. I do understand that using the AWS DNS for everything would slow dns lookups generally (being further away).
Didn't work.
So my brother and I, on the same network, are trying to paly with a friend far away. The game only supports LAN/offline mode, essentially. My brother can connect to games hosted by the friend, and my brother can join games hosted by me, but I can't connect to friend's games, and he cannot connect to mine. Peer diagnosing him says we are OK and all is good, and we can all diagnose each other perfectly, as well as ping each other. But I cannot connect to games my brother or him host. Our firewalls are properly set up, as diagnosing gives us the OK. What can we do to fix this?
I'd be glad to provide more info if needed.
Correction: If I host, my brother can connect. If brother hosts, friend can connect. If friend hosts, friend can connect.
When I diagnose my friends on hamachi it always comes up with my local results as
Tunnel: OK
Local results:
Adapter configuration:
DHCP settings are invalid
Traffic test: OK
How can I make the DHCP settings valid?
Hi,
That window is an IE window, so pls check IE settings.
Also that login step can be surpassed by attaching the client from the menu and accepting it in a browser.
We use hamachi to allow access to our domain network shares, it works like a dream on our other servers although they run server 2003 and 2008.
I have it set up as a hub on server 2012 and all seems to connect fine although some users cannot access the mapped drive through hamachi. The only way we can access it is to map the drive using the hamachi ip address which is not a viable option as these users also come into the office so it would then need to be remapped each time
The server is on a private network using a 192.168 address but this is the same for one of our other office servers and the same users have no problems opening that shared drive. I have tried changing some settings within hamachi but to no avail. Any ideas?
So far, it doesn't look as if Hamachi will ever make it's way to Chrome OS natively (without using Crouton). I dislike saying this, but I would suggest looking into other products that are currently supported on Chrome OS, such as NeoRouter. I haven't tried it yet, but it seems to work good, after some configuration.