[Help] Windows XP browse function problem

[mhn43]

We have been having a problem with the browse function on Windows XP SP2 workstations.

Scenario 1

• I logged locally into a Windows XP workstation that was previously connected to our AD domain using administrative rights. This ID is included as part of our standard deployment process.
  
• I composed a message using a web mail client (www.mail.yahoo.com).
  
• I attempted to attach files to the e-mail using the Browse function.
  
• I was able to attach the file successfully
  
• I was able to download files using IE (regmon from www.sysinternals.com)
  
• I composed a message in Lotus Notes and attempted to attach a file
  
• I was able to attach the file successfully
  

Scenario 2

• On the same PC, I created a local user called "test" that had full administrative rights
  
• I logged in as test
  
• I composed a message using a web mail client (www.mail.yahoo.com).
  
• I attempted to attach files to the e-mail using the Browse function.
  
• IE crashed
  
• I was not able to download files from IE (regmon from www.sysinternals.com)
  
• I composed a message in Lotus Notes and attempted to attach a file
  
• Notes crashed
  
• Filemon crashed when I tried to save the log file
  

We also tested with hotmail and others and got the same results. We have also seen this problem manifest itself when using Browse to search for the ID file when setting up Lotus Notes.

We have found that this problem does not present on every Windows XP workstation. In some cases, we have been able to create new users locally and did not have a problem creating attachments or browsing. All of the workstations have been patched with the latest MS patches. All systems are running Symantec AntiVirus 9.0.3. All workstations have been built using the same standard build process and all have been attached to the same AD domain with the same system and group policies.

I have not been able to capture filemon logs, since filemon crashes on these workstations whenever I try to create a log on the affected workstations. However, this has presented on 3 out of 5 different workstations (a combination of physical and virtual) that were tested. It did not seem to matter if the physical machines were laptops or desktops.

We have not yet seen this problem on Windows 2000 workstations.

Any thoughts?

Please NOW in Microsoft Windows XP section, use [TAGS] in your topic's title.

See rules.

--Sonic