Arcserve Client Logon Failure

[MikeMillerSC]

Hello,

I have a small computer service business and I am currently working with 2 customers who have the exact same problem using Arcserve 9.0 for Netware. One server is Netware 5.1 with SP 6 and the other is a brand-new Netware 6.5. On both servers, I am experiencing logon failures every time I submit a job from the client. I can submit one from the server console without any problem, but any type of job submitted from the client gets rejected.

One interesting thing on both these servers is that the AS Client will not authenticate in the "Change preferred server" section if you use the fully qualified domain name. It will authenticate admin, but not admin.fallon or CN=admin.o=fallon.

I have made several changes in NDS, granting the AS queue and user admin rights and so forth, but that does not seem to help.

I have started an e-mail tech support incident with CA, but it takes 2 days to get a response from those guys. I can remember when they used to provide free phone support.

Any suggestions would be greatly appreciated.

 

[paxo1]

You need a leading dot ie .admin.context

 

[Cyklops]

With the 'client' I assume you mean the Windows Manager for ARCserve for NetWare.
Do you use a password that exceeds the length of 15 Characters ? This is a manager limitation that doesn't count for the server console.

regards

 

[rdorseybhm]

Mike, did you ge this resolved? We are experiencing exact problem and just starting the troubleshooting process.

 

[breunigt]

Has anyone resolved this issue with BrighStor Backup. I am having the same issues and Computer Associates Tech Support is no help.

 

[teles]

It will authenticate admin, but not admin.fallon or CN=admin.o=fallon.
- - -

Do you enter the username exactly as you typed in the message? I had a similar issue and the non-intuitive fix was to UPPER CASE everything.

This style didn't work for me:
CN=admin.O=fallon

This style did work for me:
CN=ADMIN.O=FALLON

 

[breunigt]

I have used all caps,all lower case, leading dot no leading dot, everything you could think of and nothing seems to help.

 

[wilvries]

When you want to make connection with the manager to your server, you have to do two things:

1. make sure that the hostname of the server is in the hosttable of the client.

2. make contact to the server by name and NOT by ip-adress.

This is the only way to get a proper connection to the server.

succes.

 

[breunigt]

I can ping the server by host name only, but I still get the logon failure when trying to submit a job to the server from the manager