I'm pretty sure it reads nsr.res and nsrjb.res Is this related to the access violation problem? If you getting that message on a regular basis. Does the error occur during backups? Sniffer like product would show you what happening on the wire. Network spy comes to mind.
nsr.res -> config file
nsrjb.res -> jukebox config file, containing info on media devices, volumes etc.
nsrla.res -> connection settings with ports etc.
The only way to force a client to connect to a specific server is to add '-s servername' in the shortcut of nwadmin.exe. Otherwise the server would just scan the network for all networker servers. Usually it would connect to the last server connected to.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.