Ref: 03250312
Title: Cause of "Name Server not Found" Message on Server Boot Up
Date: 7-28-88

Copyright 3Com Corporation, 1991.  All rights reserved.

Problem:  What can cause a "Name Server not found" message when
booting a PC server with Name on it?  What causes messages such
as "ST:No Name Server" or "Looking for Name" on the LCD of a 3Com
server?

Possible Answers:  Normally this is a cabling problem or caused
by a change to the Ethernet address chip.

(1) To verify cabling on a PC server, boot up with a loopback
plug on the Ethernet port.  If the server boots up with the
loopback plug, there is a cabling problem.

(2) Check the board with diagnostics. If the loopback boot fails
and diagnostics pass, verify the Config.sys command line
parameters on your Ethernet driver.

(3)  If neither of the procedures above solve the problem,
another explanation must be sought.

Since this is the Name server, not having the correct domain in
the Name database is ruled out.

Another possibility is a changed or corrupted Name domain or a
changed Ethernet address (motherboard or Ethernet adapter.)  To
verify, first be sure that you have a complete configuration
report.  Then rename \3Plus\3Name\NS_DOM.000 to Old.000, copy
from your Name diskette A:\3Name\NS_DEF.DOM to C:\3Plus\3Name,
and then run \3Plus\3Config\3Namck /i to recreate NS_DOM.000.  Be
sure to use your EXISTING network number and adjust parameters to
their previous state.

If you reboot and the problem disappears, you most likely had a
corrupted Name domain.  If you reboot and you still have the
problem, a cabling problem is highly likely.

On a 3Com server, the diagnostic procedure is essentially the
same as on a PC server.
