4760 - OXO Save/Restore failure over PPP
Posted: 30 Nov 2005 05:56
Hi all,
I am running 4760 R3.1.07.00c Patch 2 server for our in house OXE and have recently added an OXO via PPP dialup (for testing purposes.) I can run the Configuration Application (via PM5) on both server and client and receive urgent Alarms ok, but if I schedule a save or restore of the OXO from a client, the task fails. If the save/restore is scheduled from the server, it is successfull every time. The scheduler log file indicates "Error reading LDAP configuration" when the task is run from a client.
All other LDAP related functions (Reporting, System Directory modifications etc) work ok. Port 389 (LDAP) is open between client and server. I am running XP Pro SP2 on the client with the inbuilt firewall turned off.
The 4760 server is running R3.1.07.00c Patch 2, and the OXO is R4.1. All other functions relating to the OXO (synchronisation, Urgent Alarms etc) work correctly.
The server is configured as part of a domain.
Despite what TCV049 says about not being able to receive Urgent Alarms on a 4760 in a domain, it is possible. You need to create a Domain User with RAS Dial In Rights and enter this user in the OXO Centralised Management, using just the username and password (not DOMAIN\\USER) and it will work correctly.
If anyone has any solution to my problem, I would be very greatfull.
I am running 4760 R3.1.07.00c Patch 2 server for our in house OXE and have recently added an OXO via PPP dialup (for testing purposes.) I can run the Configuration Application (via PM5) on both server and client and receive urgent Alarms ok, but if I schedule a save or restore of the OXO from a client, the task fails. If the save/restore is scheduled from the server, it is successfull every time. The scheduler log file indicates "Error reading LDAP configuration" when the task is run from a client.
All other LDAP related functions (Reporting, System Directory modifications etc) work ok. Port 389 (LDAP) is open between client and server. I am running XP Pro SP2 on the client with the inbuilt firewall turned off.The 4760 server is running R3.1.07.00c Patch 2, and the OXO is R4.1. All other functions relating to the OXO (synchronisation, Urgent Alarms etc) work correctly.
The server is configured as part of a domain.
Despite what TCV049 says about not being able to receive Urgent Alarms on a 4760 in a domain, it is possible. You need to create a Domain User with RAS Dial In Rights and enter this user in the OXO Centralised Management, using just the username and password (not DOMAIN\\USER) and it will work correctly.
If anyone has any solution to my problem, I would be very greatfull.