[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Now cannot ping print server from second machine

On 07/05/11 16:32, Klistvud wrote:

Dne, 07. 05. 2011 15:42:16 je AG napisal(a):

On 07/05/11 14:18, Brian wrote:

On Sat 07 May 2011 at 13:34:48 +0100, AG wrote:


Is this IP change due to having changed the stanza in
/etc/network/interfaces from what was iface eth0 inet *static* to iface 
eth0 inet *dhcp* ?

Please see your other thread on connectivity. Have x as 40 and use
ifdown followed by ifup.




Thanks Brian
I had already changed that and I am back to the original problem of loosing connectivity after a reboot. 

The /etc/network/interfaces file reads (in its entirety):

auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
#iface eth0 inet dhcp ## This reflects the earlier suggestion about changing static to dhcp 
    address 192.168.1.40
    netmask 255.255.255.0
    network 192.168.1.0
    broadcast 192.168.1.255
    gateway 192.168.1.254
# dns-* options are implemented by the resolvconf package, if installed 
    dns-nameservers 158.43.240.4
    dns-search org

However, as noted - this returns full circle to the original issues.


Things to check:
IS your gateway/router REALLY at 192.168.1.254 ? An error here will lead you to a basically "unconnected" machine, probably you won't be able even to ping the hosts on your LAN or anything. IS there really a dns server at 158.43.240.4 ? An error here will only affect dns names, so you will not be able to reach, say, www.google.com; you will still be able to reach any hosts by specifying their IP numbers directly. 



Hi Klistvud
Yes, that is the gateway/ router IP address - I just checked with the provider.
Yes, the DNS address given is accurate - domain names resolve fine (once I can get connected).
This seems to be emanating from something to do with the dhcp vs. static settings which is an issue I have never run into before and has only occurred since one of the last updates. The reason I know this is because yesterday I reinstalled my system using a testing netinstall CD from February 2011 that I had. All was fine - could connect, could print, etc. However, when I ran dist-upgrade and rebooted, this is when all of the problems started again ... just as they had after I rebooted prior to the reinstall after a 9 day uptime. This is what leads me to think that some or other configuration has been changed by a package upgrade over the last week or so. But I don't know which one. 

Thanks

AG
Reply to: