1 isolating the problem, 2 checking the network, Troubleshooting troubleshooting procedures – Siemens Unix V4.0 User Manual

Page 241: Unable to post the name on any network: <name

Advertising
background image

Troubleshooting

Troubleshooting Procedures

Product Manual

U7613-J-Z815-6-76

©

S

ie

m

ens

Ni

x

d

o

rf

I

n

fo

rm

a

ti

o

ns

s

y

s

te

m

e A

G

19

95

P

fad

:

D

:\

O

761

3e

6\

u76

13

e.

k

1

1

11.2.1

Isolating the Problem

Advanced Server runs on a UNIX system computer. The server depends upon a fully-
functional NetBIOS network to perform its file and print serving functions.

A “NetBIOS network” typically includes the following components: an application that
provides a NetBIOS protocol interface; an application that provides a network transport
protocol interface, such as TCP/IP (although some transport implementations include
NetBIOS within a common module); and an application that provides drivers for the network
adapter interface (which also may be part of the transport module).

Every NetBIOS network component must be configured and operational in order for
Advanced Server to function in a network environment. Additionally, similar modules must
be functioning on the machine which is attempting to use the file and print services of
Advanced Server, such as a Windows NT Workstation computer or Windows client
computer.

When a NetBIOS network is not available, the system typically displays the following
message when you start the server:

unable to post the name on any network: <name>.

Reviewing all of the modules involved in the end-to-end connection between a client and
Advanced Server, it is easy to see that isolating a problem is the first step for problem
solving in a client-server networking environment.

Before assuming that the problem is with the server, you must ensure that other networking
software is functioning properly. This is particularly true with new installations in which the
opportunity for a transport or physical network problem is the greatest.

It is fruitless to perform an exhaustive check of every layer of software for a problem which
affects only a single client or user. Experience will help you to determine when to use a
comprehensive problem isolation procedure or a server-specific problem isolation
procedure. The following sections offer guidelines on how to perform both procedures. Use
the one that best fits your current problem description.

11.2.2

Checking the Network

Before assuming that the server is the cause of all network problems, it is worthwhile to
perform checks to verify the sanity of the network. This is particularly important when all or
a very large portion of server users are reporting a problem at the same time.

Use the following steps to verify the sanity of the network.

Advertising