What is in your exports file? It should contain rw, user=Administrator
IS this machine a domain controller or something? This is basically a permissions issue in accessing the target through nsh.
The "No authorization to access host" error points to issues with ACLs.
- ACLs are correct in the users, exports and/or users.local files on target server for the Role that executes the job
ex: Role:User rw,map=root
- There are no restrictions in running the commands that are used by the job. If restrictions are used, then make sure the command is present in the list
ex: Role:User rw,map=root,commands=CM:cmd1:cmd2:cmd3
Lets agree for a second its to do with auth files. something has gone wrong with them.
Even after putting the working server authorization files, its the same. We do not have a lot in the exports file.
All we have is our application server name and readonly permission.
ex: server1 ro
We have some 3 application servers, we have given read only for them. This is still working on most of the machines, it is the case with few which doesnt work.
what about users and users.local files ??
well, they look pretty ok. Authorization files are same which are in the non-working server as the working server.
Would like to know if there are any other troubleshooting steps to fix this.
can you past the contents of each file ?
#* rw, user=bladmin
# BLAdmins ACLs
BLAdmins:XXXXX(LAN ID) rw,map=Administrator
unless this is the file server, you don't need 'System:System' in the users.local file.
what role:user are you connecting as?
what host are you connecting from? can the target resolve the hostname as it's entered in the exports file of the appserver(s)?
what is in the rscd.log on the target when you get that error message ?
The are a few reasons why copied security files don’t work on a different server.
Do the following:
1) If you have hostnames in exports file, please confirm they are resolved on the target server
2) If you have IP’s, then the appserver may be NAT’d on that target server, i.e. the incoming IP could be different.
In order to troubleshoot this, replace the IP’s in exports file with * and see what happens
3) Double check the Windows admin user you use in users and users.local file exists on that server. In other words, make sure the Windows user “Administrator” exists on that server