NET USE from DOS to 2003

Are you using an Active Directory Domain? Have you setup the boot disk to connect to the domain?

Could you please be more specific? I mean what type of partition
do you want to take an image from etc....

If you have a multicast server with your Ghost version try this way :
Run Network Bootdisk option from the Ghost Boot Wizard.
Choose a D-Link DFE530-TX + Next
Use PC-DOS + Next
"Symantec Ghost" + Ghost.exe path + Next
Choose DHCP if you have a DHCP server or give an IP and the correct subnet mask.
Format a floppy + Next

Copy your .dos ndis driver with the existing .dos files

Open A: in the Explorer
Delete \net\DLKPCI.dos
Edit \net\protocol.ini and replace drivername = DLKPCI$ by drivername = B44$ then save it
Edit \config.sys and replace DEVICE=\net\DLKPCI.dos by DEVICE=\net\B44.dos Then save it

(Replace "B44" with the name of your .dos file.
In my case it is b44.dos)

Run/Settings your Ghostcast Server from your W2k3 Server.

Reboot the computer you want to dump with the above floppy inserted.

And voilà.

Thanks all for your input,

I am on an Active Directory Domain but have not joined it, how would I do this? I was under the impression that I did not need to be as the share and security settings are set so 'Everyone' has 'Full Control' (I would prefer not to do this however I did it to try and solve the above problem).

The partition is NTFS 5 with XP installed on it, however I am relatively happy that ghost itself will work fine once I manage to map the network drive correctly.

I do not have GhostCast Server installed.

Thanks again
Norman

You shouldn't need to join the domain, but have a look at the protocol.ini file of your floppy and enter the domain name under workgroup and domain.

If it still doesn't work, try another network card driver.

I know understand that this has to do with Windows 2003 Server using security that is not supported by anything below Windows 2000.

Is there any way round this on a particular share.

It probably doesn't have much to do with share and credentials. More likely its a driver or nic problem. DOS often has problems correctly loading NIC drivers. Try using other drivers or another NIC with other drivers.

I can connect to a share on a non Windows 2003 computer so I am relatively happy that the driver is ok.

Thanks rindi,

What would the security side-effects of this be?

Thanx,

Sorry, I missed your last question. I'm not completely sure what side-effects that would have. I guess it just wouldn't be more secure than Windows 2000 Server used to be.