Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 25

Thread: Not able to ping other IP

  1. #11
    Join Date
    May 2010
    Beans
    92

    Re: Not able to ping other IP

    Quote Originally Posted by The Cog View Post
    That is good info.

    The ip neighbor stuff tells us a lot:
    192.168.0.87 dev enp1s0 lladdr 74:27:ea:07:b5:57 STALE
    This tells us that 192.168.0.87 exists, and is able to communicate with you. I assume that since you cannot ping it, it has a firewall blocking pings. But it is there.
    192.168.0.1 dev enp1s0 FAILED
    This tells us that we have no communication with 192.168.0.1. It is probably not on the network at all. Another common address to give to routers that you could try is the last valid address - 192.168.0.254. As this is your default gateway, you are not going to be able to communicate with anything that is not on the local network. It is also possible that there is another device on the network with your IP address 192.168.0.86 and that the gateway is sending its replies to that address instead of to you.

    I don't see anything in the firewall rules that might be interfering, although you may want to disable ufw for a short while to be sure - ufw makes a right tangled mess of iptables rules that is difficult to follow.

    In your tcpdump, I can see you are sending ping requests to 192.168.0.87 but not getting any reply. This fits with the idea that its firewall is dropping pings.
    I don't see any arp requests for 192.168.0.1 in the tcpdump output, but I am guessing that you just didn't happen to post that bit of the trace.

    Back to the original problem: Is 192.168.0.87 the windows box with the printer? Do you know what protocol you are trying to use to contact the printer with?
    I'm not good with windows networking - can anyone tell you what port number you need to use to talk to the printer?
    The output of previous post given by this PC which have its own IP 192.168.0.86. As you mentioned "As this is your default gateway, you are not going to be able to communicate with anything that is not on the local network." Then how do I will be able to configure the printer which have ip of 192.168.0.88 on a windows machine. This is the main question please.

    Edit Post :

    "I don't see any arp requests for 192.168.0.1 in the tcpdump output, but I am guessing that you just didn't happen to post that bit of the trace."

    Yes, I just posted the lines which have 192.168.0.87 ip, but at that time I was pinging 192.168.0.1 too, and here it is that trace dump :
    ARP, Request who-has 192.168.0.1 tell 192.168.0.91, length 46
    ARP, Request who-has 192.168.0.1 tell 192.168.0.86, length 28
    ARP, Request who-has 192.168.0.1 tell 192.168.0.86, length 28

    etc. lines.
    Code:
    
    
    Last edited by GirishSharma; 1 Week Ago at 12:23 PM.

  2. #12
    Join Date
    Nov 2019
    Location
    London, UK
    Beans
    17

    Re: Not able to ping other IP

    If the printer has an IP of 192.168.0.88 then it is on your local network - your default gateway is only used for subnets that are not directly connected.

  3. #13
    Join Date
    Nov 2008
    Location
    Metro Boston
    Beans
    14,502
    Distro
    Kubuntu Development Release

    Re: Not able to ping other IP

    So it seems like the real issue is installing the printer, not necessarily pinging certain IPs. Have you tried going to http://localhost:631/ and letting CUPS search for the printer?
    If you ask for help, do not abandon your request. Please have the courtesy to check for responses and thank the people who helped you.

    Blog · Linode System Administration Guides · Android Apps for Ubuntu Users

  4. #14
    Join Date
    Nov 2007
    Location
    London, England
    Beans
    6,820
    Distro
    Xubuntu 19.10 Eoan Ermine

    Re: Not able to ping other IP

    With a subnet mask of 255.255.255.0, which is very likely, anything starting with "192.168.0." is local. No need for a default gateway to route your connection elsewhere.

    This is the first mention of 192.168.0.88. Can you ping that one? If not, is it listed in "ip neighbor" after you tried?

  5. #15
    Join Date
    May 2010
    Beans
    92

    Re: Not able to ping other IP

    Quote Originally Posted by The Cog View Post
    With a subnet mask of 255.255.255.0, which is very likely, anything starting with "192.168.0." is local. No need for a default gateway to route your connection elsewhere.

    This is the first mention of 192.168.0.88. Can you ping that one? If not, is it listed in "ip neighbor" after you tried?
    Code:
    girish@girish-OptiPlex-3050:~$ ping 192.168.0.88
    PING 192.168.0.88 (192.168.0.88) 56(84) bytes of data.
    From 192.168.0.86 icmp_seq=1 Destination Host Unreachable
    From 192.168.0.86 icmp_seq=2 Destination Host Unreachable
    ^C
    --- 192.168.0.88 ping statistics ---
    9 packets transmitted, 0 received, +2 errors, 100% packet loss, time 8197ms
    pipe 6
    
    >> Can you ping that one?
    << No.
    
    
    As mentioned by SeijiSensei for CUPS link, I tried to Add printer by clicking on Adding Printers and Classes-Add Printer-Manufacture Canon-Modal LBP 6030/6040/6060 but it is not in the Model Combo list, so I don't know which Model I should choose, I choose any one and Clicked on Add Printer, but I got "Unable to Connect" message on the page i.e. Problem loading page.
    
    
    girish@girish-OptiPlex-3050:~$ ip neighbor
    192.168.0.87 dev enp1s0 lladdr 74:27:ea:07:b5:57 STALE
    192.168.0.88 dev enp1s0  FAILED
    192.168.43.1 dev wlx00c3f213fca7 lladdr a8:9c:ed:bc:57:80 REACHABLE
    fe80::1ea5:32ff:fe78:8238 dev enp1s0 lladdr 1c:a5:32:78:82:38 router STALE
    fe80::aa9c:edff:febc:5780 dev wlx00c3f213fca7 lladdr a8:9c:ed:bc:57:80 router REACHABLE
    2405:205:1488:201::9b dev wlx00c3f213fca7 lladdr a8:9c:ed:bc:57:80 router STALE
    girish@girish-OptiPlex-3050:~$ 
    
    >> is it listed in "ip neighbor" after you tried?
    << No.

  6. #16
    Join Date
    Nov 2007
    Location
    London, England
    Beans
    6,820
    Distro
    Xubuntu 19.10 Eoan Ermine

    Re: Not able to ping other IP

    This: 192.168.0.88 dev enp1s0 FAILED says that .88 does not even appear to exist on the network - it's not answering ARP requests. You could use tcpdump to prove that ARP requests are being broadcast by your PC and that no reply is being received. Beyond that, you need the help of someone administering your network. Since you can ping some other addresses, we know the network connection to your PC is working. I suspect that you either have the wrong address for the windows server (not .88), or perhaps you are using an IP address already in use by another machine (192.168.0.86).

  7. #17
    Join Date
    May 2010
    Beans
    92

    Re: Not able to ping other IP

    Quote Originally Posted by The Cog View Post
    This: 192.168.0.88 dev enp1s0 FAILED says that .88 does not even appear to exist on the network - it's not answering ARP requests. You could use tcpdump to prove that ARP requests are being broadcast by your PC and that no reply is being received. Beyond that, you need the help of someone administering your network. Since you can ping some other addresses, we know the network connection to your PC is working. I suspect that you either have the wrong address for the windows server (not .88), or perhaps you are using an IP address already in use by another machine (192.168.0.86).
    I confirm that printer is on 192.168.0.88 because when I gives the printing from windows from this PC which have its own ip 192.168.0.86, it works fine. It means, issue is at ubuntu level. This PC have dual boot i.e. Windows 10 and Ubuntu 16.04. Printer on ip 192.168.0.88 windows machine is accessible from my Windows 10 but I am not able to access/configure in ubuntu.

  8. #18
    Join Date
    Nov 2007
    Location
    London, England
    Beans
    6,820
    Distro
    Xubuntu 19.10 Eoan Ermine

    Re: Not able to ping other IP

    Can you find the outgoing arp request and returning arp reply with tcpdump? We might be able to spot something odd there although I can't think what that might be.

  9. #19
    Join Date
    May 2010
    Beans
    92

    Re: Not able to ping other IP

    Quote Originally Posted by The Cog View Post
    Can you find the outgoing arp request and returning arp reply with tcpdump? We might be able to spot something odd there although I can't think what that might be.
    Here is some info which you may find helpful please.

    Code:
    ARP, Request who-has 192.168.0.185 tell 192.168.0.82, length 46
    ARP, Request who-has 192.168.0.192 tell 192.168.0.82, length 46
    ARP, Request who-has 192.168.0.195 tell 192.168.0.82, length 46
    IP 192.168.0.86 > 192.168.0.88: ICMP echo request, id 17931, seq 2, length 64
    ARP, Request who-has 10.20.100.1 tell 10.20.100.7, length 46
    ARP, Request who-has 192.168.0.91 tell 192.168.0.87, length 46
    ARP, Request who-has 192.168.0.1 tell 192.168.0.73, length 46
    ARP, Request who-has 10.69.15.61 tell 10.69.15.33, length 46
    IP 192.168.0.86 > 192.168.0.88: ICMP echo request, id 17931, seq 3, length 64
    ARP, Request who-has 10.69.15.62 tell 10.69.15.33, length 46
    ARP, Request who-has 192.168.0.91 tell 192.168.0.87, length 46
    ARP, Request who-has 192.168.0.1 tell 192.168.0.73, length 46
    IP 192.168.0.86 > 192.168.0.88: ICMP echo request, id 17931, seq 4, length 64
    ARP, Request who-has 192.168.0.116 tell 192.168.0.85, length 46
    ARP, Request who-has 192.168.0.91 tell 192.168.0.87, length 46
    ARP, Request who-has 192.168.0.1 tell 192.168.0.73, length 46
    IP 192.168.0.86 > 192.168.0.88: ICMP echo request, id 17931, seq 5, length 64
    
    girish@girish-OptiPlex-3050:~$ ip neighbor
    192.168.0.90 dev enp1s0 lladdr 00:11:d8:ba:c3:6a STALE
    192.168.0.87 dev enp1s0 lladdr 74:27:ea:07:b5:57 STALE
    192.168.0.53 dev enp1s0 lladdr 00:e3:74:27:3d:bd STALE
    192.168.0.115 dev enp1s0 lladdr 74:27:ea:07:b8:ae STALE
    192.168.0.73 dev enp1s0 lladdr 70:71:bc:f4:ed:22 STALE
    192.168.0.88 dev enp1s0 lladdr 74:27:ea:07:b5:51 STALE
    192.168.43.1 dev wlx00c3f213fca7 lladdr a8:9c:ed:bc:57:80 REACHABLE
    192.168.0.82 dev enp1s0 lladdr 00:0e:2e:6f:e0:ca STALE
    fe80::aa9c:edff:febc:5780 dev wlx00c3f213fca7 lladdr a8:9c:ed:bc:57:80 router REACHABLE
    fe80::1ea5:32ff:fe78:8238 dev enp1s0 lladdr 1c:a5:32:78:82:38 router STALE
    girish@girish-OptiPlex-3050:~$
    And here is pinging reports of different IPs which are showing in ip neighbor :

    192.168.0.90 Works fine
    192.168.0.87 Not working
    192.168.0.53 Works fine
    192.168.0.115 Works fine
    192.168.0.73 Works fine
    192.168.0.88 Not working
    192.168.43.1 Works fine192.168.0.82 Works fine

  10. #20
    Join Date
    Nov 2007
    Location
    London, England
    Beans
    6,820
    Distro
    Xubuntu 19.10 Eoan Ermine

    Re: Not able to ping other IP

    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:
    Code:
    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:
    Code:
    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.

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •