Unsolved
This post is more than 5 years old
2 Intern
•
724 Posts
0
2140
March 30th, 2006 10:00
Domain name change
Hi, I'm trying to understand what could be wrong here. This is the situation:
Networker 7.2 running on Windows 2003 machines, all backups working fine, until someone change the domain of one of the clients. It was winserver01.test.com, and now it winserver01.test2.com.
The problem is that the client is configured with it's short name, just winserver01. All the clients and the server are in a dedicated backup network, so all hosts files set the short and long name to each IP address of that network.
First I thought that it would have no problem, since Nw server would try to reach winserver01, no matter if it is test.com or test2.com, but backups started to fail. So I added the winserver01.test2.com in the hosts files and in the aliases in client configuration. Ping works fine from any machine, to "short" or "long" names.
Manual backups work, but I receive the "Cannot contact nsrexecd service" message. Schedule backups always fail.
Networker 7.2 running on Windows 2003 machines, all backups working fine, until someone change the domain of one of the clients. It was winserver01.test.com, and now it winserver01.test2.com.
The problem is that the client is configured with it's short name, just winserver01. All the clients and the server are in a dedicated backup network, so all hosts files set the short and long name to each IP address of that network.
First I thought that it would have no problem, since Nw server would try to reach winserver01, no matter if it is test.com or test2.com, but backups started to fail. So I added the winserver01.test2.com in the hosts files and in the aliases in client configuration. Ping works fine from any machine, to "short" or "long" names.
Manual backups work, but I receive the "Cannot contact nsrexecd service" message. Schedule backups always fail.
No Events found!
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
April 6th, 2006 14:00
10.100.5.0 is backup network
10.100.32.0 is production...
OK. So the server will always use production for metadata against the client if I remember correctly (or client will return it that way). The data itself should go against the backup LAN if you have set hostname associated with 10.100.5.3 (brqoc-s-0000017) in server network interface in client resource for abbsv006. What you need to do now is to test also management communication between these two (10.100.32.10 on server and not sure what it is on client side).
dpinink_silva
2 Intern
•
724 Posts
0
April 6th, 2006 14:00
10.100.5.0 is backup network
10.100.32.0 is production...
dpinink_silva
2 Intern
•
724 Posts
0
April 6th, 2006 14:00
C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 08 c7 0d 9f 43 ...... Compaq NetFlex-3 Driver, Version 5.0.1.18
0x3 ...00 0a 5e 47 1c 5e ...... Broadcom NetXtreme Gigabit Ethernet Driver
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.100.32.1 10.100.32.10 1
10.100.5.0 255.255.255.0 10.100.5.4 10.100.5.4 1
10.100.5.4 255.255.255.255 127.0.0.1 127.0.0.1 1
10.100.32.0 255.255.252.0 10.100.32.10 10.100.32.10 1
10.100.32.10 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.100.5.4 10.100.5.4 1
10.255.255.255 255.255.255.255 10.100.32.10 10.100.32.10 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 224.0.0.0 10.100.5.4 10.100.5.4 1
224.0.0.0 224.0.0.0 10.100.32.10 10.100.32.10 1
255.255.255.255 255.255.255.255 10.100.32.10 10.100.32.10 1
Default Gateway: 10.100.32.1
===========================================================================
Persistent Routes:
None
And this is one rpcinfo test I did before:
c:\>rpcinfo -p brqoc-s-0000017
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390113 1 tcp 7937
390103 2 tcp 8750
390109 2 tcp 8750
390110 1 tcp 8750
390120 1 tcp 8750
390103 2 udp 9341
390109 2 udp 9341
390110 1 udp 9341
390120 1 udp 9341
390105 5 tcp 9595
390105 6 tcp 9595
390107 5 tcp 9640
390107 6 tcp 9640
390104 105 tcp 9477
390104 205 tcp 8624
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390113 1 tcp 7937
390103 2 tcp 8750
390109 2 tcp 8750
390110 1 tcp 8750
390120 1 tcp 8750
390103 2 udp 9341
390109 2 udp 9341
390110 1 udp 9341
390120 1 udp 9341
390105 5 tcp 9595
390105 6 tcp 9595
390107 5 tcp 9640
390107 6 tcp 9640
390104 105 tcp 9477
390104 205 tcp 8624
I'll check about the two nsrexecd processes, this sound a good thing to look for...