Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

"The connection has timed out....."

  • 6 trả lời
  • 1 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi zeroknight

more options

I have had no trouble using Firefox for many years and am able to access all/any websites excepting for one which upto a few months ago I had no trouble with. The one that I am unable to access is

  https://www.scc-online.org 

and all I get is the "The connection has timed out.." comment on an otherwise blank screen. I have contacted the webmaster who says that I am the only one with this problem. My neighbour who uses MS Edge has no trouble in displaying the website. He uses the same ISP as I do but uses Windows 11.

The webmaster says that it might be that I am using Windows 7 64bit and that Firefox cannot handle this particular website. Alternatively he suggested that my ISP was the cause of the problem although I have been using the current ISP for over 20 years and have never had this type of problem.

I have three computers all with Windows 7 and Firefox and they all have the same problem.

Is there any help available for me as the information on the "website" is important and I do not wish to have to go to my neighbour to view the website?

Les Sondheim, Parksvville BC, Canada

I have had no trouble using Firefox for many years and am able to access all/any websites excepting for one which upto a few months ago I had no trouble with. The one that I am unable to access is https://www.scc-online.org and all I get is the "The connection has timed out.." comment on an otherwise blank screen. I have contacted the webmaster who says that I am the only one with this problem. My neighbour who uses MS Edge has no trouble in displaying the website. He uses the same ISP as I do but uses Windows 11. The webmaster says that it might be that I am using Windows 7 64bit and that Firefox cannot handle this particular website. Alternatively he suggested that my ISP was the cause of the problem although I have been using the current ISP for over 20 years and have never had this type of problem. I have three computers all with Windows 7 and Firefox and they all have the same problem. Is there any help available for me as the information on the "website" is important and I do not wish to have to go to my neighbour to view the website? Les Sondheim, Parksvville BC, Canada
Đính kèm ảnh chụp màn hình

Tất cả các câu trả lời (6)

more options

What do you have set here? see screenshot I doubt it's a Win7 issue, but let me boot up my laptop and check.

more options

All is well for me on Win7. see screenshot Who are you using for DNS?

more options

I have now tried a number of different computers using different ISPs one of which was a city library reading room computer. It and the others all returned the 'Timed out..' comment on the blank screen. I also contacted my ISP technical service and asked them to attempt to access the website. The 'phone' techy' could not access the site and referred the problem to the Tech Manager. He got back to me after a while and confirmed that he was unable to get a result any different than mine. He said that the problem was not at their end and that they had not had this problem with any one else. I am about ready to give-up on the whole thing as the webmaster, to whom I spoke via telephone, maintains that it is my side which is the problem.

more options

It's definitely not a site issue because it works for me on Win7. Who are you using for DNS? What security software are you running? Just to confirm, it works for you in other browsers on Win7?

more options

This little tool helps with verifying DNS performance. https://www.grc.com/dns/benchmark.htm

more options

Try changing DNS over HTTPS (DoH) to "Off" or "Max Protection" and in Connection Settings change "Use system proxy settings" to "No proxy".

Does it still happen in Troubleshoot Mode?