• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Server 2003 AD problem

daveshel

Diamond Member
(Posted to Networking Forum as well, but there doesn't seem to be anybody there.)

This one is giving me a slight cerebral hemorrhage.

I have a new Server 2003 AD domain with a single DC and 3 member servers. We are transitioning gradually from an NT4 domain, which is where our users still live. There is a trust between the domains.

I have made a domain local group in the AD domain, and populated it with several users from the NT4 domain. On the DC, I can add the DL group to the NTFS permissions for a shared folder. But on the member servers, the DL group is not available.

I'm thinking this must be a name resolution issue, but I cannot find anything wrong there.

TIA.
 
Are the member servers are part of the AD domain or nt domain?

On the member servers when you share something it might be defaulting to the local pc instead of the domain. Click on the locations button the right and pick the domain as the place to search for users/groups.

Share a folder, Shareing tab, Enter share name, click permissions button, click Add button, look at the "From This Location" section, it should point to your domain and not the local server name, if it doesn't list the domain click the Locations button and highlight the domain and click ok, then try to find your group.

-Or-

Make sure you are logging in as a domain user and not the local administrator of the member server, you can't (normally) enumerate group lists if you aren't authenticated.


-Teva24
MC-P/SE/SA/DBA 🙂
 
The member servers are in the AD domain. The NT domain was not available form the locations button.

I think I have resolved it. The DC was using an lmhosts file to identidy the PCD in the NT domain, and I copied that file to the member server.

Thanks.
 
Back
Top