Join New PC to Server
Budget: $30 – $250 USD
I have a brand-new Windows workstation that is on our office Ethernet but still sitting outside the domain and blocked from the built-in administrator account. The rest of the network is healthy—only this one machine is having trouble—so I need someone who can jump in, join it to the network, and prove that it talks to our server without errors.
Here’s what I expect to be wrapped up during the session:
• Sign in with the built-in administrator, clear the “access denied” roadblock, and confirm full local control.
• Configure the NIC, DNS, gateway, and any other settings needed, then join the correct domain (or workgroup, if that turns out to be the better fit).
• Verify that mapped drives, shared folders, and line-of-business apps are reachable from the workstation. I’m not sure which specific shares matter yet, so you’ll help me confirm the right paths once we’re connected.
• Troubleshoot anything that keeps the machine from authenticating cleanly.
Environment notes: the server side reports itself as “Windows 11 Pro”; if that rings any warning bells we can clarify together. The issue is isolated to this new computer—no other devices are showing network trouble.
If you’re comfortable handling small-business Windows Server (and the occasional non-server edition) remotely, let me know the similar setups you’ve fixed before and the toolset you prefer—RDP, AnyDesk, PowerShell, etc. Looking to have this done today if possible.
Here’s what I expect to be wrapped up during the session:
• Sign in with the built-in administrator, clear the “access denied” roadblock, and confirm full local control.
• Configure the NIC, DNS, gateway, and any other settings needed, then join the correct domain (or workgroup, if that turns out to be the better fit).
• Verify that mapped drives, shared folders, and line-of-business apps are reachable from the workstation. I’m not sure which specific shares matter yet, so you’ll help me confirm the right paths once we’re connected.
• Troubleshoot anything that keeps the machine from authenticating cleanly.
Environment notes: the server side reports itself as “Windows 11 Pro”; if that rings any warning bells we can clarify together. The issue is isolated to this new computer—no other devices are showing network trouble.
If you’re comfortable handling small-business Windows Server (and the occasional non-server edition) remotely, let me know the similar setups you’ve fixed before and the toolset you prefer—RDP, AnyDesk, PowerShell, etc. Looking to have this done today if possible.