1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

VNC problem

Discussion in 'Sveasoft Firmware' started by Anomaly, Nov 22, 2004.

  1. Anomaly

    Anomaly Network Guru Member

    I set up port forwarding on my router so that I could use realVNC over the net to remote control my home machine and set the home machine on a static IP.

    It was working fine for a while but now I can't seem to get it working again. I don't know what's changed. I can still connect when I'm on my home network, just not over the net.

    The firewall on the router is disabled so that shouldn't be a problem.
    The external IP for the router has not changed so that's not it either.

    Anyone got any pointers, tips, or suggestions?
     
  2. Anomaly

    Anomaly Network Guru Member

    Well I've tracked the problem to ZoneAlarm. Seems that when I was first testing this stuff I disabled it to keep things simple and had forgotten that fact. Now it's back on and causing problems.

    If I turn it off everything works fine. I have not yet figured out how to configure it to get around this. I've added the router external IP to the trusted list and even turned off protection in the trusted list and still can't connect.

    The next thing I'm going to try (which I should have thought of earlier) is to add the routers internal IP to the trusted list.

    I will post results in the hopes that it helps someone else.
     
  3. ImprezaDude

    ImprezaDude Network Guru Member

    You need to add the IP address @ Internet you're coming from to the trusted list, otherwise it won't work.

    Regards
     
  4. Anomaly

    Anomaly Network Guru Member

    ImprezaDude,

    Please clarify that statement. Are you trying to say that whatever IP is issued to me by the AP at the remote location needs to be added to the trusted zone in ZoneAlarm?

    If that's what you are saying then I don't see how that would help me because that IP is going to be different every time.
     
  5. Anomaly

    Anomaly Network Guru Member

    Resolution

    So it turns out that the free version of ZoneAlarm was the source of the problem, it doesn't support modifying specific ports.

    I removed it and installed the pro version which does support opening specific ports, in a couple of different ways actually. So the problem is solved.

    Now I only have to find a replacement for ZoneAlarm because I don't want to have to pay for it. Right now I'm on the trail period.

    Any suggestions?
     

Share This Page