PvilleStang
In Runtime
- Messages
- 152
- Location
- Republic of Texas
So I'm working on a domain that has two DC's, one (hosting DNS and DHCP) being a mac server, one (hosting DNS and Domain) being a Win Server 2003 Std. box. Here's the big issue I'm having and haven't seen before.
I ping SERVER, it responds. I statically route the Domain server to SERVER, and nslookups resolve all names, including SERVER, just fine on the workstation. I go to Start > Run and type in "\\SERVER" and the server is not found. I cannot add the workstation to the domain because it is unable to see the domain controller. If I add to DOMAIN.local, it asks for the account with authorization to add to the server, and then returns an error saying "The network path was not found". Now if I add it to just DOMAIN, it returns "A Controller for the domain DOMAIN could not be contacted," without prompting even for a user / pass. What am I missing here?
P.S.
I ping SERVER, it responds. I statically route the Domain server to SERVER, and nslookups resolve all names, including SERVER, just fine on the workstation. I go to Start > Run and type in "\\SERVER" and the server is not found. I cannot add the workstation to the domain because it is unable to see the domain controller. If I add to DOMAIN.local, it asks for the account with authorization to add to the server, and then returns an error saying "The network path was not found". Now if I add it to just DOMAIN, it returns "A Controller for the domain DOMAIN could not be contacted," without prompting even for a user / pass. What am I missing here?
P.S.