unable to ping internet
Blair Wilson
I just installed solaris9 on an IBM pc server. I am having a problem
getting out to the internet. My hardware consist of Linksys 4-port
dsl/cable firewall router, Comcast Cable, two windows boxes along with the
sun box.
I can ping both windows boxes from my sun box via ip-address/ hostname. I
can ping website (espn) by ip address from the sun box. What I can't do is
ping the internet via host name or surf the web for that matter.
My resolv.conf file consist of comcast.net as my domain and comcast's dns
ip's. I have added the dns entry on the host line in the nsswitch.conf
file. Nslookup fails also.
I have done this successfully before. What am I missing here? Could I be
adding the wan nfo when I should be my lan nfo or vice-versa? ANY/ALL
suggestions are welcomed. Thanks in advance.
Blair
James C. McPherson
> I just installed solaris9 on an IBM pc server. I am having a problem
> getting out to the internet. My hardware consist of Linksys 4-port
> dsl/cable firewall router, Comcast Cable, two windows boxes along with the
> sun box.
> I can ping both windows boxes from my sun box via ip-address/ hostname. I
> can ping website (espn) by ip address from the sun box. What I can't do is
> ping the internet via host name or surf the web for that matter.
> My resolv.conf file consist of comcast.net as my domain and comcast's dns
> ip's. I have added the dns entry on the host line in the nsswitch.conf
> file. Nslookup fails also.
Blair,
Try stopping and restarting nscd with
# /etc/init.d/nscd stop ; /etc/init.d/nscd start
If that doesn't help, try a truss of an nslookup to see
what it is blocked on.
hth,
jmcp
Logan Shaw
> I just installed solaris9 on an IBM pc server. I am having a problem
> getting out to the internet. My hardware consist of Linksys 4-port
> dsl/cable firewall router, Comcast Cable, two windows boxes along with the
> sun box.
>
> I can ping both windows boxes from my sun box via ip-address/ hostname. I
> can ping website (espn) by ip address from the sun box. What I can't do is
> ping the internet via host name or surf the web for that matter.
>
> My resolv.conf file consist of comcast.net as my domain and comcast's dns
> ip's. I have added the dns entry on the host line in the nsswitch.conf
> file. Nslookup fails also.
I was going to say it sounds like you have forgotten to put your
router's IP address in /etc/defaultrouter (since you didn't
mention that step), but it sounds like that's not it since you
say you can ping a remote (not on the local LAN) web site by
IP address.
So, in this case, I would guess that you have made a syntax
error in /etc/resolv.conf or in /etc/nsswitch.conf.
Your /etc/resolv.conf should look like
nameserver 1.2.3.4
domain whatever.com
and the dns line in /etc/nsswitch.conf should look like
hosts: files dns
Or maybe you have the correct syntax in /etc/resolv.conf, but you
have put the wrong address in there, for instance you may have
transposed some digits or something.
If that doesn't answer your question, you could always try nslookup
in debug mode with something like "nslookup -d2 www.espn.com.".
That should give you info about what queries it's sending out,
responses it's getting, etc.
Hope that helps.
- Logan
Blair Wilson
My resolv.conf file looks like this:
domain comcast.net
nameserver 68.80.0.12
nameserver 68.80.0.5
I copied nsswitch.dns to nsswitch.conf, then I added dns on the hosts line.
Maybe I shouldn't have copied the nsswitch.dns file. Is there a way to
recreate a new nsswitch.conf? If I create a new file call it nsswitch.conf
with only "hosts: files dns" in it, would this be a valid nsswitch.conf
file? I also will try running nslookup in debug mode. I will be back with
the results. Again, thanks.
Blair
"Blair Wilson" <blair...@comcast.net> wrote in message
news:6YqdnYSqs5w...@comcast.com...
wassy
ping 68.80.0.12
traceroute 68.80.0.12
if either of these fails, you have other issues (routing, etc.)
This *could* be a firewall issue. nslookup uses the same underlying
stuff as ping and web surfing to do the name to address mapping.
Copy /etc/nsswitch.files to /etc/nsswitch.conf
edit /etc/nsswitch.conf and add "dns" to the hosts line.
try telnet/ping again.
Also, just for fun, do a "ifconfig -a" and check your netmask, etc.
Most often the netmask should be ffffff00, but your hub may be using something
else.
(wassy)
"Blair Wilson" <blair...@comcast.net> wrote in message news:<-Z6dnaPuwfV...@comcast.com>...
Blair Wilson
to a file, but I am having a problem getting to my windows box via ftp.
The end of the output reads" timeout, timeout, Send
Request failed". If there is a particular piece of info in output that feel
is pertinent, please let me know.
Blair
"Darren Dunham" <ddu...@redwood.taos.com> wrote in message
news:UJijc.41412$wG7....@newssvr29.news.prodigy.com...
> Blair Wilson <blair...@comcast.net> wrote:
> > Yes I can ping the dns servers.
>
> Then what happens when you try to use them for name resolution?
>
> % nslookup www.yahoo.com <dns server IP address>
> ...
>
> --
> Darren Dunham ddu...@taos.com
> Senior Technical Consultant TAOS http://www.taos.com/
> Got some Dr Pepper? San Francisco, CA bay area
> < This line left intentionally blank to confuse you. >
Blair Wilson
.0.127.in-addr.arpa, IN, PTR)
------------
SendRequest(), len 40
HEADER:
opcode = QUERY, id = 8292, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0,
additional = 0
QUESTIONS:
1.0.0.127.in-addr.arpa, type = PTR, class = IN
------------
timeout
timeout
SendRequest failed
*** Can't find server name for address 127.0.0.1: No response from
server
*** Default servers are not available
#
Blair
"Blair Wilson" <blair...@comcast.net> wrote in message
news:DdWdnW6CnYM...@comcast.com...
Logan Shaw
> Here is the output from nslookup in debug mode:
>
> .0.127.in-addr.arpa, IN, PTR)
If you are seeing this in your output it probably means that either:
(1) You are looking up 127.0.0.1 as a test of the DNS, which is
not a very good idea, or
(2) You have 127.0.0.1 as one of the nameservers listed in
/etc/resolv.conf, which isn't a good idea unless you
are running a local DNS server, which is quite unlikely,
actually.
Is either of these the case? If so, correct it and try again.
- Logan
Blair Wilson
My resolv.conf file reads like this:
domain comcast.net
nameserver xx.xx.xx.x
nameserver xx.xx.xx.xx
I can ping each nameserver. What am I doing wrong?
Blair
"Logan Shaw" <lshaw-...@austin.rr.com> wrote in message
news:s_ljc.27162$hR1....@fe2.texas.rr.com...
Blair Wilson
I should also mention, that I am using a Linksys router (befsx41).
Blair
"Logan Shaw" <lshaw-...@austin.rr.com> wrote in message
news:s_ljc.27162$hR1....@fe2.texas.rr.com...
Logan Shaw
> Logan,
>
> My resolv.conf file reads like this:
>
> domain comcast.net
> nameserver xx.xx.xx.x
> nameserver xx.xx.xx.xx
>
> I can ping each nameserver. What am I doing wrong?
You didn't exactly answer the question about whether you're
using 127.0.0.1. This is the loopback address and it's
almost definitely wrong to:
(1) use it as the nameserver
(2) put it in resolv.conf
(3) use it as a test address to look up
Obviously the computer didn't make up 127.0.0.1, so it must
be coming from somewhere.
If you have it in /etc/resolv.conf, you need to remove it
from there and replace it with an IP address that actually
has a DNS server responding on it.
Assuming that neither of those "xx.xx.xx.xx" address is
127.0.0.1, then the next step might be to trace DNS-related
packets while you do an nslookup. You should do something
like this:
step 1: run the command "snoop -r port 53" as root and leave it going
in one window
step 2: do the command "nslookup cnn.com xx.xx.xx.xx", where
"xx.xx.xx.xx" is the IP address in /etc/resolv.conf that
you can ping.
This will let you know which packets are going where and whether
they are getting responses. A normal trace would look something
like this:
1.2.3.4 -> 5.6.7.8 DNS C cnn.com. Internet Addr ?
5.6.7.8 -> 1.2.3.4 DNS R cnn.com. Internet Addr 64.236.24.12
The first line is the packet going from your local Solaris
machine (represented by 1.2.3.4) to the DNS server (represented
by 5.6.7.8). The second line is the DNS server responding
back with an IP address.
By the way, if you post the commands that you try and the
results, it's OK if you want to edit out the IP addresses,
but it would help if you replace each unique IP address
with some representative fake address and say what they
are. That way it's easier to tell what's going on in your
particular situation.
- Logan
Blair Wilson
I have 127.0.0.1 in my /etc/hosts file only. It shouldn't be there?
Blair
"Logan Shaw" <lshaw-...@austin.rr.com> wrote in message
news:wGrjc.30104$NR5....@fe1.texas.rr.com...
Logan Shaw
> I have 127.0.0.1 in my /etc/hosts file only. It shouldn't be there?
No, it SHOULD be there, but that still does not explain how it
got into the "nslookup -d2" output you posted (part of) earlier.
- Logan
Blair Wilson
there another place/file that nslookup reads?
Blair
"Logan Shaw" <lshaw-...@austin.rr.com> wrote in message
news:9rsjc.30109$NR5....@fe1.texas.rr.com...
Blair Wilson
the resolv.conf had the correct info in it, just formatted wrong. I deleted
it and recreated it using domain space domain name. I originally had tab
domain space domain name. The nameservers likewise.
Blair
"Blair Wilson" <blair...@comcast.net> wrote in message
news:6YqdnYSqs5w...@comcast.com...
Logan Shaw
> Issue resolved!
>
> the resolv.conf had the correct info in it, just formatted wrong. I deleted
> it and recreated it using domain space domain name. I originally had tab
> domain space domain name. The nameservers likewise.
This would explain the 127.0.0.1 that nslookup was using. It
searches for "nameserver"s entries in /etc/resolv.conf, but since
the tab version isn't syntactically correct, it doesn't find
anything that it considers a correct "nameserver" entry and
instead falls back to the default 127.0.0.1.
Actually, I'm surprised this was a problem. If you do a
"man resolv.conf", it specifically says that the keyword
("for example, nameserver") and the value must be
"separated by white space". And I think a tab character
should qualify as whitespace.
It's starting to sound like a bug in either the documentation
or in /usr/lib/libresolv.so.
- Logan
Blair Wilson
your help.
Blair :-)
"Logan Shaw" <lshaw-...@austin.rr.com> wrote in message
news:ynKjc.35630$Dn1....@fe2.texas.rr.com...
Sunny
Blair Wilson wrote:
> Issue resolved!
>
> the resolv.conf had the correct info in it, just formatted wrong. I deleted
> it and recreated it using domain space domain name. I originally had tab
> domain space domain name. The nameservers likewise.
>
> Blair
Sheesh!
Whitespace bugs are one of my pet peeves. I recently spent an hour
staring at a Perl program that wouldn't compile because the interpreter
claimed there were mis-matched brackets. Turned out a multi-line string
was terminated with <terminator><tab><newline>, which was not recognised
as terminating the string. This was highly frustrating because I could
see the missing bracket, but not the tab, whereas the interpreter saw
the opposite.
Rich Teer
> Whitespace bugs are one of my pet peeves. I recently spent an hour
> staring at a Perl program that wouldn't compile because the interpreter
> claimed there were mis-matched brackets. Turned out a multi-line string
> was terminated with <terminator><tab><newline>, which was not recognised
> as terminating the string. This was highly frustrating because I could
> see the missing bracket, but not the tab, whereas the interpreter saw
> the opposite.
If you use vi, use "set list" to see tabs (as ^I), and carriage
returns (as $). It's saved my sanity more than once!
--
Rich Teer, SCNA, SCSA
President,
Rite Online Inc.
Voice: +1 (250) 979-1638
URL: http://www.rite-online.net