Thank you for your answers. I was absent for a few days and couldn't follow on
this thread that I started.
My NFS/SAMBA server is in a lab with no connections to the external world and
it is just serving a few Debian development workstations. That's why I don't
care about security.
Anyway, I t
[EMAIL PROTECTED] wrote:
>
> Hello,
>
> I have Debian 2.0 in a PC with three different Ethernet interfaces, each
> interface
> in a different subnet. I notice that network daemons like telnet, ftp and NFS
> only
> work via the first interface (eth0) and completely ignore the other two
> interfa
On Tue, 1 Dec 1998 [EMAIL PROTECTED] wrote:
> The interfaces are well configured; I can ping on any of them, I have a
> custom client/server application running on the second interface and the
> routed daemon is aware of the third one. But still NFS, telnet and ftp don't
> work.
>
> The /etc/h
The interfaces are well configured; I can ping on any of them, I have a custom
client/server application running on the second interface and the routed daemon
is aware of the third one. But still NFS, telnet and ftp don't work.
The /etc/hosts.access and /etc/hosts.deny files are empty (just comm
On Mon, 30 Nov 1998 [EMAIL PROTECTED] wrote:
> Hello,
>
> I have Debian 2.0 in a PC with three different Ethernet interfaces, each
> interface in a different subnet. I notice that network daemons like
> telnet, ftp and NFS only work via the first interface (eth0) and
> completely ignore the othe
Hello,
I have Debian 2.0 in a PC with three different Ethernet interfaces, each
interface in a different subnet. I notice that network daemons like telnet, ftp
and NFS only work via the first interface (eth0) and completely ignore the
other two interfaces.
What has to be done to make them work
6 matches
Mail list logo
