<div>
There is no problem joining Windows 7 to Server 2012. <br />
<br />
Open a command prompt and type: &nbsp;NET USE T: \\Server2012name\Folder and authenticate. What numerical error do you get? &nbsp;<br />
<br />
That will help troubleshoot. You may have a firewall error or some error like that.
</div>


<div>
I run the command on my WIN7 PRO: &nbsp; NET USE T: \\cinco.local\<br />
System error 53 has occurred
</div>


<div>
This Microsoft article suggests security software is blocking or DNS is not allowing fully qualified domain name. <br />
<br />
<a href="http://answers.microsoft.com/en-us/windows/forum/windows_vista-networking/system-error-53-has-occurred-the-network-path-was/9511bbd8-ca11-4c1e-8d85-f7e8ce7e0fb9?auth=1" rel="ugc nofollow">http://answers.microsoft.com/en-us/windows/forum/windows_vista-networking/system-error-53-has-occurred-the-network-path-was/9511bbd8-ca11-4c1e-8d85-f7e8ce7e0fb9?auth=1</a><br />
<br />
Can you ping the server? <br />
<br />
Can you: &nbsp;NET USE T: \\IPaddressofserver\folder<wbr /> ?
</div>


<div>
Hi,<br />
<br />
maybe a silly question, but can you ping domain controller?<br />
Do you have some antivirus or security software, and so, does turning them off helps?<br />
<br />
Regards,
</div>


<div>
I disable my antivirus before posting my question.<br />
I run the command above: &nbsp;NET USE T:\\10.0.100.20 and I got System error 67
</div>


<div>
The new error implicates the network adapter. If you have other Windows 7 machines connected to the Server 2012, try replacing the wired network card with a new card, or, update the driver of the current card. <br />
<br />
Also update the driver of the server network card (although Server 2012 should be OK). <br />
<br />
<a href="https://support.microsoft.com/en-ca/kb/843156" rel="ugc">https://support.microsoft.com/en-ca/kb/843156</a>
</div>


<div>
You might also try TCP/IP Reset and DNS Flush.<br />
<br />
Open cmd.exe with Run as Administrator<br />
Then &nbsp;netsh int ip reset c:\resetlog.txt<br />
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache<br />
Then restart the computer
</div>


<div>
Please post screen shots and not text of the error - you keep saying you're using net use x: \\serverOrIP but in NONE of your examples have you included a share name. &nbsp;When I run net use x: \\server I too get system error 53, but if I specify a SHARE (as you should be doing) it works.<br />
<br />
A picture is worth a thousand words.<br />
<br />
And of course, MAKE SURE your DNS settings on the server ONLY point to itself and the DNS settings on the workstation ONLY point to the server and NO THIRD PARTY DNS SERVERS!
</div>


<div>
I tried all these steps and still doesn't work. I tried on another Windows 7 and I got the same result.<br />
FYI<br />
I installed server 2012 on vmware workstation 2012 on my pc. I configured my Palo Alto firewall to query LDAP and I can see all the groups(LDAP is answering correctly). I configure Active Directory through the wizard. Am I missing something?
</div>


<div>
PICTURES of your DNS settings.
</div>


<div>
It's bridged. I am attaching the snap sh<a href="https://filedb.experts-exchange.com/incoming/2016/04_w15/1089697/Windows7-1.PNG" target="_blank" title="Win7-1 (70 KB)"><img alt="Win7-1" class="file-block lazyload" style="max-width: 460px;" data-src="https://filedb.experts-exchange.com/incoming/2016/04_w15/1089697/Windows7-1.PNG" /></a>ots. My server DNS is pointing to itself.<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/04_w15/1089698/Windows7-2.PNG" target="_blank" class="file-inline" title="Win7-2 (116 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Windows7-2.PNG</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2016/04_w15/1089699/Windows7-3.PNG" target="_blank" class="file-inline" title="Windows7-3.PNG (45 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Windows7-3.PNG</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2016/04_w15/1089700/Windows7-4.PNG" target="_blank" class="file-inline" title="Windows7-4.PNG (46 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Windows7-4.PNG</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2016/04_w15/1089701/Windows7-5.PNG" target="_blank" class="file-inline" title="Windows7-5.PNG (113 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Windows7-5.PNG</a>
</div>


Windows7-3.PNG

Windows7-5.PNG

Windows7-2.PNG

Windows7-4.PNG

Windows7-1.PNG

<div>
Do you have any Windows 7 machine on the domain to this Virtual Server? &nbsp;I thought it to be one machine with an issue.
</div>


<div>
I don't have any existing machines to this domain, this is the first time I am trying to join the domain with 2 different machines in order for me to test some Palo Alto configurations.
</div>


<div>
I would check out your server DHCP, Domain and DNS settings. You have a Server Configuration issue. The question suggests it is a workstation issue and the chances are 95% that it is not a workstation issue. <br />
<br />
Check out the standard server settings and the firewall settings.
</div>


<div>
Maybe remove the Palo Alto Firewall temporarily, or disable it completely temporarily to test basic domain connection.
</div>


<div>
I will configure a 2nd server with and tested again. I ma not sure if it's because I am running a USB gigabit adapter. I will let you know.<br />
Thanks
</div>


<div>
Why are you using a USB adapter on the guest? &nbsp;<br />
<br />
If Bridged, the guest will use the host NIC, not a USB adapter. &nbsp;Is the wired NIC working?
</div>


<div>
Sorry I wasn't clear but my laptop doesn't have a network card but a USB adapter for network.
</div>


<div>
A USB Internet card (I have and use one) is not a source of external DHCP (at least not normally). So the guest would need to be NAT and you would have to adjust firewall rules accordingly. <br />
<br />
Even Wi-Fi to an external router would work better and can be bridged.
</div>


<div>
Did you figure this one out?<br />
<br />
1. You must use NAT for a cellular air card and that put the Server on a different subnet than the machine trying to join.<br />
<br />
2. You will have to address firewall rules.<br />
<br />
3. You may have to make HOSTS entries on the Server and possibly the HOST to permit naming conventions.<br />
<br />
4. You may have to address the Server by IP address.
</div>


<div>
I reinstalled a second server and authentication works fine. It seems that the first server had an issue with authentication.
</div>


<div>
Thanks for giving me different options to troubleshoot.<br />
Appreciated
</div>


<div>
Thanks for the update and I was happy to get you going.
</div>


<div>
<div class="content wysiwyg-content">
Hi Experts,<br />
<br />
I am having issues joining Windows 7PRO to a Windows server 2012 Active Directory. When trying to join the computer the windows security will pop up to enter my domain credentials but after entering this information I will get this error:<br />
&quot;The network path was not found&quot;<br />
<br />
<br />
Please advise
</div>
</div>


Hi Experts,

I am having issues joining Windows 7PRO to a Windows server 2012 Active Directory. When trying to join the computer the windows security will pop up to enter my domain credentials but after entering this information I will get this error:
"The network path was not found"


Please advise

Win 7PRO not joining domain 2012

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Windows 7 is an operating system from Microsoft. Features include multi-touch support, a redesigned Windows Shell with a new taskbar, referred to as the Superbar, a home networking system called HomeGroup, and performance improvements.