On Wed, Mar 27, 2013 at 1:26 PM, Robert Benjamin <benjie1 at cox.net> wrote: > >>>> The reason I think this is the problem is the post where you said you >>>> could log in after a very long delay. About the only thing that can >>>> cause a very long delay is the system waiting for DNS responses on >>>> what it thinks is a working network interface. The next things >>>> needed for further diagnosis would be the output of the 'ifconfig' >>>> command after you are able to log in, and the results from 'cat >>>> /etc/resolv.conf. The first should show the IP address assigned by >>>> DHCP from the router, and the second will have the DNS nameserver >>>> address(es). >>> In the last post on the forum is the output of ifconfig. It closely >>> resembles what was shown there and stated that my output should resemble >>> the one already there in post 29 ,and it does. There was no suggestion >>> to try cat /etc/reslov.conf. Can do that from the root login. Will wait >>> til I get a reply from the forum. Plenty of suggestions from here and >>> the forum and I'll keep up with both. The delay was almost an hour BTW. >>> Thanks again. The router works perfectly fine and quickly for win 7, >>> Ubuntu 12.2 and Mint 14. >> The IP address looks like what you would get from a typical home >> router, so that's probably OK. A quick test for DNS would be the >> 'dig' command. If it quickly returns a screenfull of root >> nameservers and addresses, then DNS is not the problem. If it >> doesn't, then check what you have in your /etc/resolv.conf file. >> > dig returned a lot of root nameservers instantly. OK, never mind about DNS. And on a 2nd thought, the delays it causes would be early in the startup where sendmail/samba, etc. start. Not sure why the Gnome desktop would wait for anything. I thought all it needed was the localhost entry in /etc/hosts to satisfy the need for a hostname.. -- Les Mikesell lesmikesell at gmail.com