搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

When I enter an about: item ff takes 2 min to load, error: can't find 192.168.1.200, address no longer in use, where to look?

  • 10 回覆
  • 1 有這個問題
  • 21 次檢視
  • 最近回覆由 cor-el

more options

When I enter any about: item ff takes over 2 minutes to load & comes up with an error message "Can't connect to 192.168.1.200". Now that's an old local server which is no longer in use, and obviously the IP is still somewhere in the settings so ff is looking for it. I've checked every item under about:about but can't find the IP, where could (should) I look. Thanx

所有回覆 (10)

more options

Have you done a Search in about:config? Search field at the top of that "page".

more options

as i wrote, i did a search on every pge that about:about lists

more options

and yes, the search field in about:config was my first idea. But no results.

more options

I noticed in your example, you have a space after the colon, such as- about: config. There should be no spaces. Copy and paste this, without any spaces- about:config and see if that works.

more options

If you click a link on the about:about page then you should open these page without a problem.

more options

Thanks for trying to help folks but I'm an experienced user and basically know what I'm doing. So pls. read carefully & don't jump to the next – obvious looking – solution. There are several "pages" in the "about:" section, I've gone through all of them, used search functions when available and done my part, I'm looking for experienced help. Pls. read the question carefully and reply if you have an idea. Just for the record, once again: Somewhere in a config file deep down in the basement of my ff installation there's a reference to a local server (192.168.1.200) that doesn't exist anymore, but ff thinks it still does, because it's in the config file. So everytime I call an "about:" page, there's a stall of two minutes or more, while ff is looking for that server. He then comes up with a failure notice. It's just annoying, not dangerous, and I thought I might try and find it.

Thanx for all the help.

Take care

more options

andreigler said

When I enter any about: item ff takes over 2 minutes to load & comes up with an error message "Can't connect to 192.168.1.200". Now that's an old local server which is no longer in use, and obviously the IP is still somewhere in the settings so ff is looking for it. I've checked every item under about:about but can't find the IP, where could (should) I look. Thanx

A few things don't add up here. 1. 192.168.x.x is a Router internal IP address not a Web Site. 2. What old local server are we referring to? Site location? 3. Is the server is no longer used the system will search for it however long it takes and then returns a ""Can't connect to 192.168.1.200" or "Server can't be reached".

That is what it would do. All Browser will search for this address when you input it to the url not just firefox itself.

If you type at the url: 192.168.1.200 on any browser - it will look for that IP address and if that isn't present or part of the network in the Router IP address it will eventually not find it. What you need to to is log into the Router and then look at your IP address listing to see what is listed on there first.

more options

Let me anser you point by point

A few things don't add up here. Yes. For instance you did'nt read my post properly

1. 192.168.x.x is a Router internal IP address not a Web Site. Where in my post is a "Web Site" mentioned? I explicitly wrote "a local server". Actually, it was my old NAS

2. What old local server are we referring to? Site location? What would you call "local" in IT? I'd say within the same network section as the PC we're talking about.

3. Is the server is no longer used the system will search for it however long it takes and then returns a ""Can't connect to 192.168.1.200" or "Server can't be reached". That's exactly what I described

That is what it would do. All Browser will search for this address when you input it to the url not just firefox itself. Actually, they'll search the lookup table in my local DNS. Never mind.

If you type at the url: 192.168.1.200 on any browser - it will look for that IP address and if that isn't present or part of the network in the Router IP address it will eventually not find it. But that's not what I was doing. I was typing "about:preferences" in my url field.

What you need to to is log into the Router and then look at your IP address listing to see what is listed on there first. No. What you need is to carefully read a post befor you reply to it.

Just for the record: This is my problem: When I enter any "about:" text in the url field, such as "about:preferences" or "about:addons", ff takes hangs for two minutes and then comes up with "can't find 192.168.1.200". And that's a NAS address in my local network which is no longer in use, and obviously the IP is still somewhere in the settings so ff is looking for it. I've checked every item under about:about but can't find the IP, where could (should) I look. My router is an Asus DSL AC56U, which runs my local network, and it definitly does not mention the aforementioned IP. And why should it?

more options

OK, as no one seems to have a meaningful answer, I'm closing this ticket. I forgot to mention that I'm running Mac OS X 10.12 (Sierra). And for the archives, I've found a workaround: In my local firewall, I've blocked NetAuthSysAgent for 192.168.1.200. So now, FF still throws an error message (can't connect to 192.168.1.200) but it does immediatly & doesn't try for two minutes or more. I will soon upgrade to 10.14, and this time I'll do a complete new install (very Apple-unlike) and get rid of all those skeletons in the closets.

由 andreigler 於 修改

more options

You can create a new profile to test if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.