Cant identify Windows domain without the '.com'
Hello,
When joining PC's to my network, I can only verify my domain if i type domain.com rather than just domain. On previous networks I have worked on you can do either. I presume I need to change something in DNS? Does anybody know what needs to be changed?
Thanks.
When joining PC's to my network, I can only verify my domain if i type domain.com rather than just domain. On previous networks I have worked on you can do either. I presume I need to change something in DNS? Does anybody know what needs to be changed?
Thanks.
ASKER
DNS works fine for everything, and its not causing any problems, its just the adding to the domain with netbios name that doesn't work. I will have a look at your solution and get back.
It actually doesn't matter how you join the machine to the domain, because even if you join it using the NetBIOS name, the client will from then on use exclusively DNS to find a DC.
For NetBIOS resolution to work reliably (and to prevent clogging your network with NetBIOS broadcasts), you'll need a WINS server.
And just in case, check the maybe way too obvious reason: is the NetBIOS domain name actually "domain" at all? The NetBIOS name is in no way related to the AD domain name, you can have an AD DNS domain name of microsoft.com and a NetBIOS name of LINUX.
Open a command prompt on the DC or a domain member and enter "set %userdomain%" to check the NetBIOS name.
For NetBIOS resolution to work reliably (and to prevent clogging your network with NetBIOS broadcasts), you'll need a WINS server.
And just in case, check the maybe way too obvious reason: is the NetBIOS domain name actually "domain" at all? The NetBIOS name is in no way related to the AD domain name, you can have an AD DNS domain name of microsoft.com and a NetBIOS name of LINUX.
Open a command prompt on the DC or a domain member and enter "set %userdomain%" to check the NetBIOS name.
ASKER
I have the domain correct, but I do not have a WINS server. Is this necesary to utilise this? As I say its not something I am too bothered about. What I am bothered about is if it means an actual problem will rear its ugly head in the future. I took a lot of time and preparation/research before setting up DNS, and so far a year has gone by with it working perfectly, so I am sure its fine...
If you have NetBIOS over TCP/IP enabled on your machines, then you should have a WINS server (or two with Push/Pull replication) as well; otherwise you'll have lots of completely unnecessary NetBIOS broadcasts in your network, and you won't be able to resolve a NetBIOS name (like the domain name) over subnet boundaries.
ASKER
Ok I will configure WINS and see if that helps. Does it matter its its the same server as the DNS server?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In short: *all* domain members may *only* use DNS servers that re authoritative for your AD DNS name; routers or external DNS server (from the ISP, for example) may *not* appear in the TCP/IP settings of any domain member (including the DCs). In a usual setup, this means that only the DC(s) may provide DNS services for AD members. Configure forwarders on your DNS servers to forward external requests to your ISP, or simply rely on the root hints.
Details here:
10 DNS Errors That Will Kill Your Network
http://redmondmag.com/features/article.asp?EditorialsID=413
Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382
Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/?kbid=825036