<div>
Did you ensure that on the new server's NIC properties, the ONLY static DNS server address is the IP of your Windows 2000 Domain Controller? If you set this, I expect it will be able to join the domain.<br />
<br />
I will post the entire procedure for replacing the 2000 DC in a few moments.<br />
<br />
-tigermatt
</div>


<div>
Install Windows Server 2008 onto the new server which is intended to be promoted as a Domain Controller. Ensure the new server is assigned a routable static IP address on your IP subnet. Ensure the IP address is not included in any of your existing DHCP scopes. The only DNS server entry at this stage should be the IP address of the existing domain controller on your network. <br />
<br />
After installation, join the new machine to the existing domain as a member server. This procedure is exactly the same as joining a workstation to the domain. <br />
<br />
Since you are upgrading the Operating System on the new Domain Controller, you will need to add some values to the existing Active Directory schema, in order for the new server to become a Domain Controller. Windows Server 2008 supports more functionality than before, so a schema upgrade for the domain and forest is required to facilitate this and make this new feature set fully functional on the domain. To make the necessary changes, you must be logged on as the built-in Administrator user account, or a user with Domain, Schema and Enterprise Admin privileges. <br />
<br />
Insert the Windows Server 2008 media into your current server . Open a command prompt and browse to sources\adprep folder within the Windows Server 2008 DVD media. Execute the command adprep /forestprep. <br />
<br />
Next, execute adprep /domainprep . You must be logged on as a Domain Admin user for these steps to work correctly. Once these commands have run your Active Directory schema will have been extended to support Windows Server 2008 as a Domain Controller. <br />
<br />
Promote the new server as a Domain Controller for the domain. Enter dcpromo at a command prompt and follow the wizard. When prompted, select the option for an additional domain controller in an existing domain. After the wizard completes, the new server will be acting as a Domain Controller for your domain. It is necessary at this point to restart the server for these changes to be applied. <br />
<br />
In a single-domain Active Directory forest, all servers should also be Global Catalog servers. The Global Catalog is a required component of Active Directory which is used during logins to establish universal group membership for a user account. To promote the new server as a Global Catalog, open Active Directory Sites and Services from the Administrative Tools container within Control Panel or on the Start Menu. Double-click Sites, then Servers, followed by the name of the new server. Next, right-click &quot;NTDS Settings&quot; and select Properties. On the General tab, check the Global Catalog checkbox. Restart the new Domain Controller for changes to take effect. <br />
<br />
Since you intend on removing the old Domain Controller from the domain, you need to transfer all the Operations (FSMO) roles to the new Domain Controller. <br />
<br />
The current FSMO role configuration for your network can be found by running the command &quot;netdom query fsmo&quot; at a command prompt on a Domain Controller. <br />
<br />
To transfer these FSMO roles to the new domain controller, follow the information detailed in the following Microsoft Support article: <a href="http://support.microsoft.com/kb/324801" rel="ugc nofollow">http://support.microsoft.com/kb/324801</a>. Please ensure any other information you follow is information regarding the TRANSFER of FSMO roles. Seizing FSMO roles is an emergency operation which should not be performed during this procedure. <br />
<br />
DNS is a critical component of your Active Directory network. The easiest way to install the DNS role onto the new server is to follow the instructions outlined at <a href="http://technet2.microsoft.com/WindowsServer2008/en/library/3cf4d1b1-7a6e-4438-bf4f-22d9468c17321033.mspx" rel="ugc nofollow">http://technet2.microsoft.com/WindowsServer2008/en/library/3cf4d1b1-7a6e-4438-bf4f-22d9468c17321033.mspx</a>&nbsp;You should be already using Active Directory-integrated DNS zones, which is the easiest method of allowing DNS replication to occur - DNS information is stored in Active Directory and replicates with Domain Controller replication traffic. To check if your DNS zones are AD-integrated (and convert them if not), please follow <a href="http://support.microsoft.com/kb/227844" rel="ugc nofollow">http://support.microsoft.com/kb/227844</a>. <br />
<br />
You probably want to enable DNS forwarding in the DNS console on the server, too. This forwards lookups for external domains to a DNS server at your ISP, which allows the server to effectively resolve DNS for external domains. More information on forwarders can be found at <a href="http://technet2.microsoft.com/WindowsServer/en/Library/ee992253-235e-4fd4-b4da-7e57e70ad3821033.mspx" rel="ugc nofollow">http://technet2.microsoft.com/WindowsServer/en/Library/ee992253-235e-4fd4-b4da-7e57e70ad3821033.mspx</a>. <br />
<br />
To move DHCP to the new server, you will need to first install the role. To install the role in Windows Server 2008, check the DHCP Server role option within the Add Roles wizard in the Server Manager. To correctly configure DHCP after the role is installed on your new server, you will need to ensure you configure it to distribute IP addresses which are in a different range to the IP scope defined on the other DHCP server. You should also ensure the correct DNS and WINS servers are entered into the scope options. Remember that the only DNS servers which should be configured on workstations are the Domain Controllers which are also acting as DNS servers - no ISP DNS server should ever be set through DHCP. <br />
<br />
Once all of these steps have been completed, you should have successfully transferred all of the Active Directory roles to the new domain controller. At this stage, I would suggest you shut down the old domain controller and check to ensure all services on workstations and servers are working correctly - including logins. If they are, you should be safe to switch the old DC back on, run dcpromo and demote it from its Domain Controller role. This will remove the DC as a Domain Controller, leaving it as a member server on the network. <br />
<br />
To completely remove the DC from the network, you will need to remember that any other data - including folder redirection folders and user profiles - should be replicated or otherwise transferred to either the new server or another location on the network. ROBOCOPY is useful for doing this file transfer because it can also copy over the NTFS ACLs along with the files.<br />
<br />
-tigermatt
</div>


<div>
On my new server under NIC properties, for tcp/ipv4 my only DNS server is that of the exsting server. &nbsp;It's on the general tab and on the DNS tab when I click advanced. &nbsp;I also have tcp/ipv6 installed by default. &nbsp;Is that causing any problems being there? &nbsp;Is it ok to leave it since I'm not using v6?
</div>


<div>
I would try disabling IPv6 and then see what happens - it could be causing a conflict or something.
</div>


<div>
The uninstall button is grayed out but I unchecked the box bedside tcp/ipv6. &nbsp;Still same result - network path not found.
</div>


<div>
I have continued to search the internet and this site to find a solution. &nbsp;I have followed your suggestions above. &nbsp;Other pc's on my network can leave and join the domain with no problems. &nbsp;Windows firewall is turned off. &nbsp;This server is an HP Proliant ML150 that came with Server 2008 preinstalled. &nbsp;Should I try a fresh install? &nbsp;At this point I'm grasping at straws here. &nbsp;This is very frustrating.
</div>


<div>
What about the firewall? Try disabling Server 2008's Advanced Windows Firewall through Server Manager. That should make a difference. <br />
<br />
In a networked environment with a hardware firewall, it isn't really necessary to have software firewalls enabled on servers anyway - they cause more problems than they solve.<br />
<br />
-tigermatt
</div>


<div>
I missed your last comment in which you stated the firewall was disabled. Apologies. I didn't refresh often enough.<br />
<br />
The suggestions I've posted above are all the standard ones which always solve this problem. At this point, I would be reinstalling (I would have done it a lot earlier, actually!). Try to join the domain as soon as the server comes up, (after disabling the firewall and setting a static IP, though). That will give best chances of success.<br />
<br />
-tigermatt
</div>


<div>
Thanks for your help on this...<br />
The firewall on both servers is off.<br />
I had a few roles installed on server 2008 before - I just removed all roles from the server but it didn't seem to matter - still same error. &nbsp;Are there certain roles that need to be added to join a domain?<br />
I have renamed the server. &nbsp;I have tried to add it into the AD computers list on the server 2000 server. &nbsp;Still no luck. &nbsp;It has to be unique to server 2008 too, since other xp desktops can join the domain with no errors. &nbsp;Am I correct to assume that?
</div>


<div>
ok - I will reinstall and post results soon. &nbsp;thanks.
</div>


<div>
formatted hard drive - reinstalled from the dvd. &nbsp;set ip and dns in network properties. &nbsp;turned firewall off. &nbsp;tried joining domain - &quot;The network path was not found.&quot;
</div>


<div>
Ok, could you post a complete ipconfig /all output from both the Domain Controller and the 2008 Server? Also, I assume the server is able to ping the Server 2000 server, access its resources after entering credentials, etc.?
</div>


<div>
I will post the ipconfig /all when I get back to the server. &nbsp;That's correct - I can ping (both servers, both ways) and I have even shared folders and copied files to each server from each server. &nbsp;So, there is connectivity - just no joining of the domain.
</div>


<div>
this is from the windows 2000 server - the default gateway is our dsl modem.<br />
C:\Documents and Settings\Administrator&gt;ipc<wbr />onfig /all<br />
<br />
Windows 2000 IP Configuration<br />
<br />
&nbsp; &nbsp; &nbsp; &nbsp; Host Name . . . . . . . . . . . . : gator<br />
&nbsp; &nbsp; &nbsp; &nbsp; Primary DNS Suffix &nbsp;. . . . . . . : gatewood.gatewoodschool.co<wbr />m<br />
&nbsp; &nbsp; &nbsp; &nbsp; Node Type . . . . . . . . . . . . : Hybrid<br />
&nbsp; &nbsp; &nbsp; &nbsp; IP Routing Enabled. . . . . . . . : No<br />
&nbsp; &nbsp; &nbsp; &nbsp; WINS Proxy Enabled. . . . . . . . : No<br />
&nbsp; &nbsp; &nbsp; &nbsp; DNS Suffix Search List. . . . . . : gatewood.gatewoodschool.co<wbr />m<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; gatewoodschool.com<br />
<br />
Ethernet adapter Local Area Connection:<br />
<br />
&nbsp; &nbsp; &nbsp; &nbsp; Connection-specific DNS Suffix &nbsp;. :<br />
&nbsp; &nbsp; &nbsp; &nbsp; Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet<br />
&nbsp; &nbsp; &nbsp; &nbsp; Physical Address. . . . . . . . . : 00-02-55-56-1E-13<br />
&nbsp; &nbsp; &nbsp; &nbsp; DHCP Enabled. . . . . . . . . . . : No<br />
&nbsp; &nbsp; &nbsp; &nbsp; IP Address. . . . . . . . . . . . : 192.168.1.3<br />
&nbsp; &nbsp; &nbsp; &nbsp; Subnet Mask . . . . . . . . . . . : 255.255.255.0<br />
&nbsp; &nbsp; &nbsp; &nbsp; Default Gateway . . . . . . . . . : 192.168.1.254<br />
&nbsp; &nbsp; &nbsp; &nbsp; DNS Servers . . . . . . . . . . . : 192.168.1.3<br />
&nbsp; &nbsp; &nbsp; &nbsp; Primary WINS Server . . . . . . . : 192.168.1.3
</div>


<div>
That looks all in order. Can you get one from the server 2008 server?
</div>


<div>
This is from windows 2008 server:<br />
<br />
C:\Users\Administrator&gt;ipc<wbr />onfig /all<br />
<br />
Windows IP Configuration<br />
<br />
&nbsp; &nbsp;Host Name . . . . . . . . . . . . : WIN-F88NZZHSHGH<br />
&nbsp; &nbsp;Primary Dns Suffix &nbsp;. . . . . . . :<br />
&nbsp; &nbsp;Node Type . . . . . . . . . . . . : Hybrid<br />
&nbsp; &nbsp;IP Routing Enabled. . . . . . . . : No<br />
&nbsp; &nbsp;WINS Proxy Enabled. . . . . . . . : No<br />
<br />
Ethernet adapter Local Area Connection 2:<br />
<br />
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. :<br />
&nbsp; &nbsp;Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet<br />
&nbsp; &nbsp;Physical Address. . . . . . . . . : 00-21-5A-BC-C4-E9<br />
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No<br />
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes<br />
&nbsp; &nbsp;Link-local IPv6 Address . . . . . : fe80::5cf5:b0fa:8f77:3b00%<wbr />15(Prefer<br />
&nbsp; &nbsp;IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)<br />
&nbsp; &nbsp;Subnet Mask . . . . . . . . . . . : 255.255.255.0<br />
&nbsp; &nbsp;Default Gateway . . . . . . . . . : 192.168.1.254<br />
&nbsp; &nbsp;DNS Servers . . . . . . . . . . . : 192.168.1.3<br />
&nbsp; &nbsp;Primary WINS Server . . . . . . . : 192.168.1.3<br />
&nbsp; &nbsp;NetBIOS over Tcpip. . . . . . . . : Enabled<br />
<br />
Tunnel adapter Local Area Connection* 8:<br />
<br />
&nbsp; &nbsp;Media State . . . . . . . . . . . : Media disconnected<br />
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. :<br />
&nbsp; &nbsp;Description . . . . . . . . . . . : Microsoft Tun Miniport Adapter<br />
&nbsp; &nbsp;Physical Address. . . . . . . . . : 02-00-54-55-4E-01<br />
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No<br />
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes<br />
<br />
Tunnel adapter Local Area Connection* 9:<br />
<br />
&nbsp; &nbsp;Media State . . . . . . . . . . . : Media disconnected<br />
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. :<br />
&nbsp; &nbsp;Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2<br />
&nbsp; &nbsp;Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0<br />
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No<br />
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes<br />

</div>


<div>
Another thing to note - from the new 2008 server I can browse the network just fine. &nbsp;See all other computers and printers. &nbsp;Just can't join the domain.
</div>


<div>
Two suggestions: is NetBIOS over TCP/IP enabled on the Windows 2000 server's NIC? (Advanced TCP/IP properties, WINS tab I think).<br />
<br />
Do you have any other roles installed on the Server 2008 at the present time?
</div>


<div>
BetBios over TCP/IP is enabled on the 2000 server. &nbsp;No roles are installed on the 2008 server since the reinstallation yesterday.
</div>


<div>
Sorry - should have typed NetBios
</div>


<div>
OK, I've not got many more suggestions. I seem to remember an issue back along regarding SMB. Please check to see if SMB 1.0 is enabled on the Server 2008 machine; if it is, try temporarily disabling it. I doubt this will work, but it might have some effect.<br />
<br />
More info at <a href="http://blogs.technet.com/askperf/archive/2008/05/30/two-minute-drill-overview-of-smb-2-0.aspx" rel="ugc">http://blogs.technet.com/askperf/archive/2008/05/30/two-minute-drill-overview-of-smb-2-0.aspx</a>.<br />
<br />
-tigermatt
</div>


<div>
Issued these commands to disable SMB on 2008 server.<br />
sc config lanmanworkstation depend= bowser/mrxsmb20/nsi <br />
sc config mrxsmb10 start= disabled<br />
Tried to join domain.<br />
Still same error.
</div>


<div>
I'm really running out of ideas now. Have you got another server (even an old workstation) you could just try installing Server 2008 to, in order to verify it's not a hardware issue with the particular server you're installing this to? It's highly unlikely, but we need to rule it out.<br />
<br />
-tm
</div>


<div>
And before you do that, can you try inserting the correct DNS suffix in your NIC settings. I just noticed that was missing on the 2008 Server's IPCONFIG output.
</div>


<div>
I could find a different box to install server 2008 on probably. &nbsp;I just added the DNS suffix under advanced in the NIC settings and under system properties where you can change the computer name. &nbsp;No luck. &nbsp;I renamed the server to see if that would make any difference at all. &nbsp;After turning the firewall off and enabling file sharing again - I can't browse other computers on the network. &nbsp;I can still ping them, including the 2000 server. &nbsp;But none show up in the network browser window. &nbsp;Strange. &nbsp; &nbsp;
</div>


<div>
What domain (exactly) are you entering when you go and join the server to the domain?
</div>


<div>
At first I was trying the same thing that I use to join all other pc's to the domain, which is gatewood. &nbsp;Over the past two days I have tried other combinations of gatewood.gatewoodschool.co<wbr />m, gatewoodschool.com, gator.gatewood.gatewoodsch<wbr />ool.com, of course having no luck with any of these. &nbsp;The only one that even prompts me to enter my login credentials is when I simply use gatewood. &nbsp;I have tried upper and lower case just to see if that made a difference. &nbsp;Obviously it does not.<br />
Thanks
</div>


<div>
It isn't running in VMWare, is it? <a href="https://www.experts-exchange.com/questions/23443176/Unable-to-join-a-Win2008-server-to-a-Windows-2008-Domain.html" rel="ugc">https://www.experts-exchange.com/questions/23443176/Unable-to-join-a-Win2008-server-to-a-Windows-2008-Domain.html</a>
</div>


<div>
No, no VMware going on. &nbsp;Just a straight forward server install. &nbsp;I tried creating a new domain - promoting the 2008 server then demoting it and trying to join my 2000 domain with no success. &nbsp;I'm reinstalling again this morning and wil try again.<br />
Thanks.
</div>


<div>
Failing that, just try it on another workstation, if possible with a different network cable and different port on your switch. It sounds silly because everything else works perfectly fine, but Active Directory is weird sometimes!
</div>


<div>
You're right - at this point it is silly. &nbsp;I will try to install in another workstation, switch cables and ports and post my results soon. &nbsp;Thanks again for your help. &nbsp;I have continued to scour the web looking for solutions - all to no avail.
</div>


<div>
I have tried to install server 2008 on two other boxes but both do not meet the requirements and the install stalls. &nbsp;I changed out the network cable and plugged into another port on my switch. &nbsp;I have reinstalled the OS from the DVD for the 2nd time now. &nbsp;Everthing thing I read simply says to use static ip and make your network private instead of public on the setup screen and everything should be fine. &nbsp;A few people say they had to turn the firewall off. &nbsp;I have done all of the above (again) and continue to get the Network Path was not Found Error. &nbsp;Any other ideas?
</div>


<div>
Should I just create a domain and set up the new server from scratch? &nbsp;Recreate all user accounts and copy all home directories over to the new server? &nbsp;That would have taken less time that I have spent on this so far.
</div>


<div>
It might be easier, provided you're willing to go to the hassle of doing a migration. As you can see I'm pretty much out of suggestions - do you have the NIC drivers installed correctly?
</div>


<div>
One thing that I have been sort of ignoring and not thinking about is the fact the the windows update service had been failing and not downloading or installing any updates. &nbsp;I chose to ignore this until later because I didn't think that it would make any difference sine this is a new server and most updates have to do with security related issues anyway. &nbsp;I read on bleepingcomputer.com that there was a newer version available at <a href="http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.1.6001.65/WindowsUpdateAgent30-x86.exe" rel="ugc">http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.1.6001.65/WindowsUpdateAgent30-x86.exe</a>. &nbsp;I installed the newer version - 13 updates (I think) were available and they downloaded and installed automatically. &nbsp;The server restarted. &nbsp;Tried to join the domain. &nbsp;Failed again.<br />
I can still ping the 2000 (DNS) server and ping the 2008 server from the 2000 server. &nbsp;I can share files back and forth. &nbsp;I'm going to struggle for one more day and then I'll move on. &nbsp;Any suggestions are much appreciated.
</div>


<div>
So the server is now up-to-date ?<br />
<br />
Something I've just thought of is the possibility that there isn't anything wrong with the server but with Active Directory - have you tried recently to remove another station from the network and rejoin it?
</div>


<div>
The server now has all the security patches, etc. &nbsp;<br />
I thought the same thing earlier in the week. &nbsp;On Tuesday I was able to remove and add another workstation to the domain successfully. &nbsp;I also set up a new pc and joined it to the domain with no problem. &nbsp;This network is such a simple straight forward design, I had no idea I would have this much trouble adding a new server.
</div>


<div>
Have you run the ADPrep from the Server 2008 CD on your existing server? It should only be necessary when you promote the server to Domain Controller, but as I said before, you never know what strange things could be going on!
</div>


<div>
Well tigermatt...<br />
I ran adprep /forest then adprep /domainprep /gpprep - they ran successfully (after having to configure my server to run in native mode instead of mixed). &nbsp;Still no luck joining the domain. &nbsp;I have restarted everything many times, changed cables, changed switches. &nbsp;I had no idea this would be so complicated and time consuming. &nbsp;If you have no other suggestions, I think I'm just going to dcpromo my new server, create a new domain, and start setting up my ad users all over again. &nbsp;The school only has about 65 users I think, so it would have been a lot quicker to do that from the beginning anyway. &nbsp;I'll wait for your next comment before closing this question and moving on.<br />
Thanks.
</div>


<div>
Either way, I will award you the points for all of your time.
</div>


<div>
I dcpromo'ed my 2008 server this morning and realized I lost connectivity with the 2000 server. &nbsp;I could no longer &quot;see&quot; the old server and the files on it. &nbsp;And I was thinking that if I have all users log into a new domain I bet I will have to reconfigure all of their desktop settings and shortcuts and all of that stuff too. &nbsp;That would be a larger job that I want to get into at this point. &nbsp;So, I demoted it back. &nbsp;Made sure I could copy a few files back and forth, and now I'm searching the HP and Microsoft sites for anything helpful I can find. &nbsp;I also found an update for the Intel chipset (ICH9) that I have and installed it, but it didn't help either. &nbsp;The solution to this problem is going to be one of those off the wall things that usually happens to me. &nbsp;I feel like I can find a solution somewhere. &nbsp;I will leave this question open another day or two if you want to seuggest anything else.<br />
Thanks for all your help, and the ADMT suggestion above.
</div>


<div>
This is still incredibly strange for me, and I've no idea what is actually causing this. I don't suppose you ever got around to finding a workstation which can support Server 2008, and installing just to verify whether it's an issue with the network or this particular server?
</div>


<div>
I just tried to install it on a third system here and it says it's not supported for this platform or something to that effect. &nbsp;The one I just ttried is a new workstation too, I'm not sure where the deficiency is. &nbsp;This is a strange one for me too. &nbsp;I have almost 20 years of experience in the IT field and I rarely get stumped like this.<br />
Thanks again.
</div>


<div>
Sorry I can't help any further, there must be some compatibility issue between that station and Server 2008 - its System Requirements are quite picky!<br />
<br />
If you find anything else, please let me know :-)
</div>


<div>
I've been going back and forth with HP support for the last two days. &nbsp;They sent me updated drivers for the NIC and chipset and network config utility. &nbsp;Nothing helped. &nbsp;Too bad I can't install it anywhere else to test out my network. &nbsp;Thanks again for all the suggestions.
</div>


<div>
Looks like I'll be starting over form square one!
</div>


<div>
I hope you get this tigermatt...<br />
I finally got a system that would handle my server 2008 install. &nbsp;Tried to join domain - same result. &nbsp;Took server to another location - server 2003 domain - joined domain successfully. &nbsp;Looked at that server's DNS setup and compared it to my server 2000 DNS setup and they are very different. &nbsp;I set up both servers and I know I didn't manually enter the DNS records on the 2003 server. &nbsp;<br />
So now it seems all arrows are pointing to DNS as my main problem although it's strange that all my workstations have no problem with it and server 2008 does.
</div>


<div>
New question with new findings - <a href="https://www.experts-exchange.com/questions/23610701/Windows-2008-will-not-join-Windows-Server-2000-domain.html" rel="ugc">https://www.experts-exchange.com/questions/23610701/Windows-2008-will-not-join-Windows-Server-2000-domain.html</a>
</div>


<div>
At least you have finally managed to determine that the problem is not with the Server 2008 hardware but an issue on the network. That was the clarification which we needed all along, in order to know where the issue was.<br />
<br />
I will subscribe to that question, but it looks like Chris, our resident DNS expert, is already on the trail of the problem with you.<br />
<br />
Hope it sorts itself out pretty soon. :-)<br />
<br />
Matt
</div>


<div>
<div class="content wysiwyg-content">
I have a server 2000 server that is PDC on a small network. &nbsp;It is the DHCP, DNS, and WINS server. &nbsp;DNS points to it's own static IP address. &nbsp;I have read, tried and had no luck with many suggestions on this site and many others since installing a new server 2008 server last week. &nbsp;I would like to eventually promote my new server to be the PDC, move AD from old server to new, and demote the old server to be just a member server. &nbsp;My immediate issue is that I can't get the server 2008 to join the domain. &nbsp;I have both servers plugged into the same switch, sitting side by side. &nbsp;They can each &quot;see&quot; each other, meaning I can browse files and run programs on each. &nbsp;But when I go to join the domain, I enter my usrname and password (admin security), it hourglasses for a few seconds, and then says the following error occurred attempting to join the domain. &nbsp;The network path was not found. &nbsp;I've tried renaming the server to a short simple name. &nbsp;No Luck. &nbsp;Again, I have spent hours trying to joing the domain. &nbsp;There are no other servers on my network. &nbsp;Thanks.
</div>
</div>


I have a server 2000 server that is PDC on a small network.  It is the DHCP, DNS, and WINS server.  DNS points to it's own static IP address.  I have read, tried and had no luck with many suggestions on this site and many others since installing a new server 2008 server last week.  I would like to eventually promote my new server to be the PDC, move AD from old server to new, and demote the old server to be just a member server.  My immediate issue is that I can't get the server 2008 to join the domain.  I have both servers plugged into the same switch, sitting side by side.  They can each "see" each other, meaning I can browse files and run programs on each.  But when I go to join the domain, I enter my usrname and password (admin security), it hourglasses for a few seconds, and then says the following error occurred attempting to join the domain.  The network path was not found.  I've tried renaming the server to a short simple name.  No Luck.  Again, I have spent hours trying to joing the domain.  There are no other servers on my network.  Thanks.

Need Help Joining Server 2008 to Domain

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 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.