Asin Posted January 23, 2006 Share Posted January 23, 2006 Here's the situation: I don't have Ghost Server or Ghosting software other than bootdisks with me. The ghost.exe version on the bootdisk is 8.0, so that's what I'm assuming they used to make the disk. I'm trying to load an image on the target computer from the source using a network share. I can get through the bootdisk options and when I try to use the command: net use x: \\COMPUTER\SHARENAME$ to map the share with the image, it fails on me and says that it can't find the network path with an Error 52. However, this works with other computers just fine. Mapping the share I mean. The only difference that could possibly affect this is VMware Workstation which installs a virtual network driver on the source machine. I've since uninstalled VMware and for some reason, the bootdisk now works on the target machine. Any ideas why this network driver is causing a conflict? Any help is greatly appreciated. Link to comment Share on other sites More sharing options...
Asin Posted January 29, 2006 Author Share Posted January 29, 2006 Wait, I got it. The virtual network drivers that were installed utilize Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks. I've since uncheck those for both virutal adapters and things seem to be moving smoothly again. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now