Siemens Unix V4.0 - Manual (Page 229)

Implementing WINS Troubleshooting WINS Servers
Product Manual U7613-J-Z815-6-76
©
S
iem
e
n s N
ix
dor
f
In
fo
rm
at
io
n
s s y s te
m
e A
G
1
9 9 5
P
fad
: D:
\O
7 613
e6
\u
761
3e
.k
10
To ensure that the WINS service is running:
Ê Use the wins status command at the Advanced Server command prompt to verify that
the WINS service is running. The command should display three processes named
"nbrfcdaemon", "lmx.ep" and "lmx.wins". You can also use the Services option in the
Server Manager to verify that the WINS service is running.
Ê If necessary, use the wins start command to start the service. Observe possible error
messages.
Even if the WINS service is running (but the SERVER service is not), you may get a
message like ”The Windows Internet Name Service is not running on the target machine or
the target machine is not accessible”.
To ensure that the WINS service is not only running, but also available for
administration:
Ê Use the asx status command at the Advanced Server command prompt to verify that the
SERVER service is running.
Ê If necessary, use the asx start command to start the service.
Resolving common WINS errors
To resolve "duplicate name" error messages
Ê Check if the WINS database contains name-to-IP address mappings for the name. If
there is a static address record with the name and an inconsistent IP address, delete it
from the primary WINS server database.
- Or -
Ê Check the MigrateOn box using the Advanced option in the WINS Server Configu-
ration dialog box in WINS Manager.
To locate the source of ”network path not found” messages on a WINS client
Ê Check the WINS database for the name. If the name is not present in the database,
check whether the destination or target computer uses b-node name resolution. If so,
configure this client to use WINS or add a static mapping for it in the WINS database.
Ê If the computer is configured as a p-node, m-node, or h-node and if its IP address is
different from the one in the WINS database, then its address may have changed
recently and the new one has not replicated to the local WINS server. Ask the WINS
server that registered the address to perform a push replication with propagation to the
local WINS server.