@tim-oguzhan ,
It is hard to say for sure, but the error is being caused by something that is EITHER:
- A bad credential in the domain being referenced
- An inability to resolve the domain being referenced to validate information
The simplest way to figure this out is to start by ensuring that the PLABDC01 machine is on, which it appears to be in the picture above, as well as that it is available over the network, which we cannot tell from the picture. The lab machines sometimes will appear to be on, but may have experienced an issue and are not responsive, or the networking connections are not functioning correctly, and the machine is not reachable.
IF, IF the session is still available, and has not been lost or reset by the time you read this, the I would try stopping and restarting the PLABDC01 machine, and then once it is up, ping between the PLABDC01 machine and the PLABSA01 machine to ensure that you have the correct network configuration and that DNS is working correctly as well.
First, clear the DNS resolver cache on PLABSA01:
ipconfig /flushdns
Then ping from PLABSA01 using the following:
ping plabdc01.practicelabs.com
See if that resolves and works, and if it does, then, I would shut powershell, open a new powershell admin session, and try again.
The command syntax line you are using in powershell seems to be entered correctly from what is shown in the lab instructions, there does not appear to be an error based on mistyping, but rather based on a lack of ability to resolve the domain name to and through the DNS server(s) in the lab environment.
If the lab session has been lost, or rest, then when you try again, make sure that both the PLABDC01 and PLABSA01 machines are up, and can ping via DNS resolution BEFORE you start the lab, and see what happens.
Good luck !!!
Cheers,
Adam