Are you using Network Manager to manage your networking?
If so, try running the following in an elevated console
netconfig -f update
If the above works, then you’ve been bitten by a bug that’s discussed elsewhere that will likely be fixed soon.
After running once, you shouldn’t need to run it again.
Speculation based on the apps you describe working or not…
The apps that aren’t working generally do DNS lookups often so when name resolution isn’t working, they’ll fail.
The apps you list that are working either use a different name resolution system (Tor) or heavily cache lookups, so won’t fail as quickly as the other apps.
And, I’d be curious if you use IP addresses rather than names when you SSH and mount your NFS.
SPOT ON. That did it. Now we’re back as it should. Thanks!
If the above works, then you’ve been bitten by a bug that’s discussed elsewhere that will likely be fixed soon.
After running once, you shouldn’t need to run it again.
Speculation based on the apps you describe working or not…
The apps that aren’t working generally do DNS lookups often so when name resolution isn’t working, they’ll fail.
The apps you list that are working either use a different name resolution system (Tor) or heavily cache lookups, so won’t fail as quickly as the other apps.
And, I’d be curious if you use IP addresses rather than names when you SSH and mount your NFS.
TSU
Yes, SSH and NFS connects by ip address. Didn’t see the differnce.
Thanks again, and sorry for asking for this again, didn’t know what to search for.
FYI
All directed network connections generally rely most basicly on IP addresses.
If all your connections only used IP addresses, you wouldn’t have seen any problem with each of the different apps you noticed were or were not working.
But,
Several of your apps don’t ordinarily connect to remote machines by IP addresses, they use names which through a system called host name resolution, translates the name to an ip address. When this name resolution doesn’t work, then anything relying on it fails.
In your case, each time you used a web browser (even Tor), you tried to connect to the remote address by <name> which was broken. If you are running Tor using the TBB, then Tor has its own self-contained name resolution system and doesn’t rely on your system’s, so Tor was unaffected.
running the netconfig command fixes the problem (I take no credit, it’s been discussed in other threads).