OpenVMS FTP Not Working
Advance apologies: I know just enough about VMS to be dangerous. I hope this is the correct location to post this question as I couldn't find a VMS-specific topic.
On to the problem. We have a VAX attached to an analytical instrument that just collects data. Until recently, we've been able to FTP the data from the VAX to a PC, with the VAX as the FTP server. Then it started failing sporadically. Now it doesn't work at all. The symptom: On the PC at the command prompt we type: FTP [VAX_name]. The VAX responds: Connected to [VAX_name]. Then there is a long pause and finally this message appears: Connection closed by remote host. As far as I can determine, there have not been any changes made to the system, but I am suspicious of these denials.
With my limited knowledge, I poked around a bit on the VAX and ran: UCX>SHOW SERVICE FTP/FULL. FTP is enabled, but some of the information concerns me. The port is 21, protocol = TCP, but the address is 0.0.0.0. Is this right? If not, how do I change it?
Also, under the Security heading, Accept Host and Accept Network addresses are both 0.0.0.0. Could this be part of the problem?
On to the problem. We have a VAX attached to an analytical instrument that just collects data. Until recently, we've been able to FTP the data from the VAX to a PC, with the VAX as the FTP server. Then it started failing sporadically. Now it doesn't work at all. The symptom: On the PC at the command prompt we type: FTP [VAX_name]. The VAX responds: Connected to [VAX_name]. Then there is a long pause and finally this message appears: Connection closed by remote host. As far as I can determine, there have not been any changes made to the system, but I am suspicious of these denials.
With my limited knowledge, I poked around a bit on the VAX and ran: UCX>SHOW SERVICE FTP/FULL. FTP is enabled, but some of the information concerns me. The port is 21, protocol = TCP, but the address is 0.0.0.0. Is this right? If not, how do I change it?
Also, under the Security heading, Accept Host and Accept Network addresses are both 0.0.0.0. Could this be part of the problem?
ASKER
Sorry for the delay in responding - long weekend for me. Unfortunately, the reference you posted did not give me a solution. Still looking. Thanks!
ASKER
Problem solved. Unbeknownst to me, the network folks kindly disabled our port for reasons known only to themselves, and didn't notify me. Of course, this is the first thing I should have checked, but we'd had problems figuring out the VMS netowrking stuff and I let the computer intimidate me.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
might help
Reps