Not able to ping other IP

[johnarnold]

The IP's that you cant reach are on a directly connected network. As other IPs are reachable on the network, if you clear your ARP cache and turn the firewall off (temporarily!) and they still can't be reached then it's very unlikely to be a problem with your machine.

Are these devices connected through a network switch? Reboot?

[GirishSharma]

Things are changing then. Post #15 shows that .88 is not present on the network (not answering ARP requests). But post #19 shows the server is now there on the network (it has answered ARP and its MAC address is known in the ip neighbors list) although it is not answering pings. I think not answering pings is probably due to its internal firewall blocking them.

This command will enable you to easily see when the server is or is not answering ARP requests, i.e. when it is reachable at all:

arping -I enp1s0 192.168.0.88

I cannot help you resolve why the server is sometimes answering ARP and sometimes not. But again, you can verify that this is real with tcpdump in another window:

sudo tcpdump -nnt -i enp1s0 arp

Even when it is reachable, I cannot really help you with finding the printer on it. Again, use tcpdump to see if it answers when you try to locate the printer. I'm not good on windows printing protocols, I'm afraid.

Here is required output :

In 1st window :

girish@girish-OptiPlex-3050:~$ arping -I enp1s0 192.168.0.88
ARPING 192.168.0.88 from 192.168.0.86 enp1s0
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.830ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  1.181ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.982ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.792ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  1.303ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.902ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  1.085ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.903ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.771ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.882ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.985ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.992ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.978ms
Unicast reply from 192.168.0.88 [74:27:EA:07:B5:51]  0.961ms
^CSent 14 probes (1 broadcast(s))
Received 14 response(s)
girish@girish-OptiPlex-3050:~$

And, in 2nd Window :

girish@girish-OptiPlex-3050:~$ sudo tcpdump -nnt -i enp1s0 arp
[sudo] password for girish: 
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp1s0, link-type EN10MB (Ethernet), capture size 262144 bytes
ARP, Request who-has 192.168.0.108 tell 192.168.0.103, length 46
ARP, Request who-has 192.168.0.79 tell 192.168.0.76, length 46
ARP, Request who-has 192.168.0.88 (74:27:ea:07:b5:51) tell 192.168.0.86, length 28
ARP, Reply 192.168.0.88 is-at 74:27:ea:07:b5:51, length 46
ARP, Request who-has 192.168.1.135 tell 192.168.1.91, length 46
ARP, Request who-has 192.168.0.79 tell 192.168.0.76, length 46
ARP, Request who-has 192.168.0.108 tell 192.168.0.103, length 46
ARP, Request who-has 192.168.0.88 (74:27:ea:07:b5:51) tell 192.168.0.86, length 28
ARP, Reply 192.168.0.88 is-at 74:27:ea:07:b5:51, length 46
ARP, Request who-has 192.168.0.79 tell 192.168.0.76, length 46
ARP, Request who-has 192.168.0.88 (74:27:ea:07:b5:51) tell 192.168.0.86, length 28

Will you please suggest me to reconfigure networking from zero level i.e. removing, clearing current configurations by step by step, so that we may loop to the first step to see how and where is problem.

[GirishSharma]

If anyone need wireless-info.txt here it is :

https://pastebin.ubuntu.com/p/rcZXjtWV5g/

Kindly help me why I am not able to configure the printer which have ip 192.168.0.88 on a windows machine.

[johnarnold]

If everything else is working I wouldn't clear all the settings on your Ubuntu box just yet. How about changing the IP address of the printer? and Reboot it?

[guiverc]

I just saw this, and if it's already been stated - sorry.

I'd suggest upgrading your system, Ubuntu 16.04.4 was released 2018-March-1 (https://fridge.ubuntu.com/2018/03/03...-lts-released/), so your system hasn't been fully-upgraded since before that date, kernel 4.10 is EOL & isn't supported anymore as you should have upgraded to 16.04.6 and be using 4.15 kernel. I'd suggest you `full-upgrade` or `dist-upgrade your system if online.