Linux / Windows Tightvnc Problem

I've set up tightvnc on my Linux box. A partner has tightvnc on Windows 2000.
We're coupled through a VPN, so we appear to be on a local network.

If he brings up his server, I can access it with no problem on
(his ip address):0

If I bring up my server, he can NOT access it on
(my ip address):1

I can access my own server at that address without a problem.

I have hosts.deny set to ALL: ALL

I have hosts.allow set to

#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
ALL: 127.0.0.1
ALL: 192.168.1.101
Xvnc: ALL

His ip address is 192.168.1.101

I must have left something else out. Any suggestions?

Jim
(remove not for email)

Jim wrote:
> I've set up tightvnc on my Linux box. A partner has tightvnc on Windows
> 2000. We're coupled through a VPN, so we appear to be on a local network.
>
> If he brings up his server, I can access it with no problem on
> (his ip address):0
>
> If I bring up my server, he can NOT access it on
> (my ip address):1
>
> I can access my own server at that address without a problem.
>
> I have hosts.deny set to ALL: ALL
>
> I have hosts.allow set to
>
> #
> # hosts.allow This file describes the names of the hosts which are
> #allowed to use the local INET services, as decided
> #by the '/usr/sbin/tcpd' server.
> #
> ALL: 127.0.0.1
> ALL: 192.168.1.101
> Xvnc: ALL
>
> His ip address is 192.168.1.101
>
> I must have left something else out. Any suggestions?
>
> Jim
> (remove not for email)

Your friend can try booting knoppix live CD on the windopes machine
and then see if the rdesktop utility connects to your local
machine without hassle - in which the VPN is ok, just something
in windopes - may be a default port thing or a versioning problem?

Out of interest what VPN software do you use? I was
planning on to trying out IPCop to see if it can do it ok.

7 <(E-Mail Removed)> wrote:
> Out of interest what VPN software do you use?

OpenVPN is good (and easy)
Chris

Jim <(E-Mail Removed)> wrote:
> I've set up tightvnc on my Linux box. A partner has tightvnc on Windows 2000.
> We're coupled through a VPN, so we appear to be on a local network.

> If I bring up my server, he can NOT access it on
> (my ip address):1

Can you partner do "telnet (your ip address) 5901" from a DOS box and
get a response such as "RFB 003.008"? If not, you're probably firewalled.

Chris

chris-(E-Mail Removed) wrote:
> Jim <(E-Mail Removed)> wrote:
>
>>I've set up tightvnc on my Linux box. A partner has tightvnc on Windows 2000.
>>We're coupled through a VPN, so we appear to be on a local network.
>
>
>>If I bring up my server, he can NOT access it on
>>(my ip address):1
>
>
> Can you partner do "telnet (your ip address) 5901" from a DOS box and
> get a response such as "RFB 003.008"? If not, you're probably firewalled.
>
> Chris

Or maybe the VPN just routes some kind of traffic, I've seen this
configuration already.


--

Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
(E-Mail Removed)
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÑA

The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
-- Jack Kerouac, "On the Road"

On 2004-09-05, Jim <(E-Mail Removed)> wrote:
> I've set up tightvnc on my Linux box. A partner has tightvnc on Windows 2000.
> We're coupled through a VPN, so we appear to be on a local network.
>
> If he brings up his server, I can access it with no problem on
> (his ip address):0
>
> If I bring up my server, he can NOT access it on
> (my ip address):1
>
Error messages.....?

Cheers

Alex

> I can access my own server at that address without a problem.
>
> I have hosts.deny set to ALL: ALL
>
> I have hosts.allow set to
>
> #
> # hosts.allow This file describes the names of the hosts which are
> # allowed to use the local INET services, as decided
> # by the '/usr/sbin/tcpd' server.
> #
> ALL: 127.0.0.1
> ALL: 192.168.1.101
> Xvnc: ALL
>
> His ip address is 192.168.1.101
>
> I must have left something else out. Any suggestions?
>
> Jim
> (remove not for email)
>

In article <jaau02-(E-Mail Removed)>, chris-(E-Mail Removed) says...
>
>Jim <(E-Mail Removed)> wrote:
>> I've set up tightvnc on my Linux box. A partner has tightvnc on Windows 2000.
>> We're coupled through a VPN, so we appear to be on a local network.
>
>> If I bring up my server, he can NOT access it on
>> (my ip address):1
>
>Can you partner do "telnet (your ip address) 5901" from a DOS box and
>get a response such as "RFB 003.008"? If not, you're probably firewalled.
>
>Chris

The problem indeed turned out to be related to ipchains/iptables.

The vpn is hardware based, linksys. But now it's all working ...

Thanks,
Jim