Assign win2k domain users to Win2k3 server

[Haim]

I have set up a win2k3 machine on my win2k domain to act as a
webserver. I would like to add domain users and groups to the acls on
the server. (file permissions, IIS permissions, sql logons etc.).
While the network explorer shows all the computers in the network, and I
am able to log into the domain, I am unable to assign domain users
permissions to server objects. The dialog box asks for locations and
only shows the local machine.

Please this is a pressing matter as the machine is useless unless I can
assign domain users.

Haim

 

[Marin Marinov]

<snip>
Is the machine a member of the domain? If so, you should be able to list
domain accounts by selecting the "Browse..." button when adding users in
the "Select Users or Groups" dialog and select your domain. If the
machine is not joined to the domain, you cannot grant permissions to
domain accounts.

HTH
--
Cheers,
Marin Marinov
MCT, MCSE 2003/2000/NT4.0,
MCSE:Security 2003/2000, MCP+I
-
This posting is provided "AS IS" with no warranties, and confers no
rights.

 

[Haim]

Dear Marin,
Thank you for the reply. I joined the machine to the domain using the
wizard. When I log onto the machine, it allows me to log on as a domain
user. But the "Browse ..." button only allows me to browse the local
machine and not the domain. It doesn't matter if I'm logged on as a
local administrator or domain administrator, I still cannot 'browse' the
domains users.

Haim

 

[Haim]

I finally solved the problem. I had to list the domain server's address
as one of my dns servers. This is not necessary for my win2k and winxp
machines.

Haim

 

[Marin Marinov]

I finally solved the problem. I had to list the domain server's address
as one of my dns servers. This is not necessary for my win2k and winxp
machines.

Haim

<snip>
Don't know your exact setup but without pointing to a DNS server that
can successfully find and resolve SRV records for a DC your clients will
not be able to find a domain controller and authenticate successfully.
You should make sure that your DNS infrastructure is properly configured
so all domain members (and domain controllers) point to an internal DNS.
Always remember that DNS is a foundation for AD - no DNS, no AD

I'm glad to hear you solved your problem
--
Cheers,
Marin Marinov
MCT, MCSE 2003/2000/NT4.0,
MCSE:Security 2003/2000, MCP+I
-
This posting is provided "AS IS" with no warranties, and confers no
rights.