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


Recommended Posts

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

error1.png

  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 :)

  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

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?

  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...

 

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:

 

58df7fd83adad_filesharingon.thumb.png.a09b7553adc595d87fcd1f251203ca19.png

 

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

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

Expand  

folder.thumb.png.2b37c3537ca457add23d1bb798bbf3db.png

 

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

error1.thumb.png.f0964e9c86d0e3c19fbd93a2166c8f13.png

 

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.

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..

  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.....).

 

 

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 ;)

ipv6ipconfig.thumb.png.a19b9e5fdb8d465935b617faa9891f7f.png

 

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

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Hello, Yes, and yes. More specifically, there are lots of features in Windows that I do not use--I cannot recall the last time I needed to run EUDCEDIT.EXE or ODBCAD32.EXE on a computer I own, but I'm sure that for some people they are useful, and for a smaller set of people they might even be indispensable. I don't begrudge Microsoft for including them as part of the standard Windows installation nor the people who need such tools; sometimes it is convenient to have some little utility or feature readily available. One thing I do begrudge is Microsoft's over-reliance on its own telemetry, and perhaps surpisingly on the flip side, customers who disable it. Collecting telemetry is generally a good thing, if it is done for good reasons and does not include any customer PII. However, how you interpret that telemetry is even more important, as that can lead to all sorts of disastrous decisions. On the customer side of things, telemetry is your "vote:" it's how you tell companies what features you use in the program, and lets them prioritize things appropriately. One glaring example is Windows 8, which shipped with the full-screen Start Screen because Microsoft's telemetry told them the average Windows user pressed the Windows key to bring up the Start Menu less than once a day. I have often wondered how many "power users" of previous versions of Windows (XP, Vista, and 7) that relied on the Start Menu disabled the telemetry that would have told Microsoft a difference story about its usage. More recently, I came across a young lady who had a problem with a third-party sync program on her computer running Windows 7. An update for the utility removed Windows 7 compatibility, and broke her backup process. Now, support for Windows 7 ended over 5 years ago in 2020, but there are ISVs who still support their software on it, but decisions about stuff like that are made, in part, by knowing what percentage of your customer base is on what operating system version. When I asked about that, she mentioned she had specifically disabled the telemetry from the sync program to its developers, which was optional to begin with. What made things even worse was that this was an open source utility, and its authors had a very clear, well-designed and scoped policy on the telemetry they collected, the pains they went through to avoid collecting any PII, and even other ancillary risks involving information disclosure (like just using of the software) because of the network connection made for the checks. Yet, she took herself out of telling the project maintainers "Hey, I use your software and I'm running Windows 7" by disabling the telemetry checks, which could have let them know they needed to continue supporting it. In a sense, sending telemetry is just like voting: Individually, you may not think it matters much, but it is often the basis for very important decisions. Regards, Aryeh Goretsky
    • Hello, My thoughts on this are mixed. Microsoft has hosted malicious code in the Microsoft Update Catalog where third party device drivers are stored; I wrote about one such incident about fifteen years ago, so if there are any other old malicious drivers floating around in the catalog, this will be a good step towards preventing any infestations from reoccurring. Another thing, which surprisingly is not mentioned in Microsoft's announcement, is that this helps protect against BYOVD (Bring Your Own Vulnerable Driver) attacks, where malware either comes with or downloads an older device drivers with vulnerabilities in it that can be exploited to gain access to kernel memory. Removing all those old device drivers from the Windows Update Catalog, potentially with all sorts of undisclosed vulnerabilities in them, means an attacker can no longer leisurely count on being able to download them from Microsoft's servers--something that may go unnoticed or ignored by security analysts. This makes the adversary attack a little more noisy, since they have to either include the device driver with the rest of their initial payload or download it from a third-party site at some point prior to beginning their BYOVD attack. On the other hand, it means that people who are looking for a specific version of an older device driver for whatever legitimate reasons, like compatibility, performance or stability, may end up going to dodgy third-party sites in search of older drivers, which increases the risk of exposure to everything from nuisance advertisements and unwanted software to actual malicious code. As for me, I have keeping copies of all the device drivers, firmware updates, etc. I have downloaded over the years, some dating back to DOS and Windows 3.x era, not just for hardware I won, but popular things like unified chipset and video card drivers, just in case I ever needed it. It might seem silly to collect such a thing, but the hardware drivers, firmware updates, and documentation are just about 2 TB in size. From my perspective, it is an inexpensive form of insurance, especially given that disk space is always getting cheaper over time. Regards, Aryeh Goretsky
    • @Raze Bold it boy. (I admit, we all did it from time to time..)
    • Fan Control V227 by Razvan Serea Fan Control is a powerful and versatile portable utility that allows you to monitor, control and customize the fans of your GPU and CPU to keep your machine cool and running smoothly. Fan Control supports a wide range of devices and hardware configurations, giving you complete control over your computer's cooling system. Fan Control backend is mainly based on LibreHardwareMonitor, an open source fork of the original OpenHardwareMonitor. This means that hardware compatiblity is entirely open for anyone to contribute, and doesn't rely on a single developer who may stop caring at some point. Combined with the plugin system, Fan Control is unlocked for many generations of hardware to come. Main features Guided setup process on first launch Save, edit and load multiple profiles Change the theme and color of the application. Multiple temperature sources ( CPU, GPU, motherboard, hard drives... ) Multiple fan curve functions, including a custom graph Mix fan curves or sensor togethers (max, min, average) Low resource usage Advanced tuning with steps, start %, stop %, response time and hysteresis FanControl V227 changelog: Allow decimal with hysteresis values Radeon Pro support through ADLX Fix a bug when cancelling the graph editing dialog Update LibreHardwareMonitorLib Download: FanControl V227 | Installer ~15.0 MB (Open Source) View: Fan Control Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Lol tf you are talking about. People are PAYING by using this app exclusively, just indirectly. Do you have any idea how much facebook charges for api access to WhatsApp which has become more or less a monopoly in e-commerce.
  • Recent Achievements

    • Contributor
      GravityDead went up a rank
      Contributor
    • Week One Done
      BlakeBringer earned a badge
      Week One Done
    • Week One Done
      Helen Shafer earned a badge
      Week One Done
    • First Post
      emptyother earned a badge
      First Post
    • Week One Done
      Crunchy6 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      660
    2. 2
      ATLien_0
      266
    3. 3
      Michael Scrip
      235
    4. 4
      Steven P.
      165
    5. 5
      +FloatingFatMan
      149
  • Tell a friend

    Love Neowin? Tell a friend!