What is best workaround for RPC portmapper issues?

Question

One of our Windows admins is attempting to setup a Windows Networker client with MS Services-for-Unix (SFU), but the portmapper (nsrexecd.exe) is causing a problem ... what is best workaround for this issue ?? He showed me an MS suggestion to update \Program Files
sr\Res\Nsrla.res file to read: emulate portmapper: No; along with a registry hack as another alternative to make the SFU services start before Networker services... I also saw someone reference a solution-id 30312, but can't find it now...

DavidHampson · Accepted Answer

This is probably the one you want but it says pretty much the same thing as the Microsoft technote:

Solution Title: What is the Parameter "emulate portmapper" in the nsrla.res?
Solution ID: legato30122

Here is the solution:
There is an attribute on the NSRLA resource in nsrexecd called "emulate portmapper" by default set to "yes",
That can be set to "no" if you don't want lgto_mapper to attempt to listen on port 111.
This change will have no effect on NetWorker's performance.

Please see legato30219 for an example on how to do this with nsradmin.

Here is the problem or goal:
What is the Parameter "emulate portmapper" in the nsrla.res?

Problem Environment:
Windows 2000 SP3

NetWorker for Windows

In the past Legato support's take was the Networker portmapper should be enabled and any other portmapper should be disabled.

ble1 · Answer

You are probably talking about:http://support.microsoft.com/default.aspx?scid=kb;en-us;313621Refer to EMC/LGTO support note 58621 on KB for more details on MS's KB article (or in short go with nsrla option).

pgoslin · Answer

Thanks for the replies... The nsrla.res file update seems to work fine. We've done succesful backups and restores of this client with no problems whatsoever...

NetWorker

What is best workaround for RPC portmapper issues?

Was this post helpful?