What's new

Ping works only after reboot

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Deepcuts

Regular Contributor
Hello,

I am having a strange issue between two locations, same ISP.

Location A
Dell server.
Static public IP without any firewall in front.
Windows 2008 Server R2

Location B
Asus RT-N56U doing NAT for a small network.
Static IP without any firewall in front.

Problem
Some times, after a server reboot in Location A, connectivity from Location A to Location B and vice-versa is affected.
Meaning, I cannot ping A from B or B from A
I can access some services from B to A while other services I cannot. Meaning, I can access a MySQL service while a SIP service does work/register
Only a server reboot in Location A solves the problem. Ping works and all services work also.

This baffles me, as I have tried turning off firewall in both locations without any positive result.
In Location A I have no antivirus nor other security program/appliance.

What can cause a problem like this?
Anyone else ever met such a problem?
 
what kind of server is in location A? Is it a VPS or does it have the computing power to handle all the random traffic? You need to have the firewall enabled and controlling access to the services you host otherwise the system will get swamped by random traffic. It happens a lot from the internet usually by bots scanning and trying out different things to utilise any weakness.

For me since my ISP gives me a static IP and also supplies internet to many educational institutions i get so much random traffic from brute forcing to routing attempts and usual scanning but using a really good firewall frees up so much network capacity and CPU.

Aside from that see how the server in location A is connected to the internet. If it is fully exposed and you've configured the services correctly than it should work fine. Try using UPNP on the router in location B as well.

If both are using the same type of internet with a router between than use port forwarding and UPNP. It could also be the routers arent stable either which is expected from consumer routers.
 
Location A:
Stand alone Dell PowerEdge server (not shared), with plenty of power.
Location A Server with Static IP fw off<> Fiber optic converter A<>------------------------------<>Fiber optic converter B<>Location B Router RT-N56U fw off<>Internal Network

The weird thing is that without any setting changes, after a server reboot in Location A, everything will work just fine...until a future server reboot, when it might work or it might not work, depending on....something I still haven't found :)

I have just reset winsock and waiting for the next time it will happen. Or not, hopefully.

Network capacity is plenty, having 1 Gbps on both locations.
 
finally you mentioned how they were connected. The problem would mostly be with windows server, you could also check your router to make sure it is working properly as well.

You could try checking your windows server configurations to make sure it is properly configured. Check for software conflicts and other things in detail and go through the services and scheduled tasks. it sounds like when you reboot not everything runs properly.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top