Guidance on Troubleshooting Subtle Networking Problem

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Ceyarrecks

Active member
Sep 29, 2020
27
2
Excuse me Please:

over last few weeks, maybe a month, frequent intermittent network/DNS connectivity issues are being experienced by my FireFox browser. Also, it kinda feels like the networking problems seem more noticeable in the evening, no so much in mid-day.
note, this a recent and noticeable change to Internet browsing. Sprint WISP modem consistently displays 4/5 signal strength (lessened signal might have been potential cause)
about six months (i guess) ago, I had newly implemented user.js functionality for limiting Firefox's default lack of privacy, tracking removal, improved networking, etc. (copy can be posted on demand) and with such, FF was SCREAMINGLY fast! more so with the Raspberry Pi-Hole also implemented on the network and is SOLE DNS provider many months ago.

just this last few weeks or so, SOMETHING changed. and I am uncertain where to begin testing for something that might be deep in OS, or on ISP side.
additional note about my environment: NOTHING changes, no patches, no versioning, no updates, NOTHING.
so, all things being equal, if the same car is driving on the "same" roads, as it were.

Now, the browser would frequently display a Server not found page, yet spamming Refresh/Try Again causes browser to display "Looking up site..." connect, and display page of site I was just browsing!

I have eliminated as cause:

1. Firefox Sandbox contents {emptied Sandboxie sandbox, reloaded FF as though freshly installed} no change.
2. DNS swapped on TCPIP between both Pi-Hole & direct .3 Cloudflare and back to Pi-Hole, no change.
2a. also used both .1 and .3 CloudFlare on Pi-Hole, no change.
3. user.js adjustments with and without, no change
4. Rebooted PC multiple times, no change
5. all networking equipment powered down each evening, power restored next morning, no change.

Same problem on FFv56 as well as Waterfox v2010.10(64bit) Portable.

I have both of EFF.org's HTTPS Everywhere (not currently set to FORCE ALL HTTPS) and Privacy Badger, with reminder, these both have been present on install for years without adversity.

DNS on TCPIP as well as IP are both statically assigned.
DNS Service has NEVER been enabled, ever.

I recall (but can not now find the screenshot I took) doing CLI tracert tests to www.google.com, and strangely, was initially NOT resolving, after a couple attempts would then start to function.

seemingly, it is though DNS is being intermittently blocked (or not responded to) though I do not know what further tests I can run; any tests, or networking testing software, or suggestions greatly appreciated.
CAH

p.s.
it should also be noted that I have also run several different Live CD AV scans on this system, nothing was found.
 
Strange behavior.

So, what exactly makes you think that DNS is not working? You can manually test DNS queries using nslookup at the Command Prompt.

Code:
## try and resolve using your default DNS
## this should ALWAYS work
nslookup google.com

## try and resolve using 3rd party DNS servers
nslookup google.com 1.1.1.1
nslookup google.com 8.8.8.8

If domains resolve, then DNS should not be a problem.

The ammount of customizations you have on Firefox could be causing some issues. I would consider creating a clean Firefox profile and test your experience without any plugins or modifications.


You don't have to delete your current profile and settings. You can create new ones and use them at the same time. To manage and select profiles, type in the address bar:

Code:
about:profiles

1613789225314.png
 
in using nslookup, it seems there is something amiss with Pi-Hole.
However, in looking into their Help forum, it seems they require one to be fully versed in Linux to frame questions in just a right way per their format to even submit.
so, i have a broken pi-hole.
thanks for the nslookup test.
 
  • Sad
Reactions: Barry Wallis
In line with JulioHM's FFox profile comment... A troubleshooting step I use is to create a new user profile on the computer and test the issue. If it is resolved - it's likely user profile related - if not, computer / OS / system related or network (outside of the system) related.