On Tue, 22 Jul 2003 13:19:49 GMT, Patrick D <[log in to unmask]> wrote:
> Hello
>
> I have an old application which transfers files from a DOS PC with DSCOPY
> The PC has DOS 6.22, LAN-MANAGER client and some others net files from HP ( as ARPA and so on)
>
> I can transfer files with DSCOPY from my local HP3000 ( MpeiX 5.5) with the command
>
> DSCOPY -A -r localserver#user/password.account,group#remotefile localdisk\localfile
>
> The same command on a remote HP3000 ( MpeiX 7.5) fails
>
> DSCOPY -A -r remoteserver#user/password.account,group#remotefile localdisk\localfile
>
> with the error
> DSC005: Unable to connect to source node
>
> On the remote HP3000 user,password,account,group,remotefile exist
> It's not a resolution name problem, remoteserver is in the Hosts file, and 'PING remoteserver' is OK
> I tried a fully qualified domain name ( DSCOPY -A -r remoteserver.site.organization.country#   ..... )
> and the IP adress ( DSCOPY -A -r n.n.n.n# ..... ) and it fails too
>
> I can use DSCOPY from the local HP3000 to the remote HP3000
>
> I cannot use FTP actually ( too much things to change on the PC in this too short time window !)
>

Problem solved
By looking the trames with a protocol analyser, I saw that was a name resolution problem.
In fact, HP NS-VT layers need a special syntax for the name in the HOSTS file, when the server is not in
the same IP range
This line can be wrotten with a utility called INETNAME
and the line is :
ip adress               host            comment
xxx.xxx.xxx.xxx         ServerName      #NSHOST

DSCOPY uses the comment in the resolution  !

Strange, isn't it ?

Patrick



--
* remove '.don't.spam' and '.invalid' from my eMail address if you want to write me *
* enlevez '.don't.spam' et '.invalid' de mon adresse eMail si vous voulez m'écrire  *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *