Can you please ensure that the account with which you are logged in has got the Admin rights on the OU where the CIFS server is joined.
If you have followed the primus and set the djAddAdminToLg parameter value to 1 - you need to join the CIFS server to the OU after setting this parameter. If you have set the parameter after the CIFS server was joined - you have to unjoin the CIFS server and join it back.
Lastly - are you in a different DNS Domain than the CIFS server? I mean, the computer from where you are trying to run the computer management - is that in a different DNS domain or having a different DNS Domain suffix than the CIFS server? In that case, you will not be able to see the Local User and Groups with RMC Server unavailable message.
You need to add the DNS Suffix in the search order on the TCP/IP properties on your computer. Go to Network connection - TCP/IP Properties - select advanced - in the DNS Tab - ensure that the DNS suffix for the CIFS server is appended - if not add the one.
The account does indeed have Admin right on the OU.
I have set the djAddAdminToLg parameter to 1 prior to added the CIFS server back to the domain. The server that I am connecting with is in the same domain as the CIFS server
This is not the first CIFS server we've created, but it is the first with this issue. I have noticed a couple things....
When I list the server parameters I see djAddAdminToLg twice.
nandas
4 Operator
•
1.5K Posts
0
November 5th, 2008 08:00
If you have followed the primus and set the djAddAdminToLg parameter value to 1 - you need to join the CIFS server to the OU after setting this parameter. If you have set the parameter after the CIFS server was joined - you have to unjoin the CIFS server and join it back.
Lastly - are you in a different DNS Domain than the CIFS server? I mean, the computer from where you are trying to run the computer management - is that in a different DNS domain or having a different DNS Domain suffix than the CIFS server? In that case, you will not be able to see the Local User and Groups with RMC Server unavailable message.
You need to add the DNS Suffix in the search order on the TCP/IP properties on your computer. Go to Network connection - TCP/IP Properties - select advanced - in the DNS Tab - ensure that the DNS suffix for the CIFS server is appended - if not add the one.
Hope this helps,
Thanks,
Sandip
pittperson
96 Posts
0
November 5th, 2008 09:00
I have set the djAddAdminToLg parameter to 1 prior to added the CIFS server back to the domain. The server that I am connecting with is in the same domain as the CIFS server
This is not the first CIFS server we've created, but it is the first with this issue. I have noticed a couple things....
When I list the server parameters I see djAddAdminToLg twice.
djAddAdminToLg cifs 0 1 1
djUseKpasswd cifs 0 0
djEnforceDhn cifs 1 1 1
djAddAdminToLg cifs 0
Also, while reviewing the output of a .server_config that was run by support I noticed the following..
CIFS server with no problems
-------------------------------
VDM=vdm1 CIFS SERVER=SERVER1[DOMAIN] dump cred at 0x5b378c04
1225902261: SMB: 4: USER 'DOMAIN\username'
Auth=NTLMSSP CredCapa=0x10801
SID = S-1-5-15-3814076-70c33b37-3b2108ea-36294
1225902261: SMB: 4: PRIMARY = S-1-5-15-3814076-70c33b37-3b2108ea-201
1225902261: SMB: 4: Priv=0x7f,0x3 DefOpt=0xe Adm=1, Backup/Adm=1 (Bkp=0) NTCapa=0x10801
CIFS server in question
-------------------------------
VDM=vdm2 CIFS SERVER=SERVER2[DOMAIN] dump cred at 0x37c0e804
1225902261: SMB: 4: USER 'DOMAIN\username'
Auth=NTLM CredCapa=0x401
SID = S-1-5-15-3814076-70c33b37-3b2108ea-36294
1225902261: SMB: 4: PRIMARY = S-1-5-15-3814076-70c33b37-3b2108ea-201
1225902261: SMB: 4: Priv=0x7f,0x3 DefOpt=0xe Adm=1, Backup/Adm=1 (Bkp=0) NTCapa=0x401
I am not familiar with the output, just merely point out differences in hopes that someone else might notice something.