UNSOLVED

kaizer2

updated

16 years ago

K

kaizer2

3 Posts

0

5317

January 12th, 2011 02:00

No route to host

Linux backup client fails with No route to host error message, however we're able to ping and perform nslookup the client from backup server(Windows 2003). rpcinfo -p hostname cmd returns the following error msg : can't contact portmapper error msg.Portmapper service was started on Linux client but the error still persist.

  • coganb

    736 Posts

    2884

    1

    Posted January 12th, 2011 02:00

    Hi,

    There's a number of different things that could be causing this.  Here's a couple of useful articles that should help you get to the bottom of it:

    Troubleshooting 'RPC error: Unable to send'

    Name Resolution Troubleshooting Best Practices

    -Bobby

  • dcouncil

    1 Message

    1772

    0

    Posted October 23rd, 2020 12:00

    Ever find solution? Having same issue

  • bingo.1

    1 Rookie

    2430 Posts

    1765

    0

    Posted October 24th, 2020 02:00

    Goodness - a 'revival' to a 9 year old problem !

    But the message is clear - it is a network related, most likely a name resolution problem. Try to verify this by using a local hosts file.

     

  • kim_chi

    2 Posts

    971

    0

    Posted February 5th, 2022 15:00

    on Avamar, at CLI as root, goto and edit /etc/hosts
    add a new entry with the ip_addr   FQDN_Hostname
    save & quit