[ubuntu-za] Printing hardy annual

Quintin van Rooyen quintin.vanrooyen at gmail.com
Tue Jun 26 09:37:21 UTC 2012


Hi Jan.

I wrote you a long explanation below, but it boils down to trying this:

Set the starting DHCP address to 10.0.0.4 on the router. It is in the
screenshot you sent me the field where the IP is 10.0.0.3, just change that
to 4 and save. Then restart both computers. PC2 SHOULD remain the same, and
PC1 should get a new IP if it is set to DHCP.

If PC1's IP does not change, you know for sure that it is not getting an IP
via DHCP.

You can also do:

ip ro sh

On pc1 and see if your gateway address is 10.0.0.2. If this is not the case
you will not get internet access with this machine.

Regards

On 26 June 2012 11:21, Jan Greeff <jan at verslank.net> wrote:

> Hi Quintin,
>
> Computer no. 1:
>
> jan at jan:~$ ip ad sh
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
> UP qlen 1000
>     link/ether e0:cb:4e:1b:90:74 brd ff:ff:ff:ff:ff:ff
>     inet 10.0.0.3/24 brd 10.0.0.255 scope global eth0
>     inet6 fe80::e2cb:4eff:fe1b:9074/64 scope link
>        valid_lft forever preferred_lft forever
>
> This seems fine, can you do:

ip ro sh

on this machine? I just want to confirm that the gateway is correct here.



>
> Computer No. 2:
>
> jan at jan-System-Product-Name:~$ ip ad sh
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
> UNKNOWN qlen 1000
>     link/ether 00:01:80:52:8e:cb brd ff:ff:ff:ff:ff:ff
>     inet 10.0.0.4/24 brd 10.0.0.255 scope global eth1
>     inet6 fe80::201:80ff:fe52:8ecb/64 scope link
>        valid_lft forever preferred_lft forever
> 3: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
>     link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
>
> If this one has internet access you can ignore it from now on.


>
> Printer:
>
> *General Information*
> Network status: Ready
> Active connection type: Wired
> URL: http://10.0.0.3
> Firmware revision: R0602FxNx
> Hostname: Juanita
> Admin. password: Set
> mDNS: Officejet 6300 series [4B2366]
>
> If you change the printer IP it will stop being available from PC no 2
until you enter the new address on your printer config. If PC1 is indeed
getting it's address from DHCP and Printer is static you might have to
change this printer IP. BUT, you can also, in the screen where you took the
screenshot, set the DHCP starting address at 10.0.0.4 and leave the printer
alone for now. Restart PC1 and 2, and they should get new IP's. (PC2 should
keep IP no 10.0.0.4 and PC1 should get 10.0.0.4+n (5, 6 etc.)


> *802.3 Wired*
> Hardware address(MAC): 001cc44b2366
> IP address: 10.0.0.3
> Subnet mask: 255.255.255.0
> Default gateway: 10.0.0.2
> Configuration source: Manual
> DNS server: 10.0.0.2
> Link configuration: 100TX - Full
> Total packets transmitted: 378
> Total packets received: 3016
>

On 26 June 2012 10:04, Quintin van Rooyen <quintin.vanrooyen at gmail.com>wrote:

> On 25 June 2012 16:41, Quintin van Rooyen <quintin.vanrooyen at gmail.com>wrote:
>
>> On 25 June 2012 15:38, Jan Greeff <jan at verslank.net> wrote:
>>
>>>
>>>
> Hi Jan.
>
> Can you do:
>
> ip ad sh
>
> On all the PC's and then also provide the full network details on the
> Printer and Router please?
>
> The subnet you mentioned (255.255.255.0) is actually the mask, and it
> indicates that you are on a /24 network. In this type of network the third
> octet of the IP addresses for the devices should be the same in order to
> communicate if you do not have a firewall with routing rules on your
> network.
>
> 10.0.0.2 and 10.0.0.4 should communicate, but 10.0.0.2 and 10.0.1.4 will
> for instance not communicate.
>
> Regards
>
>
>
>
> --
> Quintin van Rooyen
> quintin.vanrooyen at gmail.com
> The New SA Geek!
> http://g33q.co.za
>



-- 
Quintin van Rooyen
quintin.vanrooyen at gmail.com
The New SA Geek!
http://g33q.co.za
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-za/attachments/20120626/0e00c907/attachment.html>


More information about the ubuntu-za mailing list