Hi Teryus,
Firstly, i don't use DOS so i apologise if i'm completely wrong :)

Looks like DS is trying to map to a directory which isn't valid. You should be able to check through the boot dis creator and edit your image. It will have a reference to a directory which is mapping. Check that this map is valid.
Apart from this, i suppose it could be the network not initialising properly. Are you getting this on all machines, including those that work with other boot options? Again the boot disk creator has the drivers that can be used, ensure that the required drivers are included in the boot image.

Hope this helps.

We've often seen this issue. Reinstall PXE and redefine bootfile and should work

I've seen this when the network drivers aren't loading properly or are incorrect.  Also, this can happen if the client can't resolve the name of the server you are attempting to map.  I don't use dos very often any more in this aspect, but you may be able to use a host file to ensure the mapping happens as expected.  This can be setup during the PXE boot creation. 

Sounds like the NIC drivers to me. Make sure that the correct driver is installed for that card and also make sure its at the top of the list when building your PXE boot disk. If it still does't work try using the UNDI driver. That should work but will most likely be much slower.

Do you have an IP and are you networked at when you get the 53? If not it probably is a driver issue.
What does a manual NET USE say?
Is it an OEM machine where F: is already in use because of the multiple OEM paritions? Try wiping the drive and see if that gets you any further.
Is there an entry in the LMHOSTS on your bootdisk for the DS server?

Also this comes to mind if you are in an AD environment: https://kb.altiris.com/article.asp?article=20656&p=1

I read in your other post that WinPE and Linux work, so it's either the above issue or a driver issue most likely. What model PC are you trying it on?

Ok, thanks all for your help, I appreciate a lot.

i go to explain what i do.
.- i did a copy paste of the files of msdos to create a pxe boot for MSDOS
.- I put that files in express
.- I made the pxeboot with the wizard of altiris
.- after that i made a test with server
and boot ok, but in the part of map network send the error message

i can see the rdp from other server with the command net use

I dont know what happen
The permissions in the folder express are everyone full control
Its a strange case because with Winpe and linux, the map network if it works, but with DOS not.

The PC its a BladeBL20P HP, the model of NIC its a HP NC7781 Gigabit Server Adapter
I dont installed the driver yet, because with WinPE and Linux boot ok, i go to install the driver and building the pxe boot disk

The RDP have 3 Nics, one for Pxe, other for Administrative and other for ILO, i did some tests disconecting the other two NICS (ILO and Administrative), and not work again
I edit the lmhosts, add a line with the ip of PXE (because the file lmhosts have the ip administrative), and not work
change the order of nics (first PXE) and not work
Im go check the article of altiris brandon, all help its appreciate.

More ideas ?? please.

teryus

Well, after many attempts, the boot for dos not work

I follow the article of brandon, and the rdp not boot for dos
I create a new account (bhawver) with a new password (4 characters), and not work
I download the driver NIC of my BL40P, building a nex pxe boot for dos with the driver, and not work

With regard to your question bhawver, Why DOS if Winpe and Linuxpe work ok, you see, i dont know how to create a image of my BL40P with Winpe (capture windows 2003 sysprep image winpe), in the past we have RDP 6.5, and i remember that the images i created with DOS (push F8- select dos- push F2-exit-Mapdrive F:) and launch rdeploy and amouse, i create the image and that same image i download by the same method in other bl40p.

With Winpe i dont know how to do that, because  i send the job, the server boot ok, and after that, nothing more happen, the server trie to boot again to create the image, but he dont find the pxe server and boot to windows again

I can do the images like in the past, with DOS, but after all, i cant do that.
I can create images with Quick disk image, and deploy new installation of windows, but the problem its, when i download a image in other server, the image does not respect the domain, the IPs disappear, just leave the DNS, that happen after the image run a job call Replace ID, i remember with DOS that problem no exist, that is the reason to create the images for DOS.

Well, i accept any idea please, just leave the option of carl g taylor, reinstall PXE, i dont know how, but its the ultimate choise to do.

Regards

>The RDP have 3 Nics, one for Pxe, other for Administrative and other for ILO,
>i did some tests disconecting the other two NICS (ILO and Administrative)

Try to DISABLE  the NIC for Administrative use (disconnecting is not enough). DOS NET LOGON does not like servers with multiple OS-NIC configure for different subnet... (ILO is not a problem)