Re: Slightly OT: VNC Connections
- From: Christian <deadend@xxxxxxxxxxxxxxx>
- Date: 19 May 2008 16:25:08 GMT
On Mon, 19 May 2008 15:45:04 +0100, Graham J wrote:
Is the internal IP address of your network different from the internal
address of the remote network? (i.e you can't both have 192.168.0.0 / 24
for example)
Are you sure about this? The router is usually doing NAT, why would the
LAN range matter?
From this remote location, and others, can you ping the external IP
address of your router? Beware that some ISPs block ping traffic as a
security measure.
Some routers and firewalls block ICMP too, stopping 'ping' - but by and
large it will tell you something is responding.
A couple of things cross my mind:
1) IP address correct?
2) Port correct?
3) Nothing else trying to use the same port?
4) Router set to forward VNC port or uPNP doing the job?
5) Software firewall configured OK or REALLY off (some stay active in
memory even after being disabled)
6) Able to ping IP remote IP
7) Is ISP blocking the specific port
If XP Pro on target is the OP able to connect with a simple remote
desktop (enable remote connection in target: control panel>system>[tab]
REMOTE [check] allow computers to remotely connect to this computer. May
need to forward port 3389)
Launch viewer from client [start] [run] open: mstsc [enter]
Probably not useful, but it is all I can come up with off the top of my
head.
.
- Follow-Ups:
- Re: Slightly OT: VNC Connections
- From: Graham J
- Re: Slightly OT: VNC Connections
- From: Mark Carver
- Re: Slightly OT: VNC Connections
- References:
- Slightly OT: VNC Connections
- From: Mark Carver
- Re: Slightly OT: VNC Connections
- From: Graham J
- Slightly OT: VNC Connections
- Prev by Date: Re: Cancelling my BB account - moving home & getting new one
- Next by Date: Re: Slightly OT: VNC Connections
- Previous by thread: Re: Slightly OT: VNC Connections
- Next by thread: Re: Slightly OT: VNC Connections
- Index(es):
Relevant Pages
|
