3.3

iNEWS Workstation Problems
97
A message similar to the following should appear:
Pinging nrcs-a [10.1.38.30] with 32 bytes of data:
Reply from 10.1.38.30: bytes=32 time<10ms TTL=255
Reply from 10.1.38.30: bytes=32 time<10ms TTL=255
Reply from 10.1.38.30: bytes=32 time<10ms TTL=255
C:\>;
If you do not get replies, then the server is either down or a networking problem
exists. A brief message, similar to one of the following lines, might appear:
Bad IP address nrcs-a
Bad host nrcs-a
The iNEWS Workstation is unable to look up the name to obtain the IP address of
the server. It is unable to resolve the host name. This indicates the name entered in
the login dialog box does not exist in the local hosts file on the PC or on the Domain
Name Server (DNS) if your network is configured to use a DNS.
n
The workdebug command may be used in system operator or superuser mode.
2. If the workstation can successfully ping the server, the next step is to run the workdebug
stat command on each server at the console.
The workserver process runs on iNEWS Servers that manage the connection between
PCs and servers. The workdebug stat command queries the workserver to obtain a list of
how many sessions are configured and how many are currently logged in:
NRCS-A# workdebug stat
workserver: configured GUI general count: A 19 B 0 C 0 D 0
workserver: running GUI general count: A 0 B 0 C 0 D 0
(etc)
If workdebug stat does not return a response at the console, this may indicate the
workserver process has either died or entered a non-responsive state. The workserver
process may need to be killed and restarted. Contact Avid for further instructions.
3. If you get a response from workdebug stat, you can put workserver into a diagnostic
mode where it will display messages on the screen when PC clients attempt to establish
a connection. To do this, select all servers and type:
NRCS-A$ workdebug debug