re^2: net pblms

[ddm at mclinux.com (Derek Martin)]

On Wed, 4 Oct 2000, dan moylan wrote:

> 
> derek martin writes:
> 
> re pblm 1:
> > Oh yeah!  Seen that problem!  I think we saw it on several occasions with
> > two distinct causes...  The one that I remember was that the machine did
> > not have the routing set up properly.  The other was a mystery and I'm not
> > sure how we solved it... I think it was one of those magical problems that
> > just go away on their own.  :)
> 
> ugh!
> 
> > What is the IP address of netgear?  
> 
> 192.168.0.1 (the local box, defined as netgear.moylan.com in hosts)

Seems right.  I agree with GAF, I'd expect the duplicate entry in your
routing table would cause a problem.  I also remember seeing this...  I
can't remember how we fixed it, but once we got the extra route to stop
showing up, things started working properly.


> oddly enough, there was no inetd.conf in machine 1's /etc (and why not
> you might ask?).  perhaps that indicates something i'm missing.  i
> copied over the inetd.conf from machine 2, which did have a valid telnet
> entry but that changed nothing.

You'd need to stop and start inetd... if you didn't that should fix the
problem.  If you did, then I have no idea what the problem is.


-- 
Derek Martin
Senior System Administrator
Mission Critical Linux
martin at MissionCriticalLinux.com 

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).