We just had a similar case although it was a standard backup client.
As it finally turned out a firewall rule cut the connection after some minutes. And because of that no NW member had the chance to ever send/receive a proper error message. Therefore 'No error'.
After they increased the connection timeout between client and server/snode the situation did not change at all.
Finally we really deeply explained how the backups work and guess what - they have forgotten to also extend the timeout for the client/DD connection. They applied the same change here and ... bingo - no problems since then.
It is at least worth to verify your network/firewall timeout settings.
I've added static dns records to hosts file on networker server and it seems it resolved the issue. At least for the time being. It's funny, we've never had issues with our DNS servers.
bingo.1
2.4K Posts
0
April 3rd, 2018 10:00
We just had a similar case although it was a standard backup client.
As it finally turned out a firewall rule cut the connection after some minutes. And because of that no NW member had the chance to ever send/receive a proper error message. Therefore 'No error'.
After they increased the connection timeout between client and server/snode the situation did not change at all.
Finally we really deeply explained how the backups work and guess what - they have forgotten to also extend the timeout for the client/DD connection. They applied the same change here and ... bingo - no problems since then.
It is at least worth to verify your network/firewall timeout settings.
LTO6
1 Rookie
•
10 Posts
0
April 4th, 2018 22:00
Hello Bingo,
thanks for tip. Sadly, In my case, there are no firewalls between the devices that could affect it.
LTO6
1 Rookie
•
10 Posts
0
April 12th, 2018 00:00
Hello again,
I've added static dns records to hosts file on networker server and it seems it resolved the issue. At least for the time being. It's funny, we've never had issues with our DNS servers.