All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
using dsadd over SSH
|
Logged in as: Guest |
Users viewing this topic: none |
|
Login  |
|
|
using dsadd over SSH - Feb. 16, '04, 3:53:12 PM
|
|
|
baughj
Posts: 3
Joined: Feb. 5, '04,
Status: offline
|
I am writing a script to add users to our network. The process involves creating a Unix user, and then SSH-ing over using public key to the Windows box and running dsadd.
This entire process was working fine until I rebooted my domain controller to fix a hardware issue. Now, I get the following message:
dsadd failed:CN=<username>,CN=Users,DC=corp,DC=request,DC=com:
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.
I' m not too sure why delegation is required when I' m logged in as Administrator...what gives? In ADU&C the machine is specified as allowing delegation. I haven' t made any policy changes recently.
< Message edited by baughj -- Feb 17, '04, 9:34:49 AM >
|
|
|
RE: using dsadd over SSH - Feb. 16, '04, 6:03:05 PM
|
|
|
markfunk
Posts: 670
Joined: Mar. 31, '03,
Status: offline
|
Are you ssh' ing into the system that is the Domain Controller ?
Which Administrator are you logging into ? The local Administrator or the Domain Administrator ?
If there are two Window' s machines, then computer trust is usually when the Winodow' s workstation (that is part of the domain) contacts the domain controller to authenticate itself with the domain controller. Then the " trust" relationship is established.
If there are two Windows' machines, have you tried rebooting the non-domain controller.
Other than trying that, perhaps you should post your question on the microsoft newsgroup (serer = msnews) :
microsoft.public.servicesforunix.general
|
|
|
RE: using dsadd over SSH - Feb. 17, '04, 9:32:49 AM
|
|
|
baughj
Posts: 3
Joined: Feb. 5, '04,
Status: offline
|
I am SSHing as Administrator@hostname. The Administrator user in AD has a defined home directory with the appropriate keys.
This is the singular domain controller on the network (at the moment we do not have any others).
The machine I am SSHing from is a FreeBSD machine. dsadd worked, literally, completely fine, until I rebooted the DC to replace some hardware.
I' ll post over on the newsgroup though, thanks for the pointer.
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
|
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|