Author Topic: Network routing error  (Read 3369 times)

Offline Legend

  • First timer
  • *
  • Posts: 4
    • View Profile
Network routing error
« on: August 24, 2005, 07:23:35 am »
From time to time I receive routing error messages similar to these: *** Routing -- from No response from[[email protected]], closing link

From what I understand, "no response" means one server is no longer able to communite with another in the network by pinging, so the two servers delink. Although my server clock is off a minute or two, one of your reps in #ShadowRealm told me that system time is -not- a culprit of these mysterious "no response" error messages.

What are some possible causes (beyond the fact that one server cannot communicate with another) for "No response from..." routing errors? I'm looking for what is causing it and how to avoid these delinks. Could it have anything to do with my datacenter's network?


(Sorry, I just realized this should be on the UltimateIRCd 3.0 Support forum.)

Offline erich

  • Needs to get out more
  • ****
  • Posts: 132
    • View Profile
Network routing error
« Reply #1 on: August 24, 2005, 05:42:58 pm »
when this happens try ssh to both boxes and traceroute.

linux syntax: traceroute
win32 syntax: tracert

And keep servers in time sync. Its important. NTP client is a MUST on all servers you link.
Network Founder @


SimplePortal 2.3.7 © 2008-2022, SimplePortal