[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Tue, 05 Sep 2006 13:57:04 +0100 Neil Williams <linux@xxxxxxxxxxxxxx> wrote: > > > >> (If you're not sure, copy the contents of /etc/network/interfaces in a > >> reply.) > >> > > I don't have this file on the computer. > > I have now found /etc/sysconfig/network-scripts/ifcg-eth0 which I am told is the Mandriva version of network/interfaces. Here is a copy of the contents DEVICE=eth0 BOOTPROTO=dhcp NETMASK=255.255.255.0 ONBOOT=yes METRIC=10 MII_NOT_SUPPORTED=no USERCTL=yes IPV6INIT=no IPV6TO4INIT=no PEERDNS=yes NETMASK=255.255.255.0 DHCP_CLIENT=dhclient NEEDHOSTNAME=yes PEERDNS=yes PEERYP=no PEERNTPD=no > >> It sounds like the PC is booting with the wrong config - to the point > >> where it cannot find the network connection. Follow Robin's advice and > >> isolate *which* components of the network are still working before you > >> reboot the router. > >> As far as I can see nothing is still working, just as though I have the router switched off. Once I reboot the router everything is working OK. > > >> Also, check /etc/resolv.conf which may have been overwritten. This would > >> make it hard to locate local devices and could disable DNS resolution if > >> the local nameserver cannot be found. > >> I have now found /etc/resolve.conf which contains just one line nameserver 192.168.1.1 > > Are you running a static IP at all? > No > >> If you set your local DNS on the router, the IP address of the router > >> should be your nameserver. If you run bind on the PC, the nameserver IP > >> should be the static IP of the PC. > >> > > I don't understand all that. The router was set up for me. All I did > > was plug it in to the computer and it worked. > > Then you are probably using DHCP. It may just be that your DHCP client is barffing on startup and needs to be restarted. It may be that this > package has been updated and is now complaining about something in the > config that was previously handled. > Yes, I am using DHCP. When I go into 'Configure your computer' and look at the network section I see that the protocol is DHCP. > Try: > # /etc/init.d/dhcpd restart > (or equivalent on Mandriva) > I have searched for dhcpd - result /usr/share/doc/dhcp-common-3.0.3/contrib/dhcpd-conf-to-ldap.pl /usr/share/doc/dhcp-common-3.0.3/doc/dhcp-dynamic-dns-examples/dhcp/etc/dhcpd.conf /usr/share/setup-tool-backends/scripts/dhcpd-conf /usr/share/setup-tool-backends/scripts/dhcpd.pl /usr/lib/libDrakX/network/dhcpd.pm > Instead of rebooting the router, next time try these commands on the PC: > > # ifdown eth0 > # ifup eth0 > > It's the old GNU trick of restarting a single service instead of an > entire machine. Only Windows requires a complete restart of an entire > machine, you should avoid rebooting the router if at all possible, > especially as it does NOT appear that the router is actually the device > that has the problem. > OK, I will try that and see what happens. This time I turned off the router first, then I booted up the computer and once it was running I restarted the router. Once it had settled down I tried to download my emails and everything was fine. > -- Neil Winchurst > ============= > http://www.data-freedom.org/ > http://www.nosoftwarepatents.com/ > http://www.linux.codehelp.co.uk/ > > > -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html