Computing.Net > Forums > Windows Server 2003 > Network path not found

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Network path not found

Reply to Message Icon

Name: TbG
Date: October 24, 2007 at 15:12:42 Pacific
OS: Server 2003 R2
CPU/Ram: 1ghz p4/512
Product: Dell Optiplex GX150
Comment:

Alright, here is some information about the setup I have now:
I have a Intel Dual Core w/ 4GD RAM and 500GB of HDD space. The computer can handle anything Virtual you need.
I am setting up a network to test a lot of my schoolwork on (I am studying for Various MCPs and MCSA). Although I may be a little early to try to start setting this all up without any manual or anything, I want to have a head start on just about everything we’re going to cover in class, and so I can come home and experiment.
Right now, from my Uni, I have a copy of Server 2k3 Enterprise Edition R2, and WinXP SP2. Both OS’s are installed in the newest version of VMWare server, and have installed perfectly. But I have a small issue:
When a client (WinXP) tries to join a domain, I get the error:
“The Network Path Was Not Found”
I have changed the TCP/IP settings on the client side to reflect the servers IP address (in this case, 10.0.0.2). I can ping the domain (in this case, tbg.local) and it resolves to the IP and replies). I can ping the IP address, and it replies. I can also do it from the Server, as well.
The client and server both have their firewalls off. The server’s DNS settings are pointed to itself (10.0.0.2).
I’ve done a reasonable amount of google/technet/MS searching and I cannot find a solution that will work. I’m pretty much at a loss.
I’ve setup a domain before, but for some reason this one is kicking my ass.



Sponsored Link
Ads by Google

Response Number 1
Name: paulsep
Date: October 25, 2007 at 07:41:38 Pacific
Reply:

How are you trying to join the domain?
When you're asked for the domain you want to join,
are you using the server name or the domain name?

You must use the domain name!


0

Response Number 2
Name: Jennifer SUMN
Date: October 25, 2007 at 08:13:43 Pacific
Reply:

Yes. What exactly are you typing, and are you attempting to authenticate with a Domain Administrator account?

Life's more painless for the brainless.


0

Response Number 3
Name: TbG
Date: October 25, 2007 at 09:44:22 Pacific
Reply:

I right click on my computer >> properties >> go to computer name tab >> click the change button then click the Domain radio button.

In the text field under domain I put "tbg.local" and click ok. When the Username/Password box comes up, I put my user/pass that is set for Admin, Domain Admin, and Schema Admin so I think I've covered all the bases there.

I get the error after a few moments of waiting to join the domain.

And for future reference the server name is SERVER.


0

Response Number 4
Name: Jennifer SUMN
Date: October 25, 2007 at 09:54:10 Pacific
Reply:

Are you typing in tbg.local\username?

Life's more painless for the brainless.


0

Response Number 5
Name: TbG
Date: October 25, 2007 at 10:07:45 Pacific
Reply:

No, I am not. When I try that I get the same error.


0

Related Posts

See More



Response Number 6
Name: Jennifer SUMN
Date: October 25, 2007 at 15:48:24 Pacific
Reply:

You said in your original post "I can ping the domain (in this case, tbg.local) and it resolves to the IP and replies). I can ping the IP address, and it replies. I can also do it from the Server, as well." What can you do from the Server? Do you mean ping the client machine? Can you ping the Server (Domain Controller) from the client?

Life's more painless for the brainless.


0

Response Number 7
Name: TbG
Date: October 25, 2007 at 19:26:33 Pacific
Reply:

The server can ping the client.

The Client can ping the server IP.
The Client can ping the domain, and it resolves.
The Client can ping server.tbg.local and it replies.


0

Response Number 8
Name: Jennifer SUMN
Date: October 26, 2007 at 10:22:42 Pacific
Reply:

Have you added the DNS and WINS servers to the client's TCP/IP configuration?

Life's more painless for the brainless.


0

Response Number 9
Name: TbG
Date: October 26, 2007 at 10:31:29 Pacific
Reply:

We have found the issue. The copy of Server 2003 was a bad copy.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Network path not found

network path not found www.computing.net/answers/windows-2003/network-path-not-found/7278.html

Windows 2003 Server - Network Path not found www.computing.net/answers/windows-2003/windows-2003-server-network-path-not-found/9383.html

workstations not accessible www.computing.net/answers/windows-2003/workstations-not-accessible/3584.html