Customer provided these problem remarks (actual file qualifiers were substituted
by
name_letter):
We have
a problem when XCOM for Windows tries to access a NAS network path
using UNC. Client are trying to use \\name_a.name_b.name_c.name_d\name_e
as remote path--but every time they try it gives XCOMN0322E Cannot access
file server: The specified network password is not correct.
Client ran several tests
and when they created a symbolic link with command
mklink /d E:\name_g\name_h \\name_a.name_b.name_c.name_d\name_f
the transfer
completed correctly.
The user--shared files--path all have the correct permissions.
-
OS : Windows
Release : 11.6
Component : CA XCOM Data Transport for Windows
Support provided these comments:
-
Our understanding is that you are initiating a transfer from a UNIX system to
Windows and it is failing. The message received is XCOMN0322E Cannot
access file server: The specified network password is not correct.
Based on the command provided earlier you have the value for REMOTE_FILE=
with more slashes than necessary:
\\\\name_a.name_b.etc.\\name_f\\name_i\\etc.
Normally a UNC path would be:
\\name_a.name_b.etc.\name_f\name_i\etc.
Suggestion:
Please try to initiate the transfer from UNIX to Windows with the proper UNC
path specified for REMOTE_FILE= and provide us with the outcome. If the
transfer fails we would need for you to reproduce the problem after
turning on the XCOM trace on Unix and Windows.
-