No ping to Suse 10.2

Hi,

I have a suse 10.2 PC running as file server in a local network. The network
goes to the internet via DSL-router. I have another local network at home
and this also goes into the internet via a DSL-router. Both routers can
connect via VPN to connect those two local networks. In the internal routing
tables of the two routers the IP adresses are translatet so that I can
access PCs from network 192.168.2.0 from the network 192.168.1.0 and vice
versa. Only the suse 10.2 server (sitting in the 192.168.1.0 network) is not
accessible from the other network. I can ping from the .2-network to every
PC in the .1-network and get answers but not to the Suse server, there is no
response. If I ping the server from within the .1-network, I get answer.
I need to access samba shares there and want to establish a NX-client
connection to the NX-server runnning on the suse 10.2 server.
So I assume that there is something wrong with the network configuration or
the firewall at the suse 10.2 server. But what and where?
Thanks for any help.

Klemens

--

Klemens Lichter wrote:

> Hi,
>
> I have a suse 10.2 PC running as file server in a local network. The
> network goes to the internet via DSL-router. I have another local network
> at home and this also goes into the internet via a DSL-router. Both
> routers can connect via VPN to connect those two local networks. In the
> internal routing tables of the two routers the IP adresses are translatet
> so that I can access PCs from network 192.168.2.0 from the network
> 192.168.1.0 and vice versa. Only the suse 10.2 server (sitting in the
> 192.168.1.0 network) is not accessible from the other network. I can ping
> from the .2-network to every PC in the .1-network and get answers but not
> to the Suse server, there is no response. If I ping the server from within
> the .1-network, I get answer. I need to access samba shares there and want
> to establish a NX-client connection to the NX-server runnning on the suse
> 10.2 server. So I assume that there is something wrong with the network
> configuration or the firewall at the suse 10.2 server. But what and where?
> Thanks for any help.
>
> Klemens
>
> --

Hi Klemens, whats the output of "netstat -r" on the not accessible box?

Markus

--
Markus

I´m not in the office at the moment, will check in 3 days.
Thank you
Klemens
"Markus Reichl" <markus@knopfi.at> schrieb im Newsbeitrag
news:h6%Yi.3650$7U6.1381@kovat.provo.novell.com...
> Klemens Lichter wrote:
>
>> Hi,
>>
>> I have a suse 10.2 PC running as file server in a local network. The
>> network goes to the internet via DSL-router. I have another local network
>> at home and this also goes into the internet via a DSL-router. Both
>> routers can connect via VPN to connect those two local networks. In the
>> internal routing tables of the two routers the IP adresses are translatet
>> so that I can access PCs from network 192.168.2.0 from the network
>> 192.168.1.0 and vice versa. Only the suse 10.2 server (sitting in the
>> 192.168.1.0 network) is not accessible from the other network. I can ping
>> from the .2-network to every PC in the .1-network and get answers but not
>> to the Suse server, there is no response. If I ping the server from
>> within
>> the .1-network, I get answer. I need to access samba shares there and
>> want
>> to establish a NX-client connection to the NX-server runnning on the suse
>> 10.2 server. So I assume that there is something wrong with the network
>> configuration or the firewall at the suse 10.2 server. But what and
>> where?
>> Thanks for any help.
>>
>> Klemens
>>
>> --
>
> Hi Klemens, whats the output of "netstat -r" on the not accessible box?
>
> Markus
>
> --
> Markus