Home Forums Discussions General Discussion Amazing Charts via LogMein Hamachi

How would I go about connecting a client machine to a AC server over a Hamachi network?

Information here .

I have the network shows up; I've got the remote machine pointing to AmazingCharts.xml, but when I run AC, it times out.

I must say, I tried it and got it to work, but it was excruciatingly slow.

Michael J

A classic example of why AC, as currently built, does not run well across a WAN.

LogMeIn, Remote Desktop, or similar are a superior solution as the data connection to the DB stays on the local network, and only the screen and control signals make the transit back and forth.

LogMeIn and Remote Desktop combo work pretty well. Use LogMeIn when you have computers that don't support Remote Desktop. Hamachi also costs 199/year for commercial use. LogMeIn Free on the other hand is free for commercial use.

Can you connect to other computers via Hamachi, such as opening files, etc?

The lag time is highly bandwidth dependent with Hamachi. I have business-class cable internet (40 down, 5 up) at both my home & office, and the responsiveness is very usable.

Even with upload speeds of 5 MBPS, I would still opt for Remote Desktop. You are pretty limited in transfer rates. 5 MegaBITS/second is about 0.625 MegaBYTES/second where as your standard USB flash drive copies data at about a rate of 15 MegaBYTES/second. Having operations carried out at the host computer would be a lot better, which is why I recommend RDP and LogMeIn. Hard Drives read rates are around 60-80 MegaBytes/sec With RDP and LogMeIn, it's basically streaming your screen.

I can connect via SMB to any machine on the Hamachi network; it's just that AC times out when trying to connect to the SQL server. AS to why we're trying to use it, our picky doctor here refuses to use a remote desktop program.

Speculating now:
-- a bandwidth issue (although I'm sure you would have noticed a slowdown connecting to the other computers on the office network,)
-- problem with the AC client on the outside computer. (If it's a laptop that could be brought into the office, can you connect it as a client on the actual physical network in the office?)
-- AC Utilities has not correctly reset to the AC database through the Hamachi connection to the office server, and is still looking for AC on the physical network. (Need to get Hamachi connected first, then reset connection to the AC database in Amazing Utilities, then start AC on the client and redirect to the office database via Hamachi)

Is this done on the server or the client?

Don't need to do anything on the server.

On the client that is being connected outside the office using Hamachi, I first start up Hamachi, and make sure I can "see" the AC xml file on the office server by navigating through the network, once the office network computers appear on my home computers network window. Then I open Amazing Utilities on the client computer, and reset the path to the database. Then I start Amazing Charts on the client, and when the dialog box opens asking me to find the database, I navigate through the displayed computers until I find the AC file on the server.

As to connecting/accessing remote files [other than AC db files] there are a couple of options if the user doesn't want remote desktop.

Google Apps for commercial use will give you shared editing/use of documents while making them available where-ever you have network. The up-side over Sharepoint or similar is the ease of administration/support. There is a free version with more limited capabilities.

Another choice that is not as collaborative, nor as instantaneous, but serviceable is Dropbox. There is also a free version of that.

You could Amazing Synchronizer if the doctor ever comes on site. Downloads the database when he/she leaves and synchronizes when he/she comes back. What's his problem with using RDP?

I have to echo what Sandeep and most are saying on the thread. For me, no matter how fast your connection, I do not see why you are trying to use AC over the connection. You are sending all of the data from your host server to your remote client. This is why it times out. Think of a web page that loads slowly and then multiply by a bunch. Sandeep has given you the numbers.

In order to be more helpful, we need to know what the OS are. Are you connecting to a server, etc.?

I don't see any advantage of using the AC app on the desktop and connecting via the VPN vs just using RDP, LogMeIn or GoToMyPC. It is simply much faster.

The only downside to RDP if you are not using Windows Server 2008 is that it must use port 3389. This is a very non-secure port. However, this port number can be changed.

But, unless you have RWW or Windows 2008, I would highly recommend the parent software, LogMeIn.

Why is port 3389 so insecure? I use it all the time.

JamesNT

For further reading:

http://www.windowsecurity.com/articles/Windows_Terminal_Services.html

JamesNT

I tried logmein Hamachi and AC once. I think the cable internet speed we have is the limitting factor. You are trying to control too much and there is not enough band width.

We have used Logmein free and Logmein pro for 5 years - it is almost problem free. Logmein Pro and AC works quite well, as you can print file, and transfer files quite readily. It is almost as if you were in your office. However, the computer you log on must be set to awake on command, which takes about 3 to 4 minutes to do.

Logmein free tends to kick you off faster if you are not using the terminal, and Logmein pro give you a bit more time of inactivity (like 1 patient encounter), before it kicks you off.

I have also used both LogMeIn and Hamachi frequently. I actually prefer Hamachi (with adequate bandwidth), since the AC client is actually running on my computer, rather through screen control. With LogMeIn there is sometimes a problem with screen resolution on a tablet or laptop, scrolling, and my personal opinion is that the mouse is quirky to accurately control. I have sometimes had problems printing also. Both are very useful when used in the right circumstances.

That sounds like a great setup. But, you have 40 down and I have 4 to 10 down and definitely less up. And you are probably paying less too

Pinetree,

That sounds like a good experience, similar to mine although we use RDP or RWW if you have aSBS or amy 2008 version server, this its one good place for using a server especially 2008 where with a public certificate,RDP is the most secure remote connection.

As in another thread, please turn off hibernation, sleep settings out any similar settings on your NIC card. The nominal amount of money you save is not worth the issues you are experiencing.

One word or one number, 2008

Then you should stop using it, it is only the most dangerous port on your server, use admin as your username AND password, leave 3389 open with no restricted password attempts in place and watch the SUCCESSFUL hacking begin. More details later.

That's the thing, though. My administrator password is the mathematical equation of a line. All other user passwords are at least 14 characters long. And we are using 128-bit encryption.

All of which are deterrents mentioned in that article.

JamesNT

As one tech guy says, the longer your passwords, the more likely your staff will write them on a post-it note and put it on their monitor. Random eight character passwords that are easy to remember but difficult to guess are great.

I used to do the same thing. A friend of mine who used RDP would have over 1,000 hack attempts per day, sometimes way more. His good password along with only five password attempts before a 20 minute lockout is what saved him. I told him to close port 3389, and the next day: zero attempts. Any hacker with a scanner will find 3389 every time and they know what it is behind it. You may have good passwords and lockouts, but most won't. And, why let them get to the front door anyway. Now, with 2008, it is probably the safest way to log in.

Besides, if you ever set someone up and explain for two hours the value of passwords, they will still change it to pass1234.