Fix - The following error occurred attempting to join Windows 7 to a Domain | Path was not found
Fix - The following error occurred attempting to join Windows 7 to a Domain | Path was not found
This video shows you the process to resolve joining your computer to a domain server. The following error occurred attempting to join the domain.
Become a professional IT System Engineer by following this course:
https://www.udemy.com/course/it-syste…
Windows 11 Full Tutorial: Master Windows 11 Like a Professional
• Windows 11 Tutorial | Master Windows …
I would like to buy good servers \u0026 IT equipment’s to create more practical’s for you.
If you feel led to support me to keep creating good content. Please support me on PayPal: https://paypal.me/kelvglobalict
Please buy me a onetime coffee by supporting my work.
support me on PayPal: https://paypal.me/kelvglobalict
Connect with me on social media:
- Follow me on TikTok for one-on-one chat: https://www.tiktok.com/@kelvglobalict
- Windows 11 Facebook Group: https://www.facebook.com/groups/26676…
- Facebook: https://www.facebook.com/kelvglobalict
- Instagram: https://www.instagram.com/kelvinjohns…
- LinkedIn: https://www.linkedin.com/in/kelvin-jo…
- Twitter: https://twitter.com/kejocomputers
- Website: www.kelvglobal.com
- PayPal Donation: https://paypal.me/kelvglobalict
Get in touch with me: Email: https://kelvglobal.com/contact/
Subscribe to my YouTube channel:
/ kelvinjohnson-ict
#WindowsServer #Windows7
Content
0 -> welcome back to my youtube channel
1.92 -> in this video i want to show you how to
3.919 -> resolve a situation whereby you try to
6.16 -> join a windows 7 device to a windows
8.96 -> domain and you receive an error message
11.36 -> we say the network part was not found so
13.92 -> if for example i try to join this
15.839 -> windows 7 device to the following domain
20.48 -> and i just hit ok so i'm going to
22.48 -> actually enter my admin credentials
28.64 -> so let's wait and try to see if this
30.72 -> device will be able to actually join
33.12 -> this domain server the kelv global you
35.52 -> can see another dc001 so let's wait and
38.879 -> see if we are able to actually join this
41.2 -> windows 7 device to this to that domain
44.96 -> so here you can see that we received the
46.559 -> following error message which says the
48.239 -> following error
49.52 -> or code attempted to join the domain
51.68 -> kelv global and the network part was not
54.8 -> found so first of all to troubleshoot
56.719 -> this issue what we need to do is if i go
58.96 -> to my start menu and i enter the command
61.28 -> prompt
62.719 -> cmd and i try to ping
64.879 -> the server by name as this dc001
69.2 -> you can see that we are able to actually
70.88 -> ping that server so i can actually try
73.76 -> to also
74.96 -> let me just restart um let me start on
78 -> cmd command prompt as well and then ping
80.88 -> the windows 7 device we actually
84.159 -> trying to join let me see i think that's
87.2 -> the windows 7 0 1
90.4 -> and let me see if that is actually
92.079 -> correct so i'm just going to enter the
94 -> host name
95.16 -> [Music]
97.28 -> sorry for the mistake
98.96 -> the hostile mother's device is windows 7
102.72 -> 0 1 9 win 7 0 1 so if i go there i was
107.2 -> not able to actually ping you can see
108.799 -> i'm receiving requested timer that's the
111.36 -> win 7 0 one and also if i try to do
116.28 -> ipconfig and you can see that the ip
118.799 -> address does the one nine two one six
120.56 -> eight two four five one five zero so if
123.36 -> i try to pick ping that ping 192.168.2
130.64 -> and you can see that i'm not able to
132.319 -> ping that the windows 7 device i think
135.599 -> that should be
137.04 -> the problem so let's try and see well
139.52 -> first of all you should also make sure
141.84 -> that your firewall is also configured to
144.08 -> allow you ping that device so if i go to
147.44 -> let me just first of all
149.44 -> let me go open control panel
154.959 -> so we should always make sure that if i
157.04 -> go to the windows firewall here you
159.28 -> definitely want to create a rule to
161.2 -> actually allow the ecm people to let me
163.92 -> just try to turn this off just for this
166 -> purpose i'm going to just turn
167.84 -> everything about the firewall let's see
169.44 -> if we are if you are now able to ping
171.599 -> this device from the dc 0 0 1
175.519 -> here we go you can see now i can ping
177.12 -> which means that the um the ping command
179.84 -> was actually disabled on your firewall
182.48 -> if i try to ping this device by name as
184.319 -> well you can see that we are able to
186.319 -> ping the device so which means we are
187.84 -> able to actually communicate with both
189.92 -> the device at the same time so which
192 -> means the firewall was actually blocking
194.319 -> us trying to communicate from our server
196.56 -> from outside to inside but we are able
199.36 -> to actually connect
200.8 -> ping other devices so the next thing we
203.28 -> want to actually do is the following
205.599 -> i want to check again because what i did
207.84 -> is actually i actually configured the
209.2 -> static ip address for this divide
210.959 -> because it's actually just a test
212.159 -> environment if you are working in a
213.76 -> production environment definitely your
215.68 -> dhcp server will be providing you or we
218.159 -> are signing ip address automatically to
220.72 -> all your devices because you will not be
222.4 -> doing it manually but what i actually
224.319 -> did for this starting for this small
226.239 -> environment is i try to assign a static
228 -> ip address to make sure that their api
229.92 -> address actually um they are always in
232.319 -> there both are always in the same range
234.48 -> so what let me just go to my network
236.72 -> insurance center local area connection
239.519 -> and if i go to properties
241.92 -> another tcp ipv version for if i go to
245.519 -> properties here i can see that
248.239 -> we can see that the ip address is
249.76 -> actually the same subnet range of the
252.319 -> server and you can see our subnet mask
254.239 -> is good at default gateway is good of
256.239 -> course will give us access to the
258.079 -> internet but here we can see that our
259.84 -> preferred dns is actually the problem so
263.12 -> the preferred dns is actually with the
264.96 -> same as the default gateway which of
266.72 -> course is actually getting access to the
269.36 -> internet but it's not actually routing
272.08 -> back again to that enterprise to kelv
274.96 -> global so what we need to do right now
276.72 -> is if i add the 210
280.479 -> and then decided to add the
283.68 -> following dns also the selected dns just
286.72 -> for the other default gateway and here
288.8 -> you can see we now add a preferred dns
290.72 -> which is also is actually
293.28 -> the ip address of the server which will
295.28 -> allow the windows 7 or your windows 10
297.199 -> device to be able to route to your
299.12 -> windows server so i'm going to click ok
301.6 -> for that and then click ok again and
303.68 -> then click close but we still have
305.68 -> access to the internet because uh
307.44 -> default gateway is properly configured
309.68 -> so if i go back again here so let's try
312.72 -> to actually
314.639 -> join the device again to a domain and
316.32 -> see i'm going to enter my
319.039 -> admin credentials and then enter my
323.52 -> and password
323.84 -> click okay
327.199 -> let's try and just wait for some seconds
328.72 -> let's see if this will work this time
333.759 -> so here we go you can see that right now
335.28 -> i'm able to join this device to the
337.199 -> domain without any issues they say
339.6 -> welcome to kelp global
341.759 -> domain so if i go back again
344.479 -> to the server and let me go to active
346.32 -> directory and users and if i go to
348.72 -> computers and i do a refresh you can see
351.6 -> we now have the device just appeared
353.6 -> here as a windows 7 strip zero one so
358 -> that is how you join your device to a
360.8 -> domain if you are having any issues or
363.84 -> if you receive an error message we said
365.44 -> the network part was not found thank you
368.08 -> very much for taking your time to watch
369.52 -> this video and also this um solution can
372.08 -> also be applied to a windows 10 device
374.72 -> or windows 8.1 device thank you very
377.12 -> much and please don't forget to
378.24 -> subscribe to my youtube channel for more
380 -> i.t related video bye
385.75 -> [Music]
399.28 -> you
Source: https://www.youtube.com/watch?v=WeFXZknVtyo