Having issues with Microsoft Deployment Toolkit: can't connect to share

[Danielx64]

Ok I decided to use Microsoft Deployment Toolkit to manage my deployment of Windows 10 and Office 2016. Before I went to put this on the server at work, I decided to play it safe and play with it at home on my machine. And I am glad I did!

 

Now the issue that I am having is that when I boot the VM with the iso to connect to the deployment share, I am unable to do so.

 

First I tried pinging the host machine via IP and that was a no go. I turned my firewall off and that fixed it. Then I tried pinging the hostname of the host machine. That didn't work. So I went and edited the host file and added a line in so that I could talk to the host machine via hostname. That solved the second issue.

 

Then for fun I tried to use net use command to map a network drive. Now that where I am stuck. I am getting error 53 (The network path was not found. ). File & Printer Sharing is enabled (that was the first thing I checked when using net use).

 

I been on this all afternoon so it may be something simple but could someone please help me out?

 

pinging @BudMan

[ybrett23]

U need wds installed also

Can i ask why you don't use pxe boot?

[Danielx64]

  On 01/04/2017 at 08:38, ybrett23 said:

U need wds installed also

Can i ask why you don't use pxe boot?

Expand  

I'm doing this on windows 10 pro machine (for testing until I get enough experience to do this on a live network) so I don't think wds will be available for use, as for pxe boot: that will be done when I do it on a live network

[+BudMan MVC]

192.168.254.1???  that is the IP you gave this deployment server???

 

Is this a server actually running on something or also on some vm?? 

[Danielx64]

  On 01/04/2017 at 09:23, BudMan said:

192.168.254.1???  that is the IP you gave this deployment server???

 

Is this a server actually running on something or also on some vm?? 

Expand  

The server is a windows 10 pro host with vmware player installed and the client is in a VM

[+BudMan MVC]

And what network do you have them on??  Where are you trying to access that share from?  What is the IPconfig all from the server, what is the ipconfig /all from the client your trying to access.  Do you even have file and print sharing enabled on the server?  What exact share are you trying to connect too \\server\deploy ???  Is that shared?

[T3X4S]

  On 01/04/2017 at 10:11, BudMan said:

And what network do you have them on??  Where are you trying to access that share from?  What is the IPconfig all from the server, what is the ipconfig /all from the client your trying to access.  Do you even have file and print sharing enabled on the server?  What exact share are you trying to connect too \\server\deploy ???  Is that shared?

Expand  

I was going to say something about the lack of info given from the OP - but @BudMan has done it better than I could have...

 

[Danielx64]

Ok here's what I am working on while I get hand on experience with Microsoft Deployment Toolkit.

 

One physical computer with windows 10 pro AU installed

VMware Workstation 12 Player is used to create a virtual computer as a test client.

 

My ipconfig for the physical computer

 

  Quote

C:\Users\Daniel>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DESKTOP-9BTVQ73
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I218-V
   Physical Address. . . . . . . . . : F0-79-59-8C-03-41
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 1C-87-2C-C6-2E-4E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a847:824c:29b2:3ca6%11(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.60.166(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 67129430
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-04-85-B2-F0-79-59-8C-03-41
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::dd54:e33e:fb48:485f%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.255.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 302010454
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-04-85-B2-F0-79-59-8C-03-41
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : ASUS PCE-N15 11n Wireless LAN PCI-E Card
   Physical Address. . . . . . . . . : 1C-87-2C-C6-2E-4E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::1589:4dc9:96fa:5579%9(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.43.48(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, 1 April 2017 8:31:20 PM
   Lease Expires . . . . . . . . . . : Saturday, 1 April 2017 10:31:46 PM
   Default Gateway . . . . . . . . . : 192.168.43.1
   DHCP Server . . . . . . . . . . . : 192.168.43.1
   DHCPv6 IAID . . . . . . . . . . . : 136087340
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-04-85-B2-F0-79-59-8C-03-41
   DNS Servers . . . . . . . . . . . : 192.168.43.1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{B74CED0B-CF63-470D-89CE-D745B8C49A6F}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{8D45C576-8BAB-4B88-BC11-33ED49361F14}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{8EAD2DF7-C1A6-4B3B-87F7-E19E14ED1F0C}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Daniel>

Expand  

 

ipconfig for the VM client:

 

  Quote

X:\windows\system32>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : minint-r572fte
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : localdomain

Ethernet adapter Ethernet0:

   Connection-specific DNS Suffix  . : localdomain
   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-37-70-14
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d43c:c736:1596:f6af%2(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.254.128(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, April 1, 2017 8:23:27 PM
   Lease Expires . . . . . . . . . . : Saturday, April 1, 2017 9:38:27 PM
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . : 192.168.254.254
   DHCPv6 IAID . . . . . . . . . . . : 33557545
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-72-35-16-00-0C-29-37-70-14
   DNS Servers . . . . . . . . . . . : 192.168.254.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

X:\windows\system32>

Expand  

 

The VM can ping the host machine.

  On 01/04/2017 at 10:11, BudMan said:

Do you even have file and print sharing enabled on the server?

Expand  

Yes I do:

 

 

  On 01/04/2017 at 10:11, BudMan said:

What exact share are you trying to connect too \\server\deploy ???  Is that shared?

Expand  

 

This is the error that I am getting in the VM:

 

The VM can ping the host via hostname. Also in the first screenshot I edited the host file in the VM so that I could use server as a shortcut but thinking that may have been the issue I used the real computer name and that still didn't work.

[+BudMan MVC]

Wow what a mess!!!

 

VMnet8: is the nat adapter.. from vmware.. Which is 192.168.255/24 then you say your vm client is on 192.168.254/24

 

What vm network do you have it connected too?

 

If you want your vm client to access files off the HOST machine then you should bridge it to the same network Or you a host only network and make sure your HOST machine is actually sharing on that interface..

 

You also have just a mess of ipv6 transition.. Teredo, multiple isatap interfaces.. etc..  Yeah no wonder its not freaking working... I don't know what your pinging at 192.168.254.1 - but from your ipconfig /all of your host.  That is NOT one of its IPs on any interface..

[Danielx64]

  On 01/04/2017 at 13:40, BudMan said:

Wow what a mess!!!

 

VMnet8: is the nat adapter.. from vmware.. Which is 192.168.255/24 then you say your vm client is on 192.168.254/24

 

What vm network do you have it connected too?

 

If you want your vm client to access files off the HOST machine then you should bridge it to the same network Or you a host only network and make sure your HOST machine is actually sharing on that interface..

 

You also have just a mess of ipv6 transition.. Teredo, multiple isatap interfaces.. etc..  Yeah no wonder its not freaking working... I don't know what your pinging at 192.168.254.1 - but from your ipconfig /all of your host.  That is NOT one of its IPs on any interface..

Expand  

Well I just found the issue and fixed it. Well it a dirty hack anyway: a clean install of windows will be taking place next week anyway so much of the mess will be cleaned up for once and (I hope) all.

 

What I did was is changed the ip address for VMnet1 to 192.168.254.2 and then I disabled the VMnet1 interface.

 

I guess this is what happen when you are not careful with vmnetcfg..... (I found a guide on how to use vmnetcfg in the free version of vmware player.....).

 

 

[+BudMan MVC]

clean install has nothing to do with removing the interfaces your not using..

 

Clean install of windows creates that mess   MS in their infinite wisdom thought it a good idea to install multiple ways to tunnel ipv6 over ipv4   Because it seems users are too stupid to install or click on the one they need to use if any.. I use ipv6 and run the native dual stack without any of that nonsense of teredo, isatap, 6to4, etc..

 

See how clean my ipconfig /all looks

 

If your not ready to setup ipv6 correctly.. I suggest you just turn it all off.