Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

As far as I know, ping can test a given port. If you ping the server via the ip address and it times out, then you have network-level issues (not related to SQL Server probably) that should be addressed there.

0
Posted

As far as I know, ping can test a given port. If you ping the server via the ip address and it times out, then you have network-level issues (not related to SQL Server probably) that should be addressed there.

0

As far as I know, ping can’t test a given port. If you ping the server via the ip address and it times out, then you have network-level issues (not related to SQL Server probably) that should be addressed there. I’m not a network expert by any means, but I’d think there would be clues in the system event viewer of the server. If you wanted to go very low-tech, you could have a workstation run a command file containing something like this: :Start DATE /T >>PingLog.txt TIME /T >>PingLog.txt PING xxx.xxx.xxx.xx >>PingLog.txt GOTO Start That would run until cancelled (with Ctrl-Break), and write the date, time and PING results to a log file which could then be viewed to determine exactly when the server stopped responding. Hope this helps.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123