- This topic has 3 replies, 3 voices, and was last updated 19 years, 2 months ago by
.
-
This has been explained several times on the online manual also, I’ll put here a resume, hope it’s clear:
The management console performs any operation on the services and the remote file systems using the Windows API. The entire authorization procedure is handled by windows itself, this means you can have two distinct scenarious:
1 – You’re working on a workgroup. In that case, you’ve to be sure to be logged locally as an Administrator and also , your Administrator account must be available on the remote nodes sharing the same password. This will grant the user remote access. Also, if remote nodes are XP based, be sure to TURN OFF SIMPLE FILE SHARING. Details can be found on the microsoft MSDN site.
2 – You’ re logging on a domain. In that case, just log as a domain Administrator, be sure that the domain Administrator is also a LOCAL ADMINISTRATOR on each node and everything will work fine.
Your case is a little weird. You’re working on a domain but you have the farm on a workgroup outside the domain. I suggest you to make one of the following choice:
1 – Use the management console from an host that’s part of the workgroup, follow the rules I said before and you shouldn’t have any problem.
2 – Get yourself a big headache and find a way to authenticate a domain user on a workstation outside the domain itself. This is a little complicated but I think there should be a way to make it working.
Hope everything has sense
You must be logged in to reply to this topic.
