This post is more than 5 years old
2 Posts
0
1585
Port 111 conflict between NetWorker 7.6 and Archive Server 10.1
Hi,
As the title says, we have a conflict problem with port 111 between NetWorker 7.6 and Archive Server 10.1. I've read that starting AS before NW solves the problem. We tried and it works indeed, but we don't have absolute control on the starting sequence, so we're looking for another solution.
We found the "change the 'emulate portmapper' entry in the 'Program Files\Nsr\Res folder\Nsrla.res' file" method (http://support.microsoft.com/kb/313621/en-us), but this solution seems to apply to older versions of NW and the Nsrla.res can't be found.
The second Microsoft method (http://support.microsoft.com/kb/313621/en-us too) says "go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\nsrexecd entry and add a REG_MULTI_SZ value that is named DependOnService, and then add portmap to the list", but it seems outdated too.
We also found that you can add port 111 in HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/services/Tcpip/Parameters/ReservedPorts registry, but we don't know if it applies.
We saw in several places that this port is not used by NW and it's a deprecated. functionality. Is there a up-to-date way to tell NW 7.6 not to use port 111?
Thanks
Jean
ble1
2 Intern
2 Intern
•
14.3K Posts
1
April 24th, 2013 13:00
Also, emulate option is in NSRLA resource of nsrladb. You can see it (and change it) with nsradmin:
C:\>nsradmin -p 390113
NetWorker administration program.
Use the "help" command for help.
nsradmin> show emulate portmapper
nsradmin> print type: NSRLA
emulate portmapper: Yes;
nsradmin> q
to change it, you would say update emulate portmapper: No
ble1
2 Intern
2 Intern
•
14.3K Posts
0
April 24th, 2013 13:00
In Windows you can configure service to start with delay.
jeanv
2 Posts
0
April 29th, 2013 12:00
We tried the Emulate Portmapper = No solution and it works.wonderfully!
Thanks a lot Hrvoje!