Domino & Notes error

No answer at last known address

A line in the output of a Notes client or server trace, usually followed by a 'server not responding' type error.

What it means

Notes tried the network address it had cached for the server and got no reply there, so the connection attempt failed or moved on to other lookups.

Common causes

  • The server's IP address changed but the client or server is still using the old cached address
  • DNS or the hosts file still returning the old address
  • A Connection document or Net address pointing at an IP that is no longer in use
  • The server is down or a firewall is blocking port 1352

Quick fixes

  1. Restart the Notes client so it looks the server up again, then rerun the trace (the Trace button in the client's Ports preferences, or trace [server] on a server)
  2. Confirm DNS, any hosts file entries and the Server document's Net address all give the current address
  3. Correct or remove Connection documents that hard-code the old IP address
  4. Check the server is up and that port 1352 is reachable from the client

Need a hand with this?

Paste your exact message into What's That Error? for a plain-English explanation, or get in touch. I've been supporting Domino and Notes for 28 years.

Disclaimer

The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.

This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.