Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Hardware - Troubleshooting and Discussion > iPod, iPhone & iPad > Setup Mocha VNC Lite with DynDns.org for remote access??

Setup Mocha VNC Lite with DynDns.org for remote access??
Thread Tools
Dedicated MacNNer
Join Date: Jul 2007
Status: Offline
Reply With Quote
Jul 21, 2008, 07:37 AM
 
I am trying to remotely connect to my Macintosh while outside of my home network via my iPhone, using the newly released Mocha VNC Lite app released on the App Store last week...I can't seem to figure out what I am doing wrong and why I cannot get the connection to work properly, and I was hoping someone could give me a hand in figuring out what the problem might be...

I am trying to connect to my Leopard 10.5.4 desktop computer, on which I've enabled Remote Management in the Sharing System Preference Pane (not "Screen Sharing" for more technical reasons), and in the 'Computer Settings' options for Remote Management, I've entered in my chosen VNC password. +**Though I am not sure whether or not "Allow Access For All Users" has to be checked instead of what I currently have, which is "Only These Users..."+

I also have a paid account with dyndns.org with whom I've signed up for a Dynamic Domain Name Service.

I have also tried configuring my airport extreme to forward the necessary ports to my local desktop machine a couple different ways - I've tried using a random port between 30,000-50,000; and I've tried using the suggested port 5900, which is the default suggested by Mocha VNC Lite....I forwarded the ports mentioned to a static LAN IP address I've setup for computer...

...and for testing purposes, I have Leopard's firewall configured to "Allow All Incoming Connections"

Using VNC Lite, I entered in my Dynamic Domain Name into the 'VNC Server IP Address field (having tried a variety of alternate ways of doing so, such as - domainname.kicks-ass.net -- http://domainname.kicks-ass.net -- https://domainname.kicks-ass.net -- vnc://domainname.kicks-ass.net - vnc://domainname.kicks-ass.net:LAN-IP - etc.) ...and yes, name.kicks-ass.net is really one of the domain names they offer

In the VNC Server Port field I've entered in the port that I chose to forward in my airport extreme settings.

Finally I have "Mac OS Server" turned on, "Save Password" turned on, and "32-bit color mode" turned on...

Nothing I've been able to come up with has worked!!

Any suggestions would be greatly appreciated... Thanks!
     
Posting Junkie
Join Date: Nov 2000
Location: in front of my Mac
Status: Offline
Reply With Quote
Jul 21, 2008, 08:01 AM
 
It could be Mocha VNC, it could be your desktop Mac, it could be your AEBS. Try breaking the problem down.

If you let your iPhone connect to the same AEBS your desktop Mac is on (so that both are on the same subnet) and you tell Mocha to connect to desktopMacName.local, does it work? If so chances are port forwarding on your AEBS isn't set up properly. If not, either Mocha is giving you trouble or your dekstop Mac isn't set up properly.

Have you tried it with another client on the same subnet as your dekstop Mac? A MB or MBP maybe? Using JollyFastVNC or Chicken of the VNC, can you connect to desktopMacName.local? If not, your desktop mac isn't set up properly for VNC.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 02:34 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2