| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Coder TuX said the following on 2007-04-07 14:46: |
| 5 |
| resolv.conf is -rw-r--r-- so that's not the issue.. |
| 6 |
| |
| 7 |
| I noticed that ping works for about every ip i've tried, but TCP |
| 8 |
| connexions don't. why could that happen? I can browse my local webserver |
| 9 |
| however... |
| 10 |
| |
| 11 |
I'm not entirely clear on this, so just for clarification: |
| 12 |
Have You just pinged IP addresses or IPs AND domain names as well? |
| 13 |
|
| 14 |
You pinged the address 216.239.37.99, but does it work when you ping the |
| 15 |
corresponding domain name, ie va-in-f99.google.com, or any other domain |
| 16 |
name? |
| 17 |
|
| 18 |
If not it is clearly a problem with DNS not resolving properly, so check |
| 19 |
your network configuration (/etc/conf.d/net.eth0 or whatever your file |
| 20 |
is called)! Also read the example file in the same directory - it's full |
| 21 |
of valuable info on how to set up your network config. |
| 22 |
|
| 23 |
(If DNS resolution does work, it could also be a mockup with your |
| 24 |
firewall rules. Maybe outgoing TCP is rejected or dropped, for some |
| 25 |
reason. In all fairness, this shouldn't be happening unless you have |
| 26 |
changed any rules. It's a more of an extreme possibility.) |
| 27 |
|
| 28 |
|
| 29 |
//T |
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v1.4.6 (MingW32) |
| 32 |
|
| 33 |
iD8DBQFGF6J6JDzv6DN+QUkRAqeMAJwLAsZhOe/EyfDNXYk+Ud+pHgsfbQCaA4gl |
| 34 |
kulr33wIYEXDxHZggQGs/AM= |
| 35 |
=pA7R |
| 36 |
-----END PGP SIGNATURE----- |
| 37 |
-- |
| 38 |
gentoo-user@g.o mailing list |
Archives