BCM400 3.6 remote backup problem

[morgansdad]

I have done a backup to a remote drive many times successfully on other BCMs using the exact information "username, password, etc." and for some reason, a new BCM is giving me an error:
"AN ERROR HAS OCCURRED WHEN ATTEMPTING TO CONNECT TO THE REMOTE DRIVE. Error:170 The requested resource is in use." And the backup fails to schedule? Any ideas? I know the remote drive on my laptop is available, because when I take it back to the lab, it runs perfectly.

 

[acewarlock]

may not have the correct IP address. That's what I get when I enter the wrong IP address or the Directory isn't set to share.

 

[morgansdad]

I disconnected the customers LAN1 ethernet port, I am connected to LAN2 with an IP of 10.10.11.25, still nothing.

 

[acewarlock]

From the CMD prompt, do (IPCONFIG) and see if your Laptop is on the correct IP address

 

[morgansdad]

Correct IP address, its just me 10.10.11.25 and the BCM LAN2 10.10.11.1. The BCM has the latest patches, they recently had the BFT replaced and strangely enough they can't even do a local backup. I also noticed that although they are running 2 cabinets, there are also only 2 PEC cards and not 4, hmmmmmmmmmm.

 

[biv343]

PEC cards don't matter for an expansion cabinet. Only really need to expand the PECs when dealing with a lot of VOIP resources.

I'm guessing the issue with your backups is a drive mapping that won't release. I've run into that quite a few times. You can try to view/delete any mappings via maintenance tools, Shared Drive, Detach a shared volume. The big issue is knowing the letter of the share. Sometimes you can find that by typing the NET USE command from the BCM command line. You can detach a share by typing net use Z: /delete - subsitute Z for the letter of the share.

If you have VNC access to your system, you can check/delete the shares that way. Note that enabling VNC access on your BCM will render it 'unsupported' in Nortel's eyes.

You can also open a case with Nortel, and they can attach to the BCM and work their magic to delete the stuck drive mapping.