Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 10116

Summary: netscape hangs
Product: [Retired] Red Hat Linux Reporter: sjdyer
Component: netscapeAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6.1CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-04-21 03:49:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description sjdyer 2000-03-10 22:00:48 UTC
Netscape communicator 4.7.2 hangs after setting proxy settings. I am using
squid 2-2-stable from web proxy. It hangs for five minutes after you start
netscape and comes back with can't find url. But if you hit reload it
bring's up the web page. Also after setting up mail for netscape using
jsentry 3.1 mail proxy and get my mail. Then the next time I start
netscape it hangs and does not ever respond. The only way to do anything
is to reboot system.

Comment 1 Bill Nottingham 2000-03-20 17:26:59 UTC
Sounds like you're having problems with name resolution;
what does /etc/resolv.conf look like, and how are you connected
to the net?

Comment 2 Bill Nottingham 2000-04-18 16:51:59 UTC
closed, lack of input.

Comment 3 sjdyer 2000-04-21 03:47:59 UTC
I am connecting through a dial up connection. the resovl.conf on server is
set to dns settings for isp and work station is set to go to server. As I
said before netscape navigator by it's self works fine through the redhat
proxy server. But netscape commnuicator does not. I did however fix the
problem by upgrading to netscape communicator ver 6.0.

Comment 4 Bill Nottingham 2002-01-28 06:30:12 UTC
If using a mozilla-based browser works, that's good. In any case, we really
can't fix internal netscape networking behavior, as we don't have access to the
source code.