TCP/IP quits after 48 hours












1















I have a problem with a (remote) server running SCO UNIX. It's been working for years, but was recently moved, and I changed its IP address & gateway address. Since then it works perfectly until after EXACTLY 48 hours, other machines can't connect to it through the network, and can't ping it. The server also can't ping any other machines or the gateway on the network. Everything is done by IP address (no DNS issues). The server continues to function normally otherwise. I tried replacing the network switch to no avail. Restarting the server fixes everything for 48 hours.










share|improve this question









New contributor




Stan C is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • interesting timeframe; is there DHCP involved?

    – Jeff Schaller
    2 hours ago











  • Are you sure the IP is unique? I had a similar problem once caused by ARP collisions, but 48 hours is rather long

    – Michael Mrozek
    2 hours ago











  • Just TCP or all IP? How precise are your timings?

    – ctrl-alt-delor
    2 hours ago
















1















I have a problem with a (remote) server running SCO UNIX. It's been working for years, but was recently moved, and I changed its IP address & gateway address. Since then it works perfectly until after EXACTLY 48 hours, other machines can't connect to it through the network, and can't ping it. The server also can't ping any other machines or the gateway on the network. Everything is done by IP address (no DNS issues). The server continues to function normally otherwise. I tried replacing the network switch to no avail. Restarting the server fixes everything for 48 hours.










share|improve this question









New contributor




Stan C is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • interesting timeframe; is there DHCP involved?

    – Jeff Schaller
    2 hours ago











  • Are you sure the IP is unique? I had a similar problem once caused by ARP collisions, but 48 hours is rather long

    – Michael Mrozek
    2 hours ago











  • Just TCP or all IP? How precise are your timings?

    – ctrl-alt-delor
    2 hours ago














1












1








1








I have a problem with a (remote) server running SCO UNIX. It's been working for years, but was recently moved, and I changed its IP address & gateway address. Since then it works perfectly until after EXACTLY 48 hours, other machines can't connect to it through the network, and can't ping it. The server also can't ping any other machines or the gateway on the network. Everything is done by IP address (no DNS issues). The server continues to function normally otherwise. I tried replacing the network switch to no avail. Restarting the server fixes everything for 48 hours.










share|improve this question









New contributor




Stan C is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I have a problem with a (remote) server running SCO UNIX. It's been working for years, but was recently moved, and I changed its IP address & gateway address. Since then it works perfectly until after EXACTLY 48 hours, other machines can't connect to it through the network, and can't ping it. The server also can't ping any other machines or the gateway on the network. Everything is done by IP address (no DNS issues). The server continues to function normally otherwise. I tried replacing the network switch to no avail. Restarting the server fixes everything for 48 hours.







networking tcp-ip sco






share|improve this question









New contributor




Stan C is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Stan C is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 hours ago









Jeff Schaller

43.3k1159138




43.3k1159138






New contributor




Stan C is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 hours ago









Stan CStan C

61




61




New contributor




Stan C is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Stan C is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Stan C is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • interesting timeframe; is there DHCP involved?

    – Jeff Schaller
    2 hours ago











  • Are you sure the IP is unique? I had a similar problem once caused by ARP collisions, but 48 hours is rather long

    – Michael Mrozek
    2 hours ago











  • Just TCP or all IP? How precise are your timings?

    – ctrl-alt-delor
    2 hours ago



















  • interesting timeframe; is there DHCP involved?

    – Jeff Schaller
    2 hours ago











  • Are you sure the IP is unique? I had a similar problem once caused by ARP collisions, but 48 hours is rather long

    – Michael Mrozek
    2 hours ago











  • Just TCP or all IP? How precise are your timings?

    – ctrl-alt-delor
    2 hours ago

















interesting timeframe; is there DHCP involved?

– Jeff Schaller
2 hours ago





interesting timeframe; is there DHCP involved?

– Jeff Schaller
2 hours ago













Are you sure the IP is unique? I had a similar problem once caused by ARP collisions, but 48 hours is rather long

– Michael Mrozek
2 hours ago





Are you sure the IP is unique? I had a similar problem once caused by ARP collisions, but 48 hours is rather long

– Michael Mrozek
2 hours ago













Just TCP or all IP? How precise are your timings?

– ctrl-alt-delor
2 hours ago





Just TCP or all IP? How precise are your timings?

– ctrl-alt-delor
2 hours ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






Stan C is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505675%2ftcp-ip-quits-after-48-hours%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








Stan C is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Stan C is a new contributor. Be nice, and check out our Code of Conduct.













Stan C is a new contributor. Be nice, and check out our Code of Conduct.












Stan C is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505675%2ftcp-ip-quits-after-48-hours%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Histoire des bourses de valeurs

Why is there Russian traffic in my log files?

Rename multiple files to decrement number in file name?