Completely over-engineering something simple.
December 8, 2010 12:30 PM Subscribe
TightVNC + Hamachi + Win7 Ultimate x64, what am I doing wrong?
This is supposed to be super easy, I'm sure in my haste I've just completely overlooked something. This is supposed to be as easy as installing Hamachi on both computers, both joining a private Hamachi network, installing the server on one machine and the viewer on the other.
Then, as I understand it, you "view", and connect using the server computer's Hamachi IP. As I understand it, this mitigates any need for forwarding, etc.
Am I missing something super obvious? TightVNC isn't giving me a place to enter credentials, does it do that after a successful connection?
Anyone have any experience with this?
This is supposed to be super easy, I'm sure in my haste I've just completely overlooked something. This is supposed to be as easy as installing Hamachi on both computers, both joining a private Hamachi network, installing the server on one machine and the viewer on the other.
Then, as I understand it, you "view", and connect using the server computer's Hamachi IP. As I understand it, this mitigates any need for forwarding, etc.
Am I missing something super obvious? TightVNC isn't giving me a place to enter credentials, does it do that after a successful connection?
Anyone have any experience with this?
Response by poster: Yea, I thought of that. Thanks.
posted by TomMelee at 5:26 PM on December 8, 2010
posted by TomMelee at 5:26 PM on December 8, 2010
Off hand, you need to initialize the VNC connection before you're prompted to enter a password.
Did you start up TightVNC before starting Hamachi? It's possible that TightVNC is bound to the network interfaces that were up that that time, and not to the (newer) Hamachi interface. Try bouncing TightVNC server.
posted by chengjih at 5:40 PM on December 8, 2010
Did you start up TightVNC before starting Hamachi? It's possible that TightVNC is bound to the network interfaces that were up that that time, and not to the (newer) Hamachi interface. Try bouncing TightVNC server.
posted by chengjih at 5:40 PM on December 8, 2010
Response by poster: Server shows multiple bound ip's including the hamachi ip, but that is possible. I was trying on an un managed free network, will retry with a new managed network tomorrow. Good idea, will make sure.
posted by TomMelee at 6:44 PM on December 8, 2010
posted by TomMelee at 6:44 PM on December 8, 2010
This thread is closed to new comments.
posted by ed\26h at 2:14 PM on December 8, 2010