Trouble Listing OS X Computer under Server 2003 Domain

When I was using NT server, I could get my mac to list on my domain "DIGITAL"

This is not a file sharing issue, its getting it to list under the network directory.  The new domain under server 03 is "company.local" (company is actually the name of my company, but we wil lcall it that for annonomy reasons).

It still is being listed under DIGITAL, while all other computer are under company.local

I have changed the SMB workgroup to "Company" so I can see and share files with others on the network

Directory access wont let me set up the AD settings, "invalid forest domain combination...blah blah"  I dont have a forest name, only company.local...

Any thoughts?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew DuffyTechnical Services CoordinatorCommented:
Firstly, which version of OS X are you using (I would assume Panther but because of the major differences between the versions it's helpful to know).

PacFuAuthor Commented:
Andrew DuffyTechnical Services CoordinatorCommented:
This could be a silly question but it's worth checking - under Sharing in the System Preferences, what domain name is displayed next to the computer name (by the Edit... button)?
PacFuAuthor Commented:
go find one of your AD admins and have him/her help you with the AD binding in Directory Access... you maybe don't have Domain Admin rights to join your machine to the domain.

if you're still getting invalid domain errors then you get to go down the long road of confirming that DNS is properly happening on your network...

btw there was all that stuff earlier this year about not being able to bind into "xxx.local" domains because ".local" was not really a valid domain naming entry... i think that got fixed with 10.3.4 or .5 or something so it may not be a problem for you

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Mac OS X

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.