UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
"____ could not be found. Please check name and try aga
Moderators: Antony, Edward, profman, Ramona
7 posts
• Page 1 of 1
"____ could not be found. Please check name and try aga
by pickles » Thu 14 Apr, 2005 12:33 pm
We are running XP Pro and Netscape 7.0 on our new MPC 565. Had horrible ME for 5 terrible years. Very few problems (that weren't easily remedied) with XP. Running Zone Alarm Firewall as I have in the past with no settings changes between ME and XP. All went well until several days ago. For some odd reason, we get the "____ could not be found. Please check name and try again." everytime we attempt to go to a website....whether from a Yahoo search, our bookmarks, a hyperlink in email or "Open Web Location" from File. The 2nd time we attempt that same site....the page then loads. We have medium speed DSL and have always has speedy page loading and so this is really a bummer. It makes browsing irritating and time consuming because we must wait 5-10 seconds after initial attempt to access site before getting that error before we can actually try the 2nd time to get the site to load. We have done nothing differently (of which I am aware) except to allow some automatic updates and service packs for explorer, etc. We have IE's "firewall" disabled and allow Zone Alarm to handle our security needs. We run Norton Antivirus and we are wondering if some setting in this is causing the problem. We also use Pest Patrol to keep track of adware, spyware and keyloggers. I can't think of anything that we have done to have caused this irksome and annoying problem. Any advice would be greatly appreciated.
- pickles
- new member
- Posts: 4
- Joined: Thu 14 Apr, 2005 12:15 pm
Maybe Found Solution!
by pickles » Thu 14 Apr, 2005 1:47 pm
I unchecked the Script Blocking in Norton Anti-virus. This seems to have solved the problem....I hope. Hope this can help someone else. Thanks.
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
- pickles
- new member
- Posts: 4
- Joined: Thu 14 Apr, 2005 12:15 pm
by Alice » Thu 14 Apr, 2005 2:38 pm
That was thoughtful of you, posting a followup.
Not sure how the Norton AV script-blocking could have caused your Netscape problem, but, fwiw, I also had script-blocking disabled in Norton AV, when I had it installed (I'm using a different AV now). Instead, I was using Symantec's "noscript.exe" to disable the Windows Script Host. It's quite simple to use, and can be downloaded from a link in this article:
http://www.symantec.com/avcenter/venc/d ... sting.html
How to disable or remove the Windows Scripting Host
Also, in case it's helpful, here's a Symantec article on Norton AV and Firewall programs, including ZoneAlarm, that I remembered from a previous thread
http://service1.symantec.com/SUPPORT/na ... 2012355706
Configuring your firewall for use with Norton AntiVirus 2004 or 2005
Not sure how the Norton AV script-blocking could have caused your Netscape problem, but, fwiw, I also had script-blocking disabled in Norton AV, when I had it installed (I'm using a different AV now). Instead, I was using Symantec's "noscript.exe" to disable the Windows Script Host. It's quite simple to use, and can be downloaded from a link in this article:
http://www.symantec.com/avcenter/venc/d ... sting.html
How to disable or remove the Windows Scripting Host
Also, in case it's helpful, here's a Symantec article on Norton AV and Firewall programs, including ZoneAlarm, that I remembered from a previous thread
http://service1.symantec.com/SUPPORT/na ... 2012355706
Configuring your firewall for use with Norton AntiVirus 2004 or 2005
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319
-
Alice - Mozilla Champion
- Posts: 1790
- Joined: Sun 21 Jul, 2002 8:57 am
Root of the problem with my Netscape browsing
by pickles » Tue 19 Apr, 2005 10:00 am
Well, folks....me thinks I've found the reason why but still looking for the cure. My browsing woes began after XP SP2 was downloaded and installed. Since then (as I stated earlier) my browsing became bogged down seriously because of having to double load websites before Netscape would actually see them. I turned off sctipt blocking and this did seem to decrease the problem....but that was temporarily deceptive. I think the problem is due entirely to XP SP2 and it's security "fixes". What does anyone else noticed about their PC experience since XP's SP2 installation (if anything)?
Below is some info I gleaned from an XP book summary....
Windows XP SP2 is big step forward in security -- but it can break things
By John McCormick
"The release of Service Pack 2 for Windows XP marks a milestone in the life of this operating system. Microsoft is pulling out all the stops to improve security. So much so, in fact, that it will cause many problems—because SP2 de-emphasizes backward compatibility with legacy systems and code for the sake of security. Administrators need to know in advance just what SP2 will mean for the Windows XP systems on their networks.
Details
Windows XP SP2 will dramatically improve the default security configuration for XP in nearly every area, from e-mail to Web browsing to increased protection against the ubiquitous buffer overrun. But all of these security improvements won’t come without some considerable pain. ZDNetUK reports that Microsoft admits that as many as one application in 10 will experience problems due to the upgrade. (I consider that a conservative estimate.)
Here are some of the most important security changes that are part of XP SP2:
The Windows Firewall (formerly the Internet Connection Firewall) is now enabled by default, which should improve security for SOHO users. However, in a corporate environment, it could cause problems for users trying to connect to network resources. The firewall will also now activate much earlier in the boot cycle, even before the network stack is enabled. On shutdown, it will now remain active until after the stack is disabled.
The Messenger service is now disabled by default.
A pop-up ad blocker has been turned on by default.
A unified security application called the Windows Security Center has been added (for more information on this feature, see this News.com article). It’s supposed to bring all of the most basic security configuration information into one easy-to-manage place that will show whether your firewall is enabled, if your antivirus software is working, and if you have the latest software updates installed.
NX support is added to Windows XP. NX (no execute) will allow NX-enabled CPUs to mark certain areas of memory as nonexecutable; that is, any code pushed into those areas (perhaps by malware such as Blaster or other viruses) will just sit there unable to run and therefore will be rendered harmless. This will harden the OS against the notorious buffer overrun threats. NX is currently supported only for AMD’s K8 and Intel’s Itanium processors, but 32- and 64-bit support for this important security feature is expected in most future processor releases.
DCOM (the Distributed Component Object Model) gets a new set of restrictions in the form of an access control list for nearly every action of any COM server. There will also be a more detailed set of COM permissions, which will allow administrators to fine-tune COM permission policies.
There is improved port management. It will no longer be up to the application to close ports after it is finished. Before, if a developer left out the closing routine or the application crashed, a port could remain open and leave XP open to attack. SP2 encourages port management with an application white list that only a user with administrator privileges can alter. Placing an application (such as a peer-to-peer program) on the white list causes ports to be managed automatically. Such applications can also now be run as a regular user rather than needing local administrator privileges to open ports in ICF.
New RPC restrictions help tighten communications. The XP SP2 changes in this area let administrators fine-tune RPC services. This granular control over RPC will allow you to specify that a port be used for RPC even if the application is not on the white list. There are a lot of changes for RPC, including a new RestrictRemoteClients registry key that by default blocks most, but not all, remote anonymous access to RPC interfaces on the system. The RPC interface restriction will require an RPC caller to perform authentication, which makes it much more difficult to attack an interface and helps mitigate against Trojan attacks.
Potential problems
The NX protection mentioned above is an excellent example of something that is definitely a powerful improvement from the security standpoint. However, NX has already been reported to have caused considerable problems (at least in the 64-bit version). The biggest problem will come for applications that use just-in-time code creation. On the other hand, the .NET Framework common language runtime code already supports NX as implemented in SP2.
RPC changes are the most likely to wreak havoc with existing applications. In the pre-SP2 Windows XP implementation, there are literally scores of RPC-based services running, all of which provide a window for attack. That changes dramatically with SP2.
Because of the change in port management, if an application needs to open ports but doesn’t use stateful filtering, administrators installing it need to place the program on the white list. With the built-in firewall enabled by default, IPv4-application inbound connections for audio and video, such as for MSN or Windows Messenger, need to have their port opening and closing managed automatically. Inbound services connections (IPv4) will require some changes to configuration and/or code. Services that listen on fixed ports should ask users if the service should be permitted to open the port in ICF and, if so, the service should use the INetFwV4OpenPort API to alter ICF rules.
Another problem is the fact that Microsoft won’t be offering this service patch to those who hold pirated copies of Windows XP. This is reasonable enough, but there are a lot of illegal copies out there, especially in the Far East where a lot of worms get a quick foothold in the Internet. SP2 will apparently check product IDs looking for known pirated copies and will not install on systems with bad product IDs. This is understandable, but it will reduce the overall effectiveness of the security upgrade.
A lot of the potential problems posed by SP2 are beyond administrators’ control. Some programming code for custom applications will have to be rewritten, but at least now you know what to look for when problems come up, rather than deploying XP SP2 and finding out that it breaks your most important line-of-business application.
Final word
I expect to hear screams of pain as people deploy SP2 and discover that legacy applications no longer work, but those are probably the same people who complain so loudly (and legitimately) that Microsoft doesn’t deploy secure systems.
Nearly every security expert knew that, at some point, Microsoft would be forced to bite the bullet and take a big compatibility hit in order to solidify operating system soft spots—many of which are due to legacy code support. Plus, the XP SP2 changes will force developers to produce more secure applications and not just take advantage of a permissive Windows OS to write code that doesn’t pay attention to security.
Of course, I would never recommend that anyone widely deploy such a major upgrade the day it hits the street. You should install SP2 on a testing network (or at least a single testing system) as soon as possible, and begin compatibility testing for your specific applications.
Those of you who have the budgetary luxury of being able to conduct even more extensive testing and want to get a leg up on evaluating XP SP2 even before final release should check out the Technical Preview Program, which makes SP2 RC1 generally available for testing by IT professionals (not just those on the beta list). The initial download, which doesn’t include any support other than some Microsoft-sponsored newsgroups, requires Windows XP to be installed already. English and German versions of the update are now available and are over 250 MB.
As soon as you feel comfortable that Windows XP SP2 will not cause a significant interruption for users (or you have fixed the issues that would lead to a potential interruption), you should deploy SP2 company-wide. It’s an important upgrade that can only improve the security of your n"
Below is some info I gleaned from an XP book summary....
Windows XP SP2 is big step forward in security -- but it can break things
By John McCormick
"The release of Service Pack 2 for Windows XP marks a milestone in the life of this operating system. Microsoft is pulling out all the stops to improve security. So much so, in fact, that it will cause many problems—because SP2 de-emphasizes backward compatibility with legacy systems and code for the sake of security. Administrators need to know in advance just what SP2 will mean for the Windows XP systems on their networks.
Details
Windows XP SP2 will dramatically improve the default security configuration for XP in nearly every area, from e-mail to Web browsing to increased protection against the ubiquitous buffer overrun. But all of these security improvements won’t come without some considerable pain. ZDNetUK reports that Microsoft admits that as many as one application in 10 will experience problems due to the upgrade. (I consider that a conservative estimate.)
Here are some of the most important security changes that are part of XP SP2:
The Windows Firewall (formerly the Internet Connection Firewall) is now enabled by default, which should improve security for SOHO users. However, in a corporate environment, it could cause problems for users trying to connect to network resources. The firewall will also now activate much earlier in the boot cycle, even before the network stack is enabled. On shutdown, it will now remain active until after the stack is disabled.
The Messenger service is now disabled by default.
A pop-up ad blocker has been turned on by default.
A unified security application called the Windows Security Center has been added (for more information on this feature, see this News.com article). It’s supposed to bring all of the most basic security configuration information into one easy-to-manage place that will show whether your firewall is enabled, if your antivirus software is working, and if you have the latest software updates installed.
NX support is added to Windows XP. NX (no execute) will allow NX-enabled CPUs to mark certain areas of memory as nonexecutable; that is, any code pushed into those areas (perhaps by malware such as Blaster or other viruses) will just sit there unable to run and therefore will be rendered harmless. This will harden the OS against the notorious buffer overrun threats. NX is currently supported only for AMD’s K8 and Intel’s Itanium processors, but 32- and 64-bit support for this important security feature is expected in most future processor releases.
DCOM (the Distributed Component Object Model) gets a new set of restrictions in the form of an access control list for nearly every action of any COM server. There will also be a more detailed set of COM permissions, which will allow administrators to fine-tune COM permission policies.
There is improved port management. It will no longer be up to the application to close ports after it is finished. Before, if a developer left out the closing routine or the application crashed, a port could remain open and leave XP open to attack. SP2 encourages port management with an application white list that only a user with administrator privileges can alter. Placing an application (such as a peer-to-peer program) on the white list causes ports to be managed automatically. Such applications can also now be run as a regular user rather than needing local administrator privileges to open ports in ICF.
New RPC restrictions help tighten communications. The XP SP2 changes in this area let administrators fine-tune RPC services. This granular control over RPC will allow you to specify that a port be used for RPC even if the application is not on the white list. There are a lot of changes for RPC, including a new RestrictRemoteClients registry key that by default blocks most, but not all, remote anonymous access to RPC interfaces on the system. The RPC interface restriction will require an RPC caller to perform authentication, which makes it much more difficult to attack an interface and helps mitigate against Trojan attacks.
Potential problems
The NX protection mentioned above is an excellent example of something that is definitely a powerful improvement from the security standpoint. However, NX has already been reported to have caused considerable problems (at least in the 64-bit version). The biggest problem will come for applications that use just-in-time code creation. On the other hand, the .NET Framework common language runtime code already supports NX as implemented in SP2.
RPC changes are the most likely to wreak havoc with existing applications. In the pre-SP2 Windows XP implementation, there are literally scores of RPC-based services running, all of which provide a window for attack. That changes dramatically with SP2.
Because of the change in port management, if an application needs to open ports but doesn’t use stateful filtering, administrators installing it need to place the program on the white list. With the built-in firewall enabled by default, IPv4-application inbound connections for audio and video, such as for MSN or Windows Messenger, need to have their port opening and closing managed automatically. Inbound services connections (IPv4) will require some changes to configuration and/or code. Services that listen on fixed ports should ask users if the service should be permitted to open the port in ICF and, if so, the service should use the INetFwV4OpenPort API to alter ICF rules.
Another problem is the fact that Microsoft won’t be offering this service patch to those who hold pirated copies of Windows XP. This is reasonable enough, but there are a lot of illegal copies out there, especially in the Far East where a lot of worms get a quick foothold in the Internet. SP2 will apparently check product IDs looking for known pirated copies and will not install on systems with bad product IDs. This is understandable, but it will reduce the overall effectiveness of the security upgrade.
A lot of the potential problems posed by SP2 are beyond administrators’ control. Some programming code for custom applications will have to be rewritten, but at least now you know what to look for when problems come up, rather than deploying XP SP2 and finding out that it breaks your most important line-of-business application.
Final word
I expect to hear screams of pain as people deploy SP2 and discover that legacy applications no longer work, but those are probably the same people who complain so loudly (and legitimately) that Microsoft doesn’t deploy secure systems.
Nearly every security expert knew that, at some point, Microsoft would be forced to bite the bullet and take a big compatibility hit in order to solidify operating system soft spots—many of which are due to legacy code support. Plus, the XP SP2 changes will force developers to produce more secure applications and not just take advantage of a permissive Windows OS to write code that doesn’t pay attention to security.
Of course, I would never recommend that anyone widely deploy such a major upgrade the day it hits the street. You should install SP2 on a testing network (or at least a single testing system) as soon as possible, and begin compatibility testing for your specific applications.
Those of you who have the budgetary luxury of being able to conduct even more extensive testing and want to get a leg up on evaluating XP SP2 even before final release should check out the Technical Preview Program, which makes SP2 RC1 generally available for testing by IT professionals (not just those on the beta list). The initial download, which doesn’t include any support other than some Microsoft-sponsored newsgroups, requires Windows XP to be installed already. English and German versions of the update are now available and are over 250 MB.
As soon as you feel comfortable that Windows XP SP2 will not cause a significant interruption for users (or you have fixed the issues that would lead to a potential interruption), you should deploy SP2 company-wide. It’s an important upgrade that can only improve the security of your n"
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
- pickles
- new member
- Posts: 4
- Joined: Thu 14 Apr, 2005 12:15 pm
Re: Root of the problem with my Netscape browsing
by Alice » Tue 19 Apr, 2005 10:15 am
I'm still running WinXPsp1 but here are some threads you can look through:
http://sillydog.org/forum/viewtopic.php?t=6711
Win XP SP2 woes
http://sillydog.org/forum/viewtopic.php?t=7393
SP2 Causes Huge Outgoing Email Delay
http://sillydog.org/forum/viewtopic.php?t=6711
Win XP SP2 woes
http://sillydog.org/forum/viewtopic.php?t=7393
SP2 Causes Huge Outgoing Email Delay
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414
Last edited by Alice on Tue 19 Apr, 2005 10:27 am, edited 1 time in total.
-
Alice - Mozilla Champion
- Posts: 1790
- Joined: Sun 21 Jul, 2002 8:57 am
by Fulvio » Tue 19 Apr, 2005 10:26 am
If you are not an IE user, and you have a good Firewall, the SP2 can be a source of many problems. I am using automatic Windows Update with Big Fix, which came with my computer. Big Fix was very slow in suggesting SP2, and definitely for only a few items.
A good friend of mine (the poor thing has dialup) downloaded and installed SP2, and his computer was crippled, and he is not much of a Netscape/Mozilla user. But, you can remove SP2, I believe via System Restore.
I have four minor SP2 updates which are, also, removable.
A good friend of mine (the poor thing has dialup) downloaded and installed SP2, and his computer was crippled, and he is not much of a Netscape/Mozilla user. But, you can remove SP2, I believe via System Restore.
I have four minor SP2 updates which are, also, removable.
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 (ax)
A minority may be right, and a majority is always wrong
~ Henrik Ibsen
WinXP, SP3, 512 MB, SM2.9.1, FF12, TB12.0.1, IE8.0, Google Chrome18, Ghostwall , Avast 7.x, JRE1.7_04. Testing FF13b3
~ Henrik Ibsen
WinXP, SP3, 512 MB, SM2.9.1, FF12, TB12.0.1, IE8.0, Google Chrome18, Ghostwall , Avast 7.x, JRE1.7_04. Testing FF13b3
-
Fulvio - Moderator
- Posts: 11914
- Joined: Wed 19 Jun, 2002 10:08 am
Thank you....Alice and Fulvio
by pickles » Tue 19 Apr, 2005 11:44 am
Sure wish I would have looked into this SP2 before I installed everything. We will check out the sites that you have recommended.
After 5 years of ME....nothing can be worse...absolutely nothing. Though bothersome (slow browsing)....it is better than repeated ME crashes. Towards the end of our old Dell and ME, it would sometime take 20 minutes and 5 or 6 attempts to even get the PC up and the OS loaded.
Thanks again....you Top Silly Dogs.
After 5 years of ME....nothing can be worse...absolutely nothing. Though bothersome (slow browsing)....it is better than repeated ME crashes. Towards the end of our old Dell and ME, it would sometime take 20 minutes and 5 or 6 attempts to even get the PC up and the OS loaded.
Thanks again....you Top Silly Dogs.
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
- pickles
- new member
- Posts: 4
- Joined: Thu 14 Apr, 2005 12:15 pm
7 posts
• Page 1 of 1
Return to Firefox, SeaMonkey and Netscape
Who is online
Registered users: Google [Bot], Yahoo [Bot]
