<div>
Hi,<br />
They need to do a ipconfig /flushdns on their machine<br />
Also they can test nslookup to see if they are getting the right IP for the Old DC, as you have already confirmed that they are able to ping to IP hence a DNS issue.<br />
Also, you can put old DC entry in their Host File<br />
Thanks<br />
Nitin<br />

</div>


<div>
I did the ipconfig /flushdns.<br />
Did not work.<br />
<br />
Where is their Host File located?<br />
thx.<br />

</div>


<div>
c:\WINDOWS\system32\driver<wbr />s\etc
</div>


<div>
Maybe Pix don't let pass RPC connections and traffic to the ip address of w2k server.<br />
<br />
Try to look at pix's config. If you can use shares on the other servers than Pix can have exceptions to permit this.<br />
<br />
To be sure that w2k server works fine try to connecto to \\servername from a pc in your lan.<br />
<br />

</div>


<div>
Thank you.<br />
<br />
500 points for such simple thing is too few.<br />
So, I owe a beer.<br />
<br />

</div>


<div>
<div class="content wysiwyg-content">
Urgent please.<br />
<br />
<br />
I demoted my Win 2K domain controler last weekend.<br />
Users could log in and all drives from servers were correctly mapped within the same subnet as the old and new DC (Win 2003 Std). (10.130.61.x)<br />
<br />
However, users from 'accross' the street connected through CISCO pix, on a different subnet (10.130.62.x) don't get mappins of the old DC, however they get mapped drives from three other servers on the .61.x subnet.<br />
The old DC Win 2K was a DHCP and DNS server.<br />
<br />
Trying to connect to it throuh \\[servername] give an error Path not found.<br />
<br />
Pinging the old Win 2K server from those workstations works fine.<br />
DNS settings (hard entry on workstations) point correctly to the new DC and another <br />
<br />
Any ideas what whould the reason be?<br />
<br />

</div>
</div>


Urgent please.


I demoted my Win 2K domain controler last weekend.
Users could log in and all drives from servers were correctly mapped within the same subnet as the old and new DC (Win 2003 Std). (10.130.61.x)

However, users from 'accross' the street connected through CISCO pix, on a different subnet (10.130.62.x) don't get mappins of the old DC, however they get mapped drives from three other servers on the .61.x subnet.
The old DC Win 2K was a DHCP and DNS server.

Trying to connect to it throuh \\[servername] give an error Path not found.

Pinging the old Win 2K server from those workstations works fine.
DNS settings (hard entry on workstations) point correctly to the new DC and another 

Any ideas what whould the reason be?



Several workstations not mapping shares on demoted DC / File Server

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.