SP2, TrendMicro OfficeScan, NET USE issue

[Brian Steele]

Execution of the following cmd file will cause my WinXP
SP2 PCs to immediately crash and restart:

:Start
NET USE (driveletter): \\(server)\(share)
NET USE (driveletter): \\(server)\(share)
:Finish

Where
"driveletter" = any available drive letter
"server" = any available server
"share" = any available share

---
Yes, the cmd file is trying to run the NET USE command
twice!! This is evidently what triggers the crash - when
the PC is trying to map a drive that's already mapped.



Brian Steele

 

[Warren]

I just tried this twice and I do not repro. I map the drives with out error.
What happens if you disable your AV as a test?

 

[Guest]

If the the AV disabled, the PC does not crash.

Unfortunately, disabling the AV on the PC in a networked
environment like ours is simply not an option.

It's a bit interesting though that's it's now possible to
crash WinXP by doing something as simple as this. I
expected better "crash-resistant" behaviour from WinXP
after the SP2 upgrade.


Brian Steele

-----Original Message-----
I just tried this twice and I do not repro. I map the drives with out error.
What happens if you disable your AV as a test?

--
Warren [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights

Execution of the following cmd file will cause my WinXP
SP2 PCs to immediately crash and restart:

:Start
NET USE (driveletter): \\(server)\(share)
NET USE (driveletter): \\(server)\(share)
:Finish

Where
"driveletter" = any available drive letter
"server" = any available server
"share" = any available share

---
Yes, the cmd file is trying to run the NET USE command
twice!! This is evidently what triggers the crash - when
the PC is trying to map a drive that's already mapped.



Brian Steele

.

 

[FoyThompson]

We are experiancing the same issue with Trend OfficeScan. It occurs wit
both officescan ver 5.5 and 6.5. The BSOD only happens if you are usin
"net use" to map a share to a letter that is already in use. If yo
delete the mapping first "Net use driverletter: /delete" the crash doe
not happen. I have an open ticket with Trend on this but have no
received a fix yet.

One other note. I have been able to build a brand new XP system
upgrade to SP2 and install Trend. On the fresh build the crash doesn
occur. The downside is there is no way we are rebuilding everyone
systems just to upgrade to SP2


-
FoyThompso

 

[FoyThompson]

I forgot to mention I have also been able to cause the BSOD using VB
scripts which do not explicitly call "net use" for drive mapping. I
will crash the system if the drive letter is already mapped also.

*We are experiancing the same issue with Trend OfficeScan. It occur
with both officescan ver 5.5 and 6.5. The BSOD only happens if yo
are using "net use" to map a share to a letter that is already i
use. If you delete the mapping first "Net use driverletter: /delete
the crash does not happen. I have an open ticket with Trend on thi
but have not received a fix yet.

One other note. I have been able to build a brand new XP system
upgrade to SP2 and install Trend. On the fresh build the crash doesn
occur. The downside is there is no way we are rebuilding everyone
systems just to upgrade to SP2!

-
FoyThompso

 

[Guest]

Very interesting. I'm having the same problem. I sent a request to Trend
also. Great trouble shooting! Have you tried manualy mapping a drive?

 

[Guest]

The problem also occurs when using a network home folder in the user account
profile. Strange.