I don't know if this is related to the connectivity issues reported
earlier, but now when trying to print from a second machine, I am unable to.
The set up is my machine runs the CUPS print server and is directly
connected to a USB printer. I used to be able to print from the second
(client?) machine, but since this issue following a problem-riddled
reboot this is no longer possible.
I have tried to ping the server machine (192.168.1.40) from the client
machine (192.168.1.29) but cannot. I have stopped all the firewalls
(firestarter) on the *.*.*.40 machine and still no dice. The machines
are still connected via a hub and that hasn't changed since before I
rebooted.
The client machine (*.*.*.29) can access the Internet via the same hub,
but packets are being dropped when that machine tries to ping the
server. The server machine can now access the Net, and can ping the
client machine.
Any thoughts on what I should check out for?
TIA
AG
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> The set up is my machine runs the CUPS print server and is directly
> connected to a USB printer. I used to be able to print from the second
> (client?) machine, but since this issue following a problem-riddled
> reboot this is no longer possible.
CUPS has to set to accept print jobs from the LAN. But I expect you know
that.
> I have tried to ping the server machine (192.168.1.40) from the client
> machine (192.168.1.29) but cannot. I have stopped all the firewalls
> (firestarter) on the *.*.*.40 machine and still no dice. The machines
> are still connected via a hub and that hasn't changed since before I
> rebooted.
Firestarter configures the firewall. It is not the firewall itself so
stopping it would still leave firewall rules in place. I'm not very
familiar with iptables but
iptables -L
lists the current rules,
and
iptables -F
flushes the rules.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110507121858.GP13057@desktop">http://lists.debian.org/20110507121858.GP13057@desktop
05-07-2011, 12:26 PM
Klistvud
Now cannot ping print server from second machine
Dne, 07. 05. 2011 13:36:07 je AG napisal(a):
Hello (again)
I don't know if this is related to the connectivity issues reported
earlier, but now when trying to print from a second machine, I am
unable to.
The set up is my machine runs the CUPS print server and is directly
connected to a USB printer. I used to be able to print from the
second (client?) machine, but since this issue following a
problem-riddled reboot this is no longer possible.
I have tried to ping the server machine (192.168.1.40) from the
client machine (192.168.1.29) but cannot. I have stopped all the
firewalls (firestarter) on the *.*.*.40 machine and still no dice.
The machines are still connected via a hub and that hasn't changed
since before I rebooted.
The client machine (*.*.*.29) can access the Internet via the same
hub, but packets are being dropped when that machine tries to ping
the server. The server machine can now access the Net, and can ping
the client machine.
Any thoughts on what I should check out for?
The IP of your server. On the server, issue 'ifconfig' to see if it
still has the former IP (192.168.1.40).
TIA
AG
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Klistvud
http://bufferoverflow.tiddlyspot.com
Certifiable Loonix User #481801 Please reply to the list, not to
me.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1304771175.28162.0@compax">http://lists.debian.org/1304771175.28162.0@compax
05-07-2011, 12:34 PM
AG
Now cannot ping print server from second machine
On 07/05/11 13:26, Klistvud wrote:
Dne, 07. 05. 2011 13:36:07 je AG napisal(a):
Hello (again)
I don't know if this is related to the connectivity issues reported
earlier, but now when trying to print from a second machine, I am
unable to.
The set up is my machine runs the CUPS print server and is directly
connected to a USB printer. I used to be able to print from the
second (client?) machine, but since this issue following a
problem-riddled reboot this is no longer possible.
I have tried to ping the server machine (192.168.1.40) from the
client machine (192.168.1.29) but cannot. I have stopped all the
firewalls (firestarter) on the *.*.*.40 machine and still no dice.
The machines are still connected via a hub and that hasn't changed
since before I rebooted.
The client machine (*.*.*.29) can access the Internet via the same
hub, but packets are being dropped when that machine tries to ping
the server. The server machine can now access the Net, and can ping
the client machine.
Any thoughts on what I should check out for?
The IP of your server. On the server, issue 'ifconfig' to see if it
still has the former IP (192.168.1.40).
You're right! Now my IP has been changed to 192.168.1.64 !!!
I'm way confused now - this has always been set at 192.168.1.40 so how
has this been changed to *.*.*.64 and how do I ensure that the client
machine can keep track of any further changes to this IP?
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* ?
Thanks
AG
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 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.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110507131810.GR13057@desktop">http://lists.debian.org/20110507131810.GR13057@desktop
05-07-2011, 01:24 PM
Klistvud
Now cannot ping print server from second machine
Dne, 07. 05. 2011 14:34:48 je AG napisal(a):
On 07/05/11 13:26, Klistvud wrote:
Dne, 07. 05. 2011 13:36:07 je AG napisal(a):
Hello (again)
I don't know if this is related to the connectivity issues reported
earlier, but now when trying to print from a second machine, I am
unable to.
The set up is my machine runs the CUPS print server and is directly
connected to a USB printer. I used to be able to print from the
second (client?) machine, but since this issue following a
problem-riddled reboot this is no longer possible.
I have tried to ping the server machine (192.168.1.40) from the
client machine (192.168.1.29) but cannot. I have stopped all the
firewalls (firestarter) on the *.*.*.40 machine and still no dice.
The machines are still connected via a hub and that hasn't changed
since before I rebooted.
The client machine (*.*.*.29) can access the Internet via the same
hub, but packets are being dropped when that machine tries to ping
the server. The server machine can now access the Net, and can
ping the client machine.
Any thoughts on what I should check out for?
The IP of your server. On the server, issue 'ifconfig' to see if it
still has the former IP (192.168.1.40).
You're right! Now my IP has been changed to 192.168.1.64 !!!
I'm way confused now - this has always been set at 192.168.1.40 so
how has this been changed to *.*.*.64 and how do I ensure that the
client machine can keep track of any further changes to this IP?
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* ?
Absolutely yes. The new IP gets issued from the dhcp server on your LAN
now, it's not fixed (static) anymore. It's also not guaranteed to be
the same after every reboot, it will be as the dhcp server sees fit.
Thanks
AG
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Klistvud
http://bufferoverflow.tiddlyspot.com
Certifiable Loonix User #481801 Please reply to the list, not to
me.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1304774689.28162.2@compax">http://lists.debian.org/1304774689.28162.2@compax
05-07-2011, 01:31 PM
Klistvud
Now cannot ping print server from second machine
Dne, 07. 05. 2011 14:34:48 je AG napisal(a):
On 07/05/11 13:26, Klistvud wrote:
Dne, 07. 05. 2011 13:36:07 je AG napisal(a):
Hello (again)
I don't know if this is related to the connectivity issues reported
earlier, but now when trying to print from a second machine, I am
unable to.
The set up is my machine runs the CUPS print server and is directly
connected to a USB printer. I used to be able to print from the
second (client?) machine, but since this issue following a
problem-riddled reboot this is no longer possible.
I have tried to ping the server machine (192.168.1.40) from the
client machine (192.168.1.29) but cannot. I have stopped all the
firewalls (firestarter) on the *.*.*.40 machine and still no dice.
The machines are still connected via a hub and that hasn't changed
since before I rebooted.
The client machine (*.*.*.29) can access the Internet via the same
hub, but packets are being dropped when that machine tries to ping
the server. The server machine can now access the Net, and can
ping the client machine.
Any thoughts on what I should check out for?
The IP of your server. On the server, issue 'ifconfig' to see if it
still has the former IP (192.168.1.40).
You're right! Now my IP has been changed to 192.168.1.64 !!!
I'm way confused now - this has always been set at 192.168.1.40 so
how has this been changed to *.*.*.64 and how do I ensure that the
client machine can keep track of any further changes to this IP?
That'll be hard to do. DHCP is a dynamic protocol, changing IPs as it
sees fit. One way would be to revert to *static* instead of *dhcp*
(with all the related issues you had before); the other way would be to
use a IP-reservation-capable router as your dhcp server. If you use a
router to issue dhcp services, you may want to check out if there is a
way to configure IP reservation on the router configuration page. IP
reservation is a way to "lock" a given IP to a given MAC address (MAC
is a unique hardware network card identifier), ensuring your client
will get the same IP after every reboot. Not all routers have that
capability, however.
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* ?
Thanks
AG
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Klistvud
http://bufferoverflow.tiddlyspot.com
Certifiable Loonix User #481801 Please reply to the list, not to
me.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1304775099.28162.3@compax">http://lists.debian.org/1304775099.28162.3@compax
05-07-2011, 01:32 PM
AG
Now cannot ping print server from second machine
On 07/05/11 14:24, Klistvud wrote:
Dne, 07. 05. 2011 14:34:48 je AG napisal(a):
On 07/05/11 13:26, Klistvud wrote:
Dne, 07. 05. 2011 13:36:07 je AG napisal(a):
Hello (again)
I don't know if this is related to the connectivity issues reported
earlier, but now when trying to print from a second machine, I am
unable to.
The set up is my machine runs the CUPS print server and is directly
connected to a USB printer. I used to be able to print from the
second (client?) machine, but since this issue following a
problem-riddled reboot this is no longer possible.
I have tried to ping the server machine (192.168.1.40) from the
client machine (192.168.1.29) but cannot. I have stopped all the
firewalls (firestarter) on the *.*.*.40 machine and still no dice.
The machines are still connected via a hub and that hasn't changed
since before I rebooted.
The client machine (*.*.*.29) can access the Internet via the same
hub, but packets are being dropped when that machine tries to ping
the server. The server machine can now access the Net, and can
ping the client machine.
Any thoughts on what I should check out for?
The IP of your server. On the server, issue 'ifconfig' to see if it
still has the former IP (192.168.1.40).
You're right! Now my IP has been changed to 192.168.1.64 !!!
I'm way confused now - this has always been set at 192.168.1.40 so
how has this been changed to *.*.*.64 and how do I ensure that the
client machine can keep track of any further changes to this IP?
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* ?
Absolutely yes. The new IP gets issued from the dhcp server on your
LAN now, it's not fixed (static) anymore. It's also not guaranteed to
be the same after every reboot, it will be as the dhcp server sees fit.
Great! So how then can I stop dhcp from randomly assigning a new IP
address to my machine so that the client machine can see the server AND
enable my (server) machine to access the Net after a reboot?
This used to work fine - now it's borked and I don't know why or how,
nor more importantly how to put it back to how it was before the package
update that kicked in.
Cheers
AG
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
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.
--
Cheerio,
Klistvud
http://bufferoverflow.tiddlyspot.com
Certifiable Loonix User #481801 Please reply to the list, not to
me.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1304782346.28162.4@compax">http://lists.debian.org/1304782346.28162.4@compax
Now cannot ping print server from second machine
