Callpilot Network Backup

[mclark13]

I read thread798-1191852 and we are having the same issue. Our Callpilot backups (Option 11c switch, 201i version 04.04.04.30 callpilot, and CCM 6.0 Symposium) stopped back in November and we are unable to start backing them up to one of our servers. We checked all of our security and share settings. We are able to connect to Callpilot from all the servers we tried; however, we are unable to connect to any servers from CallPilot. We get this error:

Unable to start backup operation. 41809#Can not establish a network connection to the remote folder (\\TSMServer\Nortel_CP) using "CPBackup" backup device. Net error = 1014, Win32 = 1240. The account is not authorized to log in from this station. Remote disk device is not ready. The account is not authorized to log in from this station.

We have tried all that we know. Any assistance would be appreciated. We have an Option 11c switch and are using Symposium CCM 6.0. Our vendor is also at a loss, so I am dead in the water.

 

[pronei]

List your current pep levels. There are several peps that address this issue.

Are you able to connect to a map drive using just windows? If you can, just use the native Windows backup and schedule nightly windows backups.

 

[mclark13]

Thanks pronei,

Here are the PEPs I show for Callpilot:
PEP: CP40404SU04S
PEP: CP404S04G10S
PEP: CP404S04G19S
PEP: CP404S04G22C
PEP: CP404S04G26S
PEP: CP404S04G32S
PEP: CP404S04G33S
PEP: CP404S04G35S
PEP: CP404S04G36S
PEP: CP404S04G42S
PEP: CP404S04L07S
PEP: CPSECPEP010S

We are not able to even map a drive to do the native windows backup at this point.

 

[Jephph]

Were any of these computers added to a Windows domain recently?

 

[mclark13]

Jephph,

We were told that the nortel equipment (Callpilot and Symposium) cannot be on our domain by our supplier. The server we were backing up to was and is on our domain.

 

[pronei]

On the CallPilot Server:
Click Start
Click Run
type: \\TSMServer\Nortel_CP

Does it ask for username and pass?

If yes, enter the username as xxxx\administrator (where xxxx = the active directory domain name and administrator is the name of an administrative user on the domain). Then enter the password for that administrative user. You can then do windows backups.

If No, let me know.

 

[DFKSydney]

Could be wrong here, but when doing a network backup, on the remote device you need to create a user name and password equivalent to ngensys plus the appropriate password.

On the remote server, this "new user" then needs full administration priveleges over the backup folder.

You also need to ensure in user management on the CP server that the mapped drive to the backup "reconnects" on a reboot.

Easiest way that I know to check all this is on the CP itself, using explorer, see if you can navigate to the backup directory, AND create a new file in there.

 

[mclark13]

pronei,

It does not prompt us for a username and password.

DFKSydney,

We have the ngensys user created on the remote box, but the cp box cannot establish a network share to any box even if we create a share on the CP box give ngensys full permissions.

We get the error that the account is not allowed to login from this location.

 

[pronei]

Next, are you even able to ping the server you are attempting to do network backups to?

Try to ping the DNS name and the IP.

Sounds like more of a networking (Name resolution) problem than it does an actual Callpilot probelm.

 

[Utreg]

We had a simular problem, backup stopped working suddenly.

Deleting and re-creating the schedule via 'System', 'Backup/Restore' helped us...

 

[mclark13]

pronei,

We are able to ping the server. However, it appears it has to do with Windows Networking. We cannot browse Windows Shares on any machine even shares setup on CP box, from CP box. But we can connect from other boxes to the CP box.

Utreg,

We created a new schedule back up in CP but it also returned an error. Are you saying we should delete all the scheduled backups and then start with a new one and that may help?

 

[bbeaupre]

Hi Guys,

I had the same problems with my backup and the onyl way I could get it to work was :

1- Share a drive on a server or computer where you want to backup your Callpilot or CCM6.

2- Make sure you have the same security on all the machine, server or computer, Callpilot and CCM6.

3- Create a share folder for both type of backup, Callpilot and CCM6.

4- Add the permissions for these two folder.

5- Make sure NetBios is running on the server or Computer where you want to backup your file.

6- Create your Backup Device (network drive) in the Callpilot and CCM6 using the server or computer IP address and not a DNS name.

7- Try to ping the IP address of the server or Computer.

8- If you can't ping, don't waster your time trying to backup anything, you have to be able to ping the server before you can backup anything, depending if your data network is using vlan's or not and if your system is in the same vlan, if your not in the same vlan you might need to get and access list created for your device.

9- Once you can ping, you should be able to start your network backup.

Let me know out if this was helpfull.

 

[SSJVirus007]

You Need SP2 install...Pep010S require w2k3 Sp2.

KNOWN ISSUE: After installing this PEP on a CallPilot server without CPSECPEPSP2S, backup to a network drive will not work. When you try to map the network drive, you will get an error "The account is not authorized to log in from this station". There are two solutions for this problem:
a) install CPSECPEPSP2 to upgrade to Windows Server 2003 Service Pack 2.

 

[mclark13]

SSJVirus007,

Just for clarification. Are the two solutions to either 1) install CPSECPEPSP2 or 2) upgrade to Windows Server 2003 Service Pack 2?

 

[SSJVirus007]

Opps forgot to past the 2 fixes..

KNOWN ISSUE: After installing this PEP on a CallPilot server without CPSECPEPSP2S, backup to a network drive will not work. When you try to map the network drive, you will get an error "The account is not authorized to log in from this station". There are two solutions for this problem:
a) install CPSECPEPSP2 to upgrade to Windows Server 2003 Service Pack 2 (recommended)
b) Use Administrator Tools > Local Security Policy > Security Options. Change the "Microsoft Network Client Digitally sign communications (always)" setting to "Disabled" and reboot the server

 

[mclark13]

SSJVirus007,

Thank you very much. We are going to reboot the server Monday. I hate to do anything before the weekend. Is there a standard procedure for rebooting the CP box?

The IT Manager and I greatly appreciate all the prompt assistance we have received on this issue. I will let everyone know next week the result.

 

[SSJVirus007]

No special thing you have to do. Just reboot it like a Server. For SP2, do not download from Microft. Have a phone tech do it, they have to download from Nortel website and they are 2 parts to this. Here are the 2 number.

CPDSKPEP001S and CPSECPEPSP2S

 

[mclark13]

Just wanted to let everyone know that we changed the: b) Use Administrator Tools > Local Security Policy > Security Options. Change the "Microsoft Network Client Digitally sign communications (always)" setting to "Disabled" and reboot the server and reboot the server and it is now backing up just fine.

Thanks again for everyone's help.

 

[soltdahg]

We had the same issue after hour 5.0 Upgrade- (vendor blamed our Network) but we apped the fix to Local Security Policy listed above.

Just a question, where is this documented on Nortel's site? I'd like to get it so I can go back to the vendor for some "adjustments" to the labor on the bill for this job.