| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 55.1 | Installing NetWorker from a Shared Volume | DECWET::KOWALSKI | Cat parade organizer | Thu Nov 07 1996 11:27 | 12 |
| 55.2 | Resolving Connection Problems | DECWET::KOWALSKI | Cat parade organizer | Thu Nov 07 1996 11:28 | 111 |
| 55.3 | SPX/IPX Services | DECWET::KOWALSKI | Cat parade organizer | Thu Nov 07 1996 11:30 | 39 |
| 55.4 | Windows NT Client Notes | DECWET::KOWALSKI | Cat parade organizer | Thu Nov 07 1996 11:31 | 55 |
| 55.5 | Info we need for problems w/ NSR modules for Exchange/SQL Servers | DECWET::LENOX | Spring Training is less than a month away! | Wed Jan 22 1997 14:18 | 55 |
| 55.6 | Tool to provide basic NT support information | DECWET::KOWALSKI | Time's not for saving | Thu Jan 23 1997 08:54 | 60 |
| 55.7 | Cannot register service: Timed out | DECWET::KOWALSKI | Time's not for saving | Tue Feb 04 1997 11:08 | 11 |
| The NT client is installed by default with the
remote exec service enabled and the legato portmapper
disabled. Nevertheless, when the remote exec service
starts, it attempts to register itself with the
portmapper. This effort times out and fails after
a few minutes, resulting in the message in the
daemon.log "Cannot register service: Timed out".
The message can be ignored. If the portmapper
is started, the message will not occur.
Mark
|
| 55.8 | nsr_ping diagnostic tool | DECWET::KOWALSKI | Time's not for saving | Thu Feb 06 1997 08:51 | 55 |
| I posted today the "nsr_ping" tool for diagnosing connectivity
problems with clients in
slugbt:/pub/networker/miscellaneous/unsupported/nsr_ping
aka
ftp://www.zso.dec.com/pub/networker/miscellaneous/unsupported/nsr_ping
Right now there are only NT versions for NetWorker V4.3 (Intel
or Alpha); however, these NT versions can diagnose problems with
ANY NetWorker client.
Here are the README's from the ftp area:
nsr_ping is an unsupported troubleshooting tool
for diagnosing NetWorker client connectivity
problems. Run it from the NetWorker server,
specifying the NetWorker client with the
-c option.
The tool checks three items of connectivity:
1. Performs an ICMP ping (see man ping) against
the client. A failure here indicates a very
basic TCP/IP configuration problem.
2. Performs an RPC 'ping' by contacting the
(NetWorker) portmapper on the client. A failure
here probably means the portmapper is not
running.
3. Performs an nsr_ping by contacting nsrexecd
on the client and running "savefs -pp". This
should report back the client's attribute.
A failure here may mean:
- nsrexecd is not running
- the savefs program is missing
- the server is not authorized to backup the
client (not in /nsr/res/servers file).
=====================================================
On NT, run nsr_ping.exe from a Command Prompt window.
The executable must be in win32app\nsr\bin or
win32app\nsr\bin must be on your PATH.
usage:
nsr_ping [-rin] [-D2] [-c client]
[-c client] client to ping, default localhost
[-D2] run in debug mode
[-i] don't ICMP ping
[-n] don't NetWorker ping
[-r] don't RPC ping portmapper
|
| 55.9 | Windows version of nsr_ping | DECWET::KOWALSKI | Time's not for saving | Mon Feb 10 1997 14:35 | 7 |
| Windows versions of the nsr_ping program were
also posted for Alpha and Intel NT.
/pub/networker/miscellaneous/ \
unsupported/nsr_ping/NT/{Alpha | x86}/WinPing.zip
Mark
|
| 55.10 | for more on killing processes | DECWET::LENOX | When Sears comes out with a Kenmore PC... | Wed Apr 30 1997 11:21 | 6 |
|
If pviewer or stopping the NetWorker services does not kill
all the nsr processes, then at the command prompt use TLIST
to get a list of processes and their pids and use KILL -f
with the pid to kill the processes. This hasn't failed me
yet.
|
| 55.11 | | montlake.zso.dec.com::lenox | posted with NetNotes | Fri May 30 1997 18:24 | 10 |
|
Does your tape seem to hang when labeling?
Never fear, check your daemon.log, asap! If you see
authentication errors, it probably is an indication that
your TCP/IP addressing is not setup properly. E.g.
say you have two IP addresses for the system but
your DNS/WINS stuff doesn't do reverse lookups
properly. NetWorker is very touchy about IP name
lookups.
|