For the past week I have been experiencing problems downloading email "unknown host:verizon..." and connecting to web sites "www.xxx.com unavailible". I generaly have to try to download emails multiple times or reload web pages several times to get the information. DSL providor is verizon.

Any suggestions?

thanks

"www.xxx.com unavailible" and "unknown host:verizon" suggest you are not connected to Verizon. Either Verizon is having problems with their service, or you have a problem with your DSL configuration.

What have your tried, as far as your configuration tools are concerned, to check/edit/correct your configuration?

So far on my side i've turned of firewall and lowered the selinux setting and unchecked the MAC box . I've ran traceroute to verizon ist test 30 hops nothing, 2 subsequent traceroutes turned up nothing for the 1st 15 hops and then connection on hop 16 @ 87ms.

BTW on the system that runs XP no problem. Just on my linux sys.

Ping returns the following:
ping www.verizon.net
PING www.verizon.net (206.46.230.37) 56(84) bytes of data.
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=1 ttl=242 time=85.3 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=2 ttl=242 time=84.7 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=3 ttl=242 time=85.9 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=4 ttl=242 time=84.3 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=5 ttl=242 time=85.2 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=6 ttl=242 time=84.4 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=7 ttl=242 time=84.8 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=8 ttl=242 time=85.0 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=9 ttl=242 time=85.9 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=10 ttl=242 time=84.8 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=11 ttl=242 time=86.2 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=12 ttl=242 time=85.9 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=13 ttl=242 time=84.6 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=14 ttl=242 time=86.7 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=15 ttl=242 time=85.0 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=16 ttl=242 time=85.1 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=17 ttl=242 time=86.7 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=18 ttl=242 time=84.4 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=19 ttl=242 time=85.6 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=20 ttl=242 time=86.2 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=21 ttl=242 time=84.7 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=22 ttl=242 time=84.6 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=23 ttl=242 time=85.0 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=24 ttl=242 time=87.2 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=25 ttl=242 time=84.8 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=26 ttl=242 time=85.6 ms
64 bytes from es.verizon.net (206.46.230.37): icmp_seq=27 ttl=242 time=85.2 ms

[1]+ Stopped ping www.verizon.net

I think I found the problem DHCPD is failing on startup. Unable to start/restart under Services.

Any suggestions?

Some providers only support ipv4 the last versions of linux install by default ipv4 and ipv6.
You can check it by using
ifconfig
You see 2 lines with an ip-address in the shape of numeric and alphanumeric address.
Just disable ipv6 support.

ipv6 is currenly disabled. DHCP is failing on start, unable to start/restart it under Services menu. Dsl provider is verizon.

could you check with
lsmod
if tulip and dmfe are active modules

I checked lsmod neither tulip or dmfe are actice mods.

I am sorry but i have no real simple solution, you could reinstall dhcp or have a look at error messages by using dmesg

If this keeps up I may have to change distro or revert to M$. !!
However currently I'm runnning Ubuntu via a live cd and have no problems with the net.

Go to Ubuntu for information, and write down the correct setup in the Networking files. Then YOU'LL have them for the Distro YOU choose in the future. Comparing the output of Ubuntu: which YOU say works < I agree> ; with the output of the faulty Distro previously, will provide valuable insight to the errors and their resolve. DHCP has different ways of getting started manually by user. "/etc/init.d/network start" and "/etc/init.d/network restart". Also try "service dhcpd restart". Try "iface eth0 inet dhcp" or similar Ethernet Device < eth1, eth2, etc. >. Using "netstat -r" and "netstat -nr" are solid tools for viewing the routing table. Http:www.wiki.com has many uses. Tutorials, previous solutions, and great descriptions for identifying, applying, and tweaking the system.