T
Thomas B Stephenson
Well I have been reading every post I can find on this subject for weeks.
Yet, I have found no solution to the following:
Using IE6 on Windows XP SP2 NIS 2005.
At the MSN sight (Whether home page or not) I receive "Object Moved" blah
blah blah click here message on an otherwise white screen. If I click
"here" it does not go to the clicked link but to the last link actually
viewed. If I click back and hit the link again, no problem. If at the
Object Moved page I hit refresh, no problem.
This situation occurs on almost all links. I can assure you I have no
spyware programs running and all Windows security patches etc. are
installed.
Two other observations: First, the Object Moved problem disappears if I
disable NIS? Second, no problems going to MSN or MYMSN via Firefox even
with NIS active. For what its worth, I can find nothing at the Symantec
website on this issue.
I know I'm not the only one with this problem, based on other posts here and
elsewhere. Can't believe Microsoft/Symantec are totally oblivous to the
situation. I did contact both MSFT and Symantec but neither has chosen to
yet respond.
I would appreciate any comments.
Yet, I have found no solution to the following:
Using IE6 on Windows XP SP2 NIS 2005.
At the MSN sight (Whether home page or not) I receive "Object Moved" blah
blah blah click here message on an otherwise white screen. If I click
"here" it does not go to the clicked link but to the last link actually
viewed. If I click back and hit the link again, no problem. If at the
Object Moved page I hit refresh, no problem.
This situation occurs on almost all links. I can assure you I have no
spyware programs running and all Windows security patches etc. are
installed.
Two other observations: First, the Object Moved problem disappears if I
disable NIS? Second, no problems going to MSN or MYMSN via Firefox even
with NIS active. For what its worth, I can find nothing at the Symantec
website on this issue.
I know I'm not the only one with this problem, based on other posts here and
elsewhere. Can't believe Microsoft/Symantec are totally oblivous to the
situation. I did contact both MSFT and Symantec but neither has chosen to
yet respond.
I would appreciate any comments.