Am Montag, 25. Dezember 2000 14:21 schrieben Sie:
> Matthias Schulz wrote:
> > But eth seems not to be able to resolve that matthschulzg is 192.168.0.1.
> > Yes it is in /etc/hosts though just as
> > 192.168.0.1 matthschulzg. Is this correct?
>
> take out the period if it is in /et
Matthias Schulz wrote:
> The only difference I can see is 192.168.0.1.1026 vs. matthschulzg.1028.
> The 1026 and 1028 are the prcessnumbers on 192.168.0.1 right? So they are
> just to ignore!?
looks like it yeah.
> But eth seems not to be able to resolve that matthschulzg is 192.168.0.1.
> Yes
Am Sonntag, 24. Dezember 2000 12:59 schrieb Nate Amsden:
> try commenting out everything in /etc/hosts.deny
>
> and putting:
>
> ALL : [EMAIL PROTECTED]
>
> in /etc/hosts.allow
Did it, no luck.
> unix/linux seems to not to like to work in an enviornment where there is
> no
> DNS resolution, or mo
try commenting out everything in /etc/hosts.deny
and putting:
ALL : [EMAIL PROTECTED]
in /etc/hosts.allow
unix/linux seems to not to like to work in an enviornment where there is
no
DNS resolution, or more specifically name resolution in general
(i imagine there isn't in your case), if you want
Hi all,
I'm still out of luck with a ethernet-connection between 2 computers.
Here are the facts: debian 2.2 Kernel, 2.2.18, Linksys ethernetcards
(one PCI, one PCMCIA) crossover cable
I can ping each other just fine.
Same machines can telnet each other or nfs-mount directories when I use the
pl
5 matches
Mail list logo