11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHRENNTECH again....
Leading reported evidence
Reset router all good
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Leading evidence: 'Reset router all good' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Reset router all good' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I find that many network providers use marginally performing DNS servers that can cause havoc at the edges of the internet and present symptoms similar to what you were seeing.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I find that many network providers use marginally performing DNS servers that can cause havoc at the edges of the internet and present symptoms similar to what you were seeing.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
11 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
What issue were you having? If you post the URL you're trying to hit and the issue you're having, it's easier to confirm the issue.
There was a period of a couple of hours today where every thread I tried to open on Rennlist was resulting in a 500 error. I've also noticed that when I have issues with one Internet Brands-hosted site (like Rennlist and Corvetteforum), it happens on the others, so I'm assuming they're hosting multiple sites from the same location...
www.RennTech.org
Safari 9.1.3 Mac Pro
I get the "Safari can't open the page because the server where page located isn't responding"
I've tried everything I know! Course I'm an old broken down ex-railroader!
Just upgraded to Safari 10. No improvement.
Well, never mind! I tried on my "smart phone" and it won't access either. Disabled Wi-Fi on phone and it jumped right on Renntech! Headed to the router next or a call to service provider.
At least I now have the latest Safari. Thanks JTT.
I find that many network providers use marginally performing DNS servers that can cause havoc at the edges of the internet and present symptoms similar to what you were seeing. Consider adding one or two other known good outside DNS servers (i.e. I think Google supports public DNS usage).
8.8.8.8 and 8.8.4.4 are the Google free DNS servers. Liberating yourself from your ISP's likely crappy DNS infrastructure is a great idea.
If you are security-minded, Norton, Avast, Comodo, and more offer "safe" DNS; known-evil sites are blacklisted at the DNS level so it's harder to get pwned.
This is a source reference. Confirm exact model applicability in the original material.
