Name Resolution Issue 1

[mugs82]

I have an NT 4.0 domain. We our primary dns server is a Windows 2000 member server. Sometimes, when a client tries to connect to a host, the only way we can connect to it is by using the fully qualified domain name. Like when mapping a drive you have to type in host.domain.com. Other times, you can just type the host name. This makes no sense to me. Can anyone tell me what's happening and how to correct the issue?

 

[GregDarby]

Hi,

I am assuming you mean the clients that request the name resolution are on the same Lan / Wan?

If you need to resolve machine names 2 options are:

1) - Create hosts files on each machine (take too long)
2) - Run a WINS Server and setup WINS on each box.

Easy..


Regards,

Greg

 

[mugs82]

I should have told you, I am also running WINS on that same box. Host files are not an option....

 

[Claudek]

A few things, Am assuming you have Win2k Pro clients, though the setting apply to Xp and Win NT 4.0 clients as well.

For the clients that are having issues:

In win2k pro, right-click My Computer, Properties, Computer Name, Change, More. Make sure your Primary DNS suffix is configured properly.


Now navigate to TCP/IP properties on the client. Click Advanced, DNS.
In the DNS server addresses, in order of use, your internal DNS server should be listed first. The "Append primary and connection specific DNS suffixes" should be selected as should the checkbox "Append parent suffixes of the primary DNS suffix"

Hope that helps - If the dns suffix is not correct or not defined properly you can only connect using fully qualified domain name. If it is configured properly, you can connect just using host name.




Claudius (What certifications??)

http://www.iteq.com.au

 

[mugs82]

Thanks Claudius - I'll let you know what I find.