Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?
On Sunday, May 16, 2021 at 2:35:22 PM UTC-7, Bry Pas wrote:and use Linux or Windows tools to look at paths to that system to see whether the paths are up, and maybe whether the system itself is up (or at least whether its TCP/IP handlers are up).
Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?I don't remember whether there is a different error for system down.
Do you know whether the Expand paths in your network are carried via TCP/IP vs. an old-style leased line or some other old-style way? If you know the Expand paths are carried over TCP/IP, you should be able to learn the IP address of the target system
Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?
Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?
On Sun, 16 May 2021 14:35:21 -0700 (PDT), Bry Pas <bryanp...@gmail.com> wrote:Hello All,
Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?Whether your connection is old-fashioned WANs or (more likely these days) TCP/IP, Expand has configurations on those paths for retransmissions and timeouts.
Those are designed to allow the connections to be resilient to temporary commucations issues.
TCP/IP also has similar settings, with defaults for end-to-end processing. If I recall, the per-session defaults can be overridden in the Expand configuration.
Do you have access to the EMS logs on your system and on the target system? Can you check to see if errors were reported wheny your FUP failed?
You didn't say whether this was a 'constant' failure which never resolves, or an occasional one. Although it's been a very long time since I diagnosed these,
I seem to remember that it's possible to configure path connection parameters in such a way that large file transfers can cause failures.
Have you reached out to the Systems Administrators to see if they're aware of the failures?
Good luck with this. Please keep us informed with what you learn.
Bill
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 286 |
Nodes: | 16 (2 / 14) |
Uptime: | 85:35:01 |
Calls: | 6,495 |
Calls today: | 6 |
Files: | 12,099 |
Messages: | 5,276,973 |