[25146] in Hotline Meeting
call to hotline from James Ernstmeyer - problem resolved
daemon@ATHENA.MIT.EDU (Jerry Burke)
Thu Oct 27 13:07:07 1994
Date: Thu, 27 Oct 94 13:12:38
From: burke@MIT.EDU (Jerry Burke)
To: hotline@MIT.EDU
HI all,
James sent email to hotline saying he got an error message "no hesiod"
and could not get into Athena. ....
Dept: EECS room m26-463-1 It's a VS3100.
Called james to see if the problem could be his network connection.
He has an SUTPE drop with a Mau. His the link light was out. Asked him
tosee if the aui cable wwas loose. It was. He recoonected and all is
okay.
I asked him to let us know if the cable comes loose again and we will
replace it.
Explanation:
No hesiod - could be a symptom of many things, because the last thing
the workstation does is check for this info.
The most common I have found are:
- network drop bad
- cable bad
- cable loose
- hesiod servers really are down
Trouble shooted this by:
- Checking hesiod servers 1st, they were up
- ping the clients workstation m26-463-1 (got no response
- called the client to check the network drop, asked him to look for the
link light on the tpt transceiver
- if no tpt transceiver then ask client to reseat his utp connection
- if multiple port transceiver (ask client if possible to switch to
another port on the dual or quad transceiver)
- once they check this they can try to logon again
- if do all this and still are having a problem, you may want to look at
the afs servers, to see if they are up.
- if all this checks out we may want to report to ops or help-desk,
depending on problem
This saves the client and us time, I did this over the phone in less
than 5 minutes.
Client is back up... Jerry
