Just read my steps and you’ll see the prob. email at williamb@home.com if you have an answer. Thanks!
Instal Win2k on a system
Config Win2k w/ TCP/IP-IP, subnet, no gateway, NetBEUI,Client for MS Networks?bound to TCP/IP and NetBEUI,File and PrintSharing?bound to NetBEUI
Instal Office 2k
-WinNT 4 serv recognizes the sys as a NT 5 wkstn
-System runs perfect & is still used daily with out any problems
Made an image using Ghost 6.03. Placed imaged drive in an another machine (same hw)& booted w/o network cable attached. Rebooted the machine & scandisk popped up as normal after ghosting. Booted the machine & the PnP wizard found & loaded drivers for any BIOS difs w/o any probs. Changed the sys props for network id from being in a domainto a machine in a workgroup.
Removed TCP/IP & its settings.
Rebooted for the first time. Sys came up without a hitch & worked. I then shut down the machine & booted from the boot disk, I then inserted the disk with Ghost Walker 6.03 & ran with normal config. Changed the name of the system from consult to 1234567 & then set a new SID. All went w/o any problems. Restarted the sys, booting under Win2k, came up no prob, then reset the sys props for the NW id to join the domain through the SETID wiz? no problems
Rebooted system, came back up & ran logon script from NT4 Server & sys worked like normal?
NOW HERE?s THE HITCH
NT4.0 Server man. sees the imaged system as a ?NT Workstation or Server? grayed out, & when you click on it for info itstates ?the network path was not found?. Any sys can ping this sys & get a response on its internal IP.
No other sys can see this new sys in nethood, or can see the imaged sys NetBIOS name, or a sys logged in as domain admin cannot access the share\\imagedsystemname\c$
BUT?
the new imaged sys can access any other sys when logged in as a domain admin
