Sunday, June 26, 2011

network path can't be found

Problem:
After I added Active Directory service in win2003, I want to connect my workstation to this server, I got an error message, network path can't be found.
Detail:
I have a computer router, ip is 192.168.0.1. It specify the server ip is 192.168.0.72.
I have a win2003 server, ip is 192.168.0.72, dynamic get ip from router. Because the router already specify its ip to 192.168.0.72, so use dynamic ip won't have problem.
The netbios for this server is server0, The full domain for this server is server.server.website4u.ca, primary DNS suffix is server.website4u.ca.
I added user ziyan to this domain.
I have another computer os is win7. The computer is wks001. ip is 192.168.0.21 which is dynamic from router. It has local user ziyan.
Now I want to join this computer to domain and let domain to control its password.
I tried to change to domain server0, after a while, it come back with error message "network path can't be found".
The problem is I use 192.168.0.1 as primary DNS. Although I installed wins service on the server, so server0 can be found without problem. But it still can't find server.server.website4u.ca. Because server.server.website4u.ca is not exist in the real internet, it exist in my local network. I should let the DNS know that server.server.website4u.ca is in my local network.
Solution:
In TCP/IP, I added 192.168.0.72 in DNS, and put it in the first position, 192.168.0.1 is the second DNS. Also I added 192.168.0.72 in wins, and put it in the first position, 192.168.0.1 is the second wins.
After I done these setup. I was able to successful added my workstation to the domain. So when I login, it shows login with wks001/ziyan, this is local user. And I switch user, it shows login with server0 domain, username, and password. So I login user ziyan again, and use the password which I created on server (different from local password), I logged in and computer started to create new desktop for me.
Conclusion:
I did many system which the server ip is 192.168.0.1, so I never has problem to join a domain. But for server which ip is not 192.168.0.1, I wasn't able to join a domain until today. I found many posts on Internet about this problem. There are so many solutions. Maybe they don't need to do so many changes, try to do what I did. Good Luck!

No comments:

Post a Comment