"Error 53" then Bad command or filename

[Che Peake]

Hi there guys,

I've been using Altiris 6.1 and the Proliant Integration Module 1.6 successfully for a while now, but the last week I've started having problems. I replaced a faulty NIC in the server that runs RDP (the one that DHCP etc is ataached to) and then it all went wrong. Every time I send a job to a blade (BL20p's) it gets a DHCP address, downloads the boot image then an error 53 flashes up before the screen clears and all I see is "Bad command or filename" followed by an A:\> prompt. I'm guessing it can't map the F drive. I've tried uninstalling and reinstalling Altiris and the PIM, I tried rebuilding the server using the same database, I tried again with a new database, and I even tried using a new database and a new deployment server (DL360G3) but I still get the same error on all my blades no matter what job I send (Capture hardware image and windows image, capture hardware image, erase hadrdware and disks, etc) Anyone have any suggestions? please help!

[Jonas Back_2 · Accepted solution]

Interesting indeed :). Have you tried from the A:\> prompt to switch to F: or manually do a net use to the express share? Maybe there's an errormessage that you can see more easily here since at PXE-boot an errormessage flashes so quickly so you won't be able to see it.

And it JUST has to with the blades? No problem on sending commands to DL380's for example?

[Che Peake]

Hi Jonas, thanks for the reply. I have tried to manually map to the express share but I still get the Error 53 - computer could not be found. We only have blades to test with and have only ever used the RDP stuff on them. I'm really stuck as to why it has stopped working!

[Jonas Back_2]

It could be something with nameresolution (WINS/DNS). Could you check to see which IP-adress the DNS and WINS points to for that server? The NIC with the DHCP-address or the one with static IP-address?

Also do you have any other server in the domain (any fileserver will do). Try sharing a directory there with Everyone Full Control. Then try to map THAT share from the prompt. Does this work? Since I guess you're using a domain-user to connect the drives (this is specified when you create the PXE-boot files).

[Che Peake]

Hi again Jonas

Thanks again for your reply. I have now solved the issue, although I'm not sure why it works. The server running RDP is in it's own workgroup and VLAN, but has a second network card attached to the production network to allow us remote access to the server. As soon as the second card is disconnected from the production network, everything works. Strange, as it was working in this configuration before... Never mind, all is working again now.

thanks for your help!

Cheers
ChÃ

[Jonas Back_2]

Just one thing could be to check that NetBIOS is enabled on the network card attached to the Production network. And also, check bindings to see if if maybe the priority to use the production network card for NetBIOS before the other one.

[simon_164]

Hi Che,
I am having the same problem, i tried to map to the drive f: manually but i am getting the error 53 again.

Do you have any idea?
I have another network card on the server but it is not used so i don't think this is the problem

regards !!

[Tv_3]

Hi all,

Multiple NIC connected to the network on an RDP server isn't working.

A multihomed RDP server is not supported !

Sincerly