In
I decided to go the easy route, and rename my network
appliance filer to a new name, and add it to the network.
When it tries to add the computer account, the filer
gives me an error that says:
DNS is not properly configured for windows 2000
operation, cannot resolve simple domain (domain) to
(domain.int)
My DNS server appears to be running fine, no probs with
any other devices, only this netapp, any ideas?
Basically, if you follow the golden rule with AD and DNS, never use any
other DNS server IP address in any machine IP properties other than the
internal DNS server/servers that is/are hosting your AD zone. The only place
to reference an external DNS is by configuring a forwarder in DNS properties
to your ISP's DNS.
Now, if your network configuration follows the rules above, what exactly are
the Netlogon error you are receiving? Usually following the above rule, you
won't get errors as such, unless there are other factors going on, such as a
single label domain name, multihomed DCand.or DNS server, missing Primary
DNS Suffix, etc.
If you can post the Event ID error #s and an unedited ipconfig /all and your
AD DNS domain name, that can give us a good start to help diagnose this for
you.
Thanks!
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.
This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.