IExplorer wierdness - help please

PeeluckyDuckee

Diamond Member
Feb 21, 2001
4,464
0
0
OK, this is wierd and beyond my comprehension....

First of all, a brief description about the environment...
Servers are Windows NT 4.0 Servers
Clients are Windows 95 and NT 4.0 Workstation
One domain

I have a client (A) that's having some major performance issues when accessing the intranet website in the domain. When she moves to another workstation, its the same reoccuring problem. It takes here 30+ seconds to open the main intranet site. Another user (B) logged into this user's (A) machine gets the same problem. But when the other user (B) logs back onto her own machine (B), intranet access is fine.

IE will run up to 100% at times, although hd activity is nil. Checked processes running and shows nothing abnormal.

Both workstations are running IE 5.5 with SP6

When I use my admin account and log into user A's machine and replace the problematic IEXPLORE.EXE file with a new one, then access the intranet again, things seem MUCH speedier. From 30+ seconds down to about 8 seconds to open the intranet. And it ain't the intranet server or network that is slow either. Tried changing lan port switch ports too. Intranet access is normal for other users around user A.

After me replacing the IEXPLORE.EXE file, I had her re-logon to her own machine (with in mind that what it did for me will do the same for her - speedy up intranet access). But you know how things never work the way you want to? Well, this is it :( Same thing. Just as slow as before?

Can this be a profile error? An OS and/or application going wonky? Going to search technet and see what comes up too, meanwhile appreciate if anybody has a clue as to what's happening here. Thx.

Plucky
 

GregANDTCH

Golden Member
Dec 10, 2000
1,370
0
76
Maybe it's some file in her profile folder(s).
It might have it's own copy of iexplore.exe under her profile?
:confused:
 

PeeluckyDuckee

Diamond Member
Feb 21, 2001
4,464
0
0
That would not be a possibility I believe, as IE is installed locally on the machine, not under the profile.