[RESOLVED] Server not found with latest NoScript

[Grumpy Old Lady]

That's always happened more-or-less with my install of Fx/NS on this XP machine. I've had NS almost since it came out on AMO and I can't remember what it was like without NS, and I'm not prepared to run Fx without NS for any standing tests so I am probably not equipped to comment on the tech stuff, but I do have long experience with Fx/NS on OS X 10.3.9 and can make comparisons across systems if it's any use.
On first resuming from idle disconnect (when the system is put into standby with the XP power management functions) there is almost always a 'server not found' on the first dns request of the session - if that request is within about 60s of resumption of the session. Waiting 30s or more is the fix.
Depending on the hardware - I've had 3 different network adaptors on this machine while tuning it for best throughput of a clunky WAN - the sensitivity of this first request is more or less noticeable.

On the OS X machine there was rarely a server not found on resumption from standby.
I've always attributed it to DNS caching peculiarities between systems and hardware and ignore it.

Edit: I've just remembered that Thunderbird is equally sensitive to this first request after standby, so my contribution is definitely as a comparison between XP and other systems :-)

[GµårÐïåñ]

Agreed, running without NS is not an option for me but it would be nice to have less of the functional hits/misses/annoyances that prop up. Fx is sufficiently broken and full of flaws without giving it a hand Even though I was certain that its not a DSL issue, on therube's suggestion I had it checked and sure enough no problem and runs nearly 2 Mbits faster than the ISP average, on ANY machine on this DSL line and I use this machine on a client T1 line, same issue, I have used it on the company network of Multiple-T3 lines with an OC3 backbone and same problem, so I am 100% certain it has nothing to do with my internet connection or ISP. I support NS willingly and gladly install the latest and the most unstable version but it just gets to me when attempts to identify a problem sometimes get less attention than they should. Especially that the extensions I run, NS is the only one that relies on DNS and cache, other than Fx itself and since disabling NS fixes the problem, would suggest its something in there but no point pushing it I guess, everyone is convinced its a phantom.

[foxicat]

Hi,

first of all, thank you so much of sticking with me through the problem! Thank you, thank you!

@grumpy Old Lady: Just to clarify: my problem is NOT the first request after standby; I absolutely share the experience that the first request after standby gives the error message. That has always been the case for me also (Vista). But what has change for a couple of days is that the second request now is unsuccesful. Normally the second request reconnects me and I refresh once and the page is loaded. Now I have to refresh about 20-30 times.

Here is more information on my connection and what I tried.
- DSL broadband connection
- The only Firewall I have is the windows Vista firewall; I have never changes any settings there, the settings have been the same since getting the machine.
- The automatic discconnection time span can be chosen in the software of the router I use (also tried to change the time span from 5 minutes to 30 minutes, but it does not help with the problem because the problem comes after the disconnection)
- I also read about a problem with DNS Cache so I flushed the DNS Cache in my machine with ipconfig /flushdns, that was one of the first things I did --> did not help
- I created a new profile in Firefox with only NoSCript --> problem still there
- problem does not occur in IE

Now, the last thing I tried is the advice by Giorgio Maone: I clicked once "Address not found" because no connection, then I was reconnected, I waited 30 seconds: the page did load after 3 or 4 times (not 20-30 times) as usual. So I could reduce the number of times I needed to reload the page, but the page is not there on second click like it used to be.

What else can I try because I want NoScript back...

Thank you again

[Grumpy Old Lady]

Hi foxicat,

Don't worry about my posts too much. I always try to add data when others are troubleshooting, and I was just trying to add for Giorgio's data that my XP system's observed first-up behaviour after standby is the same as yours.
In case it was a help with the big geek's interpretation of your particular problem.
And I think your reports of reducing the waits after Giorgio's suggestion indicate some progress in his thinking about it.
You don't have an unusual bit of software or hardware from your internet connection provider? Just a thought.

[Giorgio Maone]

Should be fixed in latest development build 1.9.7.81.

[foxicat]

Hi Giorgie Maone,

installed newest build (which was 1.9.7.84). And tried it out all day. By now the problem is solved! Thank you soooo much!!!!!!!!!!!!!!!!!!!!!

At first, after the upgrade to 1.9.7.84 I still had to click about 5 times till the page of the first click reloaded (which was already an improvement to the behavior before). I then had to reset my router anyway because of a blackout in our building and after that, the problem was solved: the page is reloaded immediately after re-connection, as it was before.

I tried a couple of times now and always no problem.

You are great, thank you again!
I'm really happy and appreciate your help!!

Bye and keep up the good work...

[dhg]

I've been seeing this same problem for years. I am currently using 2.9.0.4 and still having this problem.

[barbaz]

@dhg: This particular problem was surely resolved more than 6 years ago, your issue is likely similar but not identical. Can you please describe in more detail the particular symptoms you see?

[dhg]

@dhg: This particular problem was surely resolved more than 6 years ago, your issue is likely similar but not identical. Can you please describe in more detail the particular symptoms you see?

Sometimes (maybe only after coming out of sleep?) when I access a new URL (e.g., click on a link, click on a bookmark, do a search, load an unloaded tab), Firefox says "Server not found. Firefox can't find the server at" (wherever). Sometimes I've found that if I already have a tab open for a given site, I can continue to access other pages on that site. Regardless, when I get into this state, I am still able to access the problematic URL from other browsers; and the problem goes away when I restart the sick Firefox instance.

My recollection is that this problem has only occurred when NoScript is installed. However, it just now happened while NoScript is installed but disabled. I don't know enough about how extensions work to know whether that relieves NoScript of any guilt for this situation

[barbaz]

it just now happened while NoScript is installed but disabled. I don't know enough about how extensions work to know whether that relieves NoScript of any guilt for this situation

That conclusively shows it's not NoScript related. That's not the sort of ghosts that a disabled extension can leave.