VNsea: I have tried EVERYTHING

[theJesusHorse]

I have a major problem connecting to my VNC server when I am outside of my home
network, and I know a lot of other people have the same problem. All of my
router/server settings are correct. I don't think it is a problem with VNsea,
the router or the VNC server. I think it is some sort of problem with the internet
service provider. I did a few tests...

1. When connected via EDGE or an outside wifi network, I COULD NOT access my
desktop's VNC server using VNsea.

2. When my iPhone is connected to my home wifi network, and the IP address in VNsea
is set to my PC's local IP address(192.168.1.101), then I can connect with no problem.

I enlisted the help of my friend who lives in a different city and who uses a
different ISP(his is Cox, mine is Comcast). I could connect to my friend's VNC server
using VNsea on the iPhone, and he could connect to my desktop's VNC server using
UltraVNC Viewer(he doesn't have an iPhone). That tells me that both of our routers
and VNC servers are set up correctly. So that rules out the VNC servers and the
routers as causing the problem. VNsea worked perfectly when I tried to access my
friend's VNC server, so VNsea seems to be working properly on my iPhone.
The only thing left to blame is the ISP. I don't know what the issue could be, but it
seems like the problem lies there. Any input?

iPhone service provider: T-Mobile($5.99 tZones)
Home ISP: Comcast

[JoeT]

Your friend is almost certainly wrong and your router is almost certainly NOT set up to port-forward the ports that VNSea needs to your PC.

The only other thing I can think of is that you are trying to connect to IP address 192.168.1.101 while on Edge which is impossible - you'd need to connect to the external (public) IP address of your router.

[theJesusHorse]

No, my port forwarding is set up properly. Like I said, my friend was able to access my VNC server. I was on my pc watching him control the mouse cursor. So if he is able to access my server, then my router must be set up correctly.

[Tinman]

T-Zones is the issue. There are port restrictions that come with that price.

Fortunately, since you are in control of both the client and server, you can use a different port. Try 995.

VNSea format with IP address:
xxx.xxx.xxx.xxx:995

With a URL instead (i.e., for using Dyndns):
mypc@homeip.net:995

And of course configure the server to use the same port.



--
Mike

[theJesusHorse]

T-Zones is the issue. There are port restrictions that come with that price.

I don't think that T-Zones is the problem, at least not by itself. I can't connect to my desktop VNC server even when I am using wifi!(unless its my home network and I'm using local IPs)
I tried what you suggested anyway, but it didn't work.

[Tinman]

Whatever issue you have with WiFi has nothing to do with T-Zones, which does indeed restrict ports. I also don't understand why you think it is your ISP when you've already stated that a 2nd party was able to access your machine from outside the local net. If it was a Comcast issue your friend would not have been able to connect.

You've also said nothing about how you are setting up the remote connection (dynamic IP using dyndns, static IP, used latest dynamic IP, etc.).


--
Mike

[theJesusHorse]

You've also said nothing about how you are setting up the remote connection (dynamic IP using dyndns, static IP, used latest dynamic IP, etc.).

I have tried using DynDNS as well as just using my latest dynamic IP(which doesn't change often). Neither seems to work.

[theJesusHorse]

Ok, the T-Zones was the main problem, thanks Tinman. Unfortunately, changing the port didn't work, so I had to go back to the regular priced data plan...
Now I can connect to my VNC servers, but another problem has surfaced. The VNC servers tend to crash randomly. Oh well, at least the connection problem is solved!