232899 - host does not resolve after cable Internet connection has been lost then restored.

Status: RESOLVED DUPLICATE of bug 227551

(Core :: Networking, defect)

Description

[Peter Kroll]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

I have several machines networked to a hub and a hub connected to a router and
the router connected to the cable modem. Sometimes the router or the cable modem
loses their connection to the Internet. Once I unplug and plug the router and
cable modem back in and the Internet connection is restored. Mozilla will not
resolve host names. If I close all mozilla windows, including mail and download
manager. Then start Mozilla again. It will then begin to work again.

Reproducible: Sometimes
Steps to Reproduce:
1. Open Mozilla and browse to some websites.
2. Physically lose the Internet connection
3. Try to surf while mozilla is still in online mode and enter domains which are
not in the cache.
4. Physically reconnect Internet connection
5. Attempt to accept domains/hosts which are not in cache. 

Actual Results:  
The host names do not resolve.

Expected Results:  
The host names should resolve.

I've marked this bug as critical because not only will no domains resolve I lose
all the work done in open windows if I'm forced to close them to get mozilla
working again.

Comment 1

[Peter Kroll]

Also, Im not sure if these bugs are related but they seem to have similar
problems with host names not resolving:
http://bugzilla.mozilla.org/show_bug.cgi?id=225379
http://bugzilla.mozilla.org/show_bug.cgi?id=208741

Comment 2

[Darin Fisher]

Peter,

Can you try toggling the online/offline state when this problem next happens? 
There's an icon in the lower-right hand portion of the browser frame that allows
you to toggle this state.  Please let us know if that helps.  Thanks!

Comment 3

[Peter Kroll]

I got this problem again today. I toggled to offline then to online in the lower
right corner of mozilla and then mozilla started resolving host names again,
without having to restart mozilla.

Thanks for the workaround. However, this is still a valid bug.

Suggestion:
When mozilla can't resolve a domain name, maybe whatever important routines are
restarted when offline/online is toggled should be called so mozilla makes sure
it's online. 

Comment 4

[Peter Kroll]

Toggling offline/online does not allow me to check mail. I can now browse but
I'm still unable to connect to POP3 servers.

Comment 5

[benc]

Darin: what do you think is failing that offline;online fixes?

Peter: I know this sounds a little silly, but can you give us a new set of
steps, just for MailNews? Their offline-online stuff is slightly different than
the browser interfaces.

Comment 6

[Peter Kroll]

Reproducible: Sometimes
Steps to Reproduce:
1. Open Mozilla and browse to some websites.
2. Open up mailnews and check your email.
3. Physically lose the Internet connection
4. Try to surf while mozilla is still in online mode and enter domains which are
not in the cache.
5. Physically reconnect Internet connection
5. Attempt to accept domains/hosts which are not in cache. 
6. In the browser toggle online/offline 
7. Browsing should now work, visit a web based mailer
8. Send an email to one of your POP3 accounts that you check in mozilla
9. goto already open mailnews window click Get Msgs

Actual Results:
Does not connect to POP3 server and download new mail

Expected Results:
mailnews should contact POP3 server and download new mail

Comment 7

[SR]

I confirm this behaviour on versions 1.6 stable and on nightly Mozilla/5.0
(Windows; U; Windows NT 5.1; fr-FR; rv:1.8a2) Gecko/20040602.

Going offline/online fixes the browser bug but NOT the mailer bug.
Mailer cannot access to POP3 servers (I get no error, the mozilla icon on the
top right corner of the window doesn't start moving) although it can acces to
news servers (at least some).
Hence, mozilla MUST be restarted when this problem occurs.

I have not experienced this bug before using mozilla as main mail client. I used
to use mozilla as the main newsreader.

This is, in my opinion, a really important bug, as I've installed mozilla as
main browser AND mail client in several places, and every people experience the
same problem.

Comment 8

[Darin Fisher]

Interesting... the last comment mentions problems with POP mail, and not other
parts like the browser.  Brendan: you were experiencing this problem with POP
mail too, right?

Comment 9

[David :Bienvenu]

remember that POP doesn't cache connections - so it should be like http - it's
the new connection that's failing, which could mean some level below mailnews is
caching a dns lookup

Comment 10

[Darin Fisher]

hmm... very strange.  if HTTP works, but POP doesn't... hmm...

Comment 11

[Brendan Eich [:brendan]]

I think Darin and I saw a POP socket open across a laptop suspend/resume roaming
cycle (my laptop), and I resumed with a different DHCP'd IP address.  But Linux
didn't kill the socket post-haste, for which I blame Linux hippies.

This bug has OS: Windows XP, though.  Doesn't seem like what I saw.

/be

Comment 12

[SR]

(In reply to comment #11)
> I think Darin and I saw a POP socket open across a laptop suspend/resume roaming
> cycle (my laptop), and I resumed with a different DHCP'd IP address.  But Linux
> didn't kill the socket post-haste, for which I blame Linux hippies.

I don't use DHCP on some of the hosts on which I experience this problem, so the
bugs are probably distinct ones.

Comment 13

[:Gijs (he/him)]

Reporter, half a year later, can you still reproduce these bugs? To what extent
(ie, only pop, only http or something different)?

Comment 14

[SR]

bug, as reported in comment #7,  is still there (at least in mozilla 1.7.3).
I have no way to reproduce the bug and don't know if it's related to loosing
connection.
It's a major problem IMHO.

Comment 15

[Peter Kroll]

I believe this bug is still here. I do not have the same internet connection as
before, so it's hard to reproduce the sudden disconnection of the Internet.
Pulling out the network cable doesn't seem to do the same trick. I think the
Network cable has to be plugged and you lose connection from the router/ISP.
Then after connection is restored the browser displays the behavior described in
the above comments.

You can be sure if the bug wasn't specifically addressed and fixed then it still
exists. 

Comment 16

[Wayne Mery (:wsmwk)]

dup/related to bug 232585, bug 227551?

Comment 17

[Wayne Mery (:wsmwk)]

no response from reporter, Peter.

Stan/SR, duping to bug 227551, but without peter or you to check it's not just a guess.