VNC from Router to Router

[fromb]

Is there really no one here who can at least tell my why I’m unable to get RealVNC, TightVNC and even tried PcAnywhere to work from Telkom ADSL Premium Combo at home through a Mega 100WR at the office? Using it from a dial-up through the Mega 100WR works but obvious very slow so port forwarding must be correct if I can get in from dial-up so why won’t it work from another router? PLEASE HELP!! I have now spent days trying while I’m supposed to be on leave and relaxing.

Kev

 

[willemvdm]

All the experts who have the good answers seem to be gone on holiday.

I really don't have any idea what you are talking about, so excuse me if I got the cat by the tail. As far as I know, dial-up does not imply correct port forward, because one don't do/need port forward with a dial-up connection.

What I could suggest is look at www.portforward.com (I think its like that)

If you can't come right there, try router in bridge mode. Its less secure, so make sure you got a software firewall running.

Hope that helps.

 

[ghalied]

what is the error vnc is displaying when your try to connect?

 

[fromb]

Failed to connect to server.

 

[HvRooyen]

IANA boffin, but any port in a storm, eh?
1. I assume you've already had a look at firewall rules on the local router (if any).
2. Windows firewall? Might work differently on the different interfaces. Try disabling it.
3. How about sniffing the traffic? I'm thinking something like ethereal (now wireshark).

Good luck.

 

[fromb]

Hi HVROOYEN

I've setup port forwarding on the router for VNC (5900,5800) and for PcAnywhere (5631,5632) and as said, when I try from a dial-up conection anywhere, I can get intp the PC in the office via the router in the office but just slow. Trying from home using ADSL just won't work.

Haven't even installed a firewall on the pc in the office (will do once I get the system working). The pc in the office uses Win 98.

Downloaded wireshark just now but don't have a clue how to use it or how it could help me solve my problem.

Kev

 

[bwana]

As long as you have the routers working properly - ie the correct ports are being forwarded to the correct static ip's (unless you're using bridged mode in which case the port forwarding issue is moot) - then I dont see why it shouldnt work.

 

[HvRooyen]

fromb:

It seems to me as if you have already proven that the remote system is OK. Therefore the problem should be more proximal.
1. Your local computer: Windows software firewall can block programs trying to make outbound connections. It may be activated for LAN / WLAN, but not for dialup. (Silly, but possible). Exceptions (programs allowed to connect through the firewall) may also differ. (I am assuming you use WinXP / have a software firewall on the local computer)
2. Your local router: Does it have logs or a logging option? Can you ping the remote ports via ADSL? Bridging mode has been mentioned before.
3. Not to test your remote system, but an aid to debugging: I think TightVNC server has a debugging mode which logs detailed information. It may be worthwhile installing that on the office pc, then seeing what it logs when you try to connect (my R10 says it won't even get a single connection request, as that is not where the problem is)
4. Wireshark: (I usually run it in linux, so don't ask me too much about using it under windows). It is a packet sniffer. Tell it to look at your LAN /WLAN interface, then try to create a connection. Try this a few times, then tell it to stop sniffing (the packets add up pretty quickly, making it difficult to see much - especially if you don't stop all other network activity). It should now show you a list of *all* packets that were transmitted over the network, hopefully nice and colour coded to assist you. From this you should be able to see where the connection went pear-shaped. You might want to compare this with what it sees on your dialup interface when you connect in that way, so you can see what should have happened.