Old client information shown in nwadmin indexes and save sets 1

[bengood24]

I have a Networker 6.1.3 server running on HP-UX. I have a group of Windows 2000 servers that are Networker clients. Some time before I started in this position some of these Windows servers were decomissioned. The hostnames have not been reused, but the IP addresses have been reused by new Windows servers. I am attempting to use Networker to back up these 4 new servers.

When the save group starts that these 4 new servers are in, the backup fails at the authtype: nsr client message that a lot of people see for various reasons. I ran a sniffer on the windows machine and saw that the Windows machines were retransmitting packets to the Networker server and were not receiving a reply. The machines are in a switch, I don't have an easy way of running a sniffer to see if the HP machine is trying to respond.

I don't know for sure what is going on, but I do know there is information for the old servers when looking at the Indexes window in nwadmin, and those servers are listed in the list of clients in the save set recover window. When I run mminfo, I see no information about the old servers. There are no indexes in the /nsr directory for the old servers.

Is there any way that I can remove this old information completely?

I can add a new machine with a previously unused hostname and IP address and back it up with no problems.

 

[Chacalinc]

did you see the /etc/hosts file of your hp box? probably your old windows are there and the hp box is mixing all servers (old and new)

 

[bengood24]

The /etc/hosts only has the new servers. None of the decommissioned servers are listed in it.

 

[Chacalinc]

When the save group starts that these 4 new servers are in, the backup fails at the authtype: nsr client message that a lot of people see for various reasons.

could you post the message?

some errors I get sometimes when I install new windows clients are for *name vs IP* related mistakes. unix must have them with the correct name in the /etc/hosts table and windows must see the unix box with its name (ussualy in the C:\winnt\system32\drivers\etc\hosts )

if you ping from hp to windows *using the name* is correct? and back from win to hp is correct (again with name).

 

[bengood24]

Ping with name or IP works perfectly from HP to Windows and from Windows to HP.

The error message is as follows:

All unexpectedly exited:incr:save
:All 5 retries attempted
:All nsrexec: authtype nsrexec
:All type: NSR client description;

When you look at the windows machine on ethereal sniffer you see the packet with the text NSR client description; then more packets with what should follow (I don't remember the contents but it is more information about the networker client), and that packet gets retransmitted by the windows machine until the retries are finished.

I am trying to get ethereal running on the HP machine to see what it is doing now.

 

[Chacalinc]

hmmm.... some firewall?

from windows: rpc -p hp_box

take a look to the ports opened.

 

[Chacalinc]

sorry, command is : rpcinfo -p hp_box

try it back from hp to windows too.

 

[bengood24]

From Windows to HP.

program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390115 1 tcp 16692
390113 1 tcp 7937
390103 2 tcp 8322
390109 2 tcp 8322
390110 1 tcp 8322
390103 2 udp 8323
390109 2 udp 8323
390110 1 udp 8323
390107 5 tcp 8323
390107 6 tcp 8323
390105 5 tcp 9231
390105 6 tcp 9231
390104 105 tcp 8204
program vers proto port
100000 4 tcp 111
100000 3 tcp 111
100000 2 tcp 111
100000 4 udp 111
100000 3 udp 111
100000 2 udp 111
100024 1 tcp 49152
100024 1 udp 49153
100021 1 tcp 49153
100021 1 udp 49154
100021 3 tcp 49154
100021 3 udp 49155
100021 4 tcp 49155
100021 4 udp 49156
100020 1 udp 4045
100020 1 tcp 4045
100021 2 tcp 49156
1342177279 4 tcp 51972
1342177279 1 tcp 51972
1342177279 3 tcp 51972
1342177279 2 tcp 51972
100005 1 udp 53205
100005 3 udp 53205
100005 1 tcp 56626
100005 3 tcp 56626
100003 2 udp 2049
100003 3 udp 2049
100003 2 tcp 2049
100003 3 tcp 2049
390115 1 tcp 16692
390113 1 tcp 7937
390103 2 tcp 8322
390109 2 tcp 8322
390110 1 tcp 8322
390103 2 udp 8323
390109 2 udp 8323
390110 1 udp 8323
390107 5 tcp 8323
390107 6 tcp 8323
390105 5 tcp 9231
390105 6 tcp 9231
390104 105 tcp 8204

From HP to Windows

program vers proto port service
100000 2 tcp 7938 rpcbind
100000 2 udp 7938 rpcbind
390113 1 tcp 7937 nsrexec

I have no firewall between the server and clients.

 

[605]

Do you start all over? If not, i assume it will fail because NetWorker will also remember their old IP adresses in the media database.

First, the name resoulution must be unique from all directions. But also the IP address must not change unless you redefine the clients.


Finally, try to run a manual backup from the clients first before you start a group from the server.

 

[bengood24]

If I remember correctly a manual backup from the client was working, but I haven't tried this recently. IP address resolution is identical in both directions. Basically, I'm trying to find a way to keep from starting all over.

 

[605]

Sorry, i should have mentioned this earlier:

NW stores information about the client ID in the media index. Part of this info will be the IP address. If you do not start from scratch, problems will be obvious.

 

[bengood24]

Ok, I had a feeling I would have to redo the setup.... it's just I've never done it from the beginning in the first place and wanted to see if I was missing something. Thanks for the help.

 

[bengood24]

Ok, so it's almost 2 months later and I've finally reinstalled Legato on the HP server. And to my surprise last night it STILL did not back up those 4 windows servers from before. I am completely baffled. There is no mention whatsoever in any DNS or any hosts file about the old server names.

I removed Networker, and the /nsr (well I moved it to keep just in case). Checked the hosts files, the DNS servers, the clients' hosts files. rpcinfo shows the right ports open. nslookup by name and IP resolves correctly. I see traffic on tcpdump but I still see retransmissions from the windows machine to the HP after the NSR client description packet.

I can backup manually from one of the 4 windows servers to the HP with no problem. I can add a completely new windows server and back it up from the HP server with no problem.

Any ideas?