Here's a note we recieved on this topic just the other day
(sorry, I thought it had already been posted):
Subject: Netview 6 NT Client installation problems
John, just in case anyone else wastes an hour or so, then be aware that
a bug in the Netview 6 NT client installation process, as it doesn't update
/winnt/system32/drivers/etc/services with the port numbers and aliases
for the client to talk to the server. This shows itself with Cannot connect
server database messages.
Fix: copy all of the TME10 Netview 'services' entries from the server
installation to the client. Remeber that NT needs a reboot to pick this up.
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
---------------------- Forwarded by Leslie Clark/Southfield/IBM on
04/07/2000 04:15 PM ---------------------------
"Chance, Larry" <email@example.com>@tkg.com on 04/07/2000 11:49:11 AM
Please respond to IBM NetView Discussion <firstname.lastname@example.org>
Sent by: email@example.com
To: "'firstname.lastname@example.org'" <email@example.com>
Subject: [NV-L] Listening Port - Client/Server
Anybody know the PORT number used by the Netview for NT server
for which remote CLIENTS are connected? I'd like to find out if it's
'listening', but I don't know that PORT number.
I'm having problems with a CLIENT workstation not connecting
to the Netview for NT server. NETCHECK doesn't connect with TCP
either, however 'nbsession' is OK.
I didn't have this problem in version 5.x. I don't remember anything
at the server that needed starting for a remote client. Does version 6
do something different?
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l