Closed Bug 210769 Opened 22 years ago Closed 20 years ago

tries to dial out

Categories

(Core :: Networking, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: thorne, Assigned: darin.moz)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 I have a local server setup for web development stuff. When I load up some of the pages that contain ads, Mozilla trys to dialup to my ISP and connect to the internet (to load the ads). Reproducible: Always Steps to Reproduce: 1. 2. 3.
that's your OS setup, has nothing to do with Mozilla.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
well, my OS is setup to only dial a connection when I tell it to. Mozilla is the only browser out of the 4 I use for testing that does it (Mozilla, Netscape 7, Opera, and IE). It only started doing this recently too, maybe since 1.4rc1 or possibly sometime in 1.3.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
*** Bug 218666 has been marked as a duplicate of this bug. ***
Assignee: general → darin
Component: Browser-General → Networking
QA Contact: general → benc
Summary: trys to dial out → tries to dial out
I have exactly the same problem with Firefox 0.9.2 on my laptop. Laptop is using WIN XP Pro. This DOES NOT happen with my Mozilla 1.6 or with MS Exploder. This ALWAYS happens after it first opens and I try to go to whatever is the first site I wish to visit. This problem does not happen on my desktop. O/S is WIN XP Home.
I've heard other reports of this sort of problem. It seems that WinXP may store the information under different keys than other versions of Windows. And moreover there can be conflicting rules defined in the Windows registry. It may be the case that Mozilla should look at the rules in a different order. You should find the same behavior with Mozilla 1.7 and Firefox 0.9. If not, then please let us know. Also, can you please report the values of the following registry keys: HKEY_CURRENT_USER\Software\Microsoft\RAS Autodial\Default HKEY_LOCAL_MACHINE\Software\Microsoft\RAS Autodial\Default Thanks!
I am running W2K and am having the same problem, where Firefox tries to dial using my ISP connection, eventhough I have a LAN connection to the internet. This does not happen with IE. Details: OS: Win 2K SP4 Firefox: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Is there any way to send confirmation on this bug, as it is becoming VERY annoying.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.