Active Directory on Windows Server 2003

[Baffled]

If I am adding a server to a domain, do I need to load Active Directory onto that server for it to be accessible from another domain? The only other server in the same domain is accessible from the other domain but this one isn't

[jamesj2001]

What exactly do you mean by "accessable"?  What are we trying to accomplish?  How exactly is your network set up?

[Baffled]

Basically we have two domains (A & B). There is one server connected to domain B which is accessible by clients on domain A. However, the new server, if joined to domain B can be seen by clients on Domain A but when anyone tries to access it (i.e. open it up) they get a message saying "There are currently no logon servers available to service the logon request.". Anyone logged on to domain B can happily look at the servers contents. If I join the server to domain A then anyone logged into domain A can happily open up the server without any bother.

I was thinking that it may be a trust problem, but all the help stuff on trusts indicates that trust is between domains. The existsing server on domain B (an exchange server) is not experiencing any problems like this. So, I don't think it is a trust problem.

My question about Active directory is to see if this would solve the problem. But, I don't want to make this server a domain controller if I can help it.

Thanks

[Spoiler]

There are currently no logon servers available to service the logon request

What you have is a user in domain A trying to connect to a share in domain B. What is happening is the user in domain A tries to connect and domain B asks who are you and your machine says I am DOMAIN-A\user. Domina B returns nope I have no user called DOMAIN-A\user. Than it looks around and can't find any logon servers in Domain B so you get an error. There are currently no logon servers available to service the logon request

This has nothing to do with the machine being a DC or not.

If both machines are in the same forest or enterprise you can create a global group which can work across domains. Than put your user into the global group.

You can also try to login to the machine and make a account named the same as the user in the other domain. And than give the new account permission to the folder.

So you have a account called Bob in Domain B you need to create a used called Bob on the machine in Domain A Make sure that the passwords are the same and that you have logged into the machine once to create a profile.

Good luck....

[Baffled]

Thanks. This sounds great! I've been told to leave the server connected to domain A for now. In a short while, however, I'll be building another one which will definitely need to be in domain B. So, I'll need this solution then.

Once again, thanks loads.

[Spoiler]

Glad we could help....

Come back any time!