Re: another request to reach the router
ghilljr_at_satx.rr.com
Date: 04/22/05
- Previous message: kejoseph_at_hotmail.com: "Re: RedHat EL 3 Slow tar"
- In reply to: David Efflandt: "Re: another request to reach the router"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 21 Apr 2005 17:20:20 -0700
Sorry for the delayed getting back to this. I was out of town.
I appreciate your response.
>> cat of /etc/resolv.conf:
>> search 192.168.0.1
> >nameserver 20X.XXX.XXX.X0 \ Primary
> >nameserver 2XX.XX.XXX.X1 \ secondary
> >nameserver 2XX.XX.XXX.XX3 / and tertiary DNS from telecom co.
> >I read somewhere that these should not be used when assigning the IP
> >address manually so I tried taking them out and it didn't change a
> >thing!
>Your 'search' line is incorrect. If that is included at all, it
should be
>one or more domains, NOT an IP (see 'man 5 resolver').
>You do need nameserver(s). And if eth IP is manually >assigned,
>nameserver(s) have to be manually set in resolv.conf.
I removed the "search" line and left the others. Still no joy!
My man pages for resolver were just a list of system calls but I found
a good explanation at Linux-HQ.
I still don't understand how I can go through the router to other
machines and yet not be able to access the router itself? When I ping
it, I get "Host unreachable" in spite of the default route showing in
the route table???
Any more advice would be appreciated. I'm ready to try a reinstall!
THanks Gordon
- Previous message: kejoseph_at_hotmail.com: "Re: RedHat EL 3 Slow tar"
- In reply to: David Efflandt: "Re: another request to reach the router"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|