<div>
is the problem on this machine only, or an all of them?<br />
<br />
what happens is you issue a nslookup &lt;servername&gt; command where servername is a server on your network?<br />
<br />
are you going though s firewall? (if so open ports in this order TCP53 UDP53)<br />
<br />
is DNS running on the server (start &gt;run &gt;cmd &gt;net start {enter} )<br />
<br />
if youve done all of this (and the DNS entry in the TCP settings of the client is correct)<br />
put in the IP of your doamin controller as the secondary DNS
</div>


is the problem on this machine only, or an all of them?

what happens is you issue a nslookup <servername> command where servername is a server on your network?

are you going though s firewall? (if so open ports in this order TCP53 UDP53)

is DNS running on the server (start >run >cmd >net start {enter} )

if youve done all of this (and the DNS entry in the TCP settings of the client is correct)
put in the IP of your doamin controller as the secondary DNS

<div>
<div class="content wysiwyg-content">
Hello.. im working on this windows 2000 workstation and for some reason the dns isnt working.. the dns is setup correctly and i can ping the servers but it wont resolve ips.. any thoughts?
</div>
</div>


Hello.. im working on this windows 2000 workstation and for some reason the dns isnt working.. the dns is setup correctly and i can ping the servers but it wont resolve ips.. any thoughts?

windows 2000 workstation dns problem

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.