OK this is a mess but basically I can only image on 2 subnets, the subnet that the K2000 resided on and the one that my department uses.  Any other subnet will get the following: System error 53 has occurred.  The network path was not found.  ERROR: Unable to mount shares at \\1/4\peinst

Quick background:
I'm storing my images on our file server following this KB http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wims-k2000-version-3-6.  This actually worked for a while and then something changed.  I want to say that it was on the network but my network guys swear up and down that they didn't change anything.

I've done so much troubleshooting I don't know where to start but here we go.

All KBE's are made with the KBE manipulator unless otherwise specified. 
So there's the error.  I first thought this was my KBE and made a new one, but that didn't help.  It would still only work on my subnet and nothing else.
I then created the KBE with the echo command turned on to see if it would tell me where it's failing, but it seems not to be my commands because it doesn't get that far because...
I created a KBE without any extra commands added and I get the same issue.
I also created a normal KBE using Media Manager with the same results
I am able to map drives after the error and it just leaves me hanging. I can map a drive to my file server and I can map to to \\k2000\petemp and it goes through. But I have to use another drive letter other than X, when I try X is says that the local drive name is already in use.  However when I do a net use it doesn't show any other drives being mapped.
I know that I've done more but I can't think of anything else right now.

Oh and I called Tech support for this and they told me that Kace can't image across vlans... I just hung up after that.
Option 66 and 244 are both setup btw

If you need me to test anything just let me know, I have a pc setup upstairs with vmviewer installed so I can take screenshots if need be.

Thanks in advance. 
Answer Summary:
4 Comments   [ - ] Hide Comments


  • The KBE uses the X drive as a ram drive to contain the boot wim from the PXE boot. net use will not show it since it is not a network drive but is local to the machine. though if you run dir x: you will see the files on the ram disk.
  • if you recreate the failure (above) and run kgetdhcp 66 and kgetdhcp 67
    what do you get back?
    also if you run ipconfig what do you get back?
  • When I do an ipconfig I get and IP, subnet, and default gw and when I do a /all I have DNS servers as well.
    When I do a kgetdhcp 66 I get ¼ > (the > isn't the right sign but I can't make the block arrow in the error)
    kgetdhcp 67 comes back as kbox2000.0
  • when I type kgetdhcp 244 it returns the IP address for my Kbox.
Please log in to comment

Community Chosen Answer


Ok guys I have it figured out.  After following genfoch01 steps and running kgetdhcp 66 and kgetdhcp 67 and 244 I was able to figure out what the problem was.  

I was getting the ascii characters for option 66 and I didn't know why but after talking to my brother he said to delete the option and re-create it using a string value.  Mine was set to IP on one of my servers.  (Now I want you all to know that I didn't create these, they were already setup for me by my server engineers, the very same people unwilling to help troubleshoot the problem.)

After deleting option 66 following this command netsh dhcp server \\servername delete optiondef 66 (because you can't just delete predefined options) I re-created it as a string value and everything started working.  It's weird that up on the floors I could only hit the broken dhcp server.  I think they made a change on the switches to point to the broken one first instead of the one that was working.

I've been dealing with this problem since I set my K2 to store the images on my file server.  I've never gotten to use the K2 because of this problem and no support from my level 3 guys.

Thanks again everyone!!!
Answered 10/25/2014 by: knuckle66
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity


What about option 67?  Also you how are the options set up?  Ours are on a per subnet basis not a global scope.  We have to put them in for each subnet and have seen this same problem when they create new subnets and do add the option for that subnet.  A per subnet is the typical setup, this allows the flexibility for multiple pxe servers.

Answered 10/23/2014 by: SMal.tmcc
Red Belt

Please log in to comment
I forgot to mention option 67 last week, and I apologize for getting back to you so late, I was off the last couple of days.  Here's a screen shot of my DHCP scope options.  We have 2 server and they are both setup the same.  Right now the scope options are setup globally. 

Answered 10/25/2014 by: knuckle66
Yellow Belt

Please log in to comment