UAC bug with 5536 and connecting to Mac OSX?

Submitted this bug against a previous seed, but it's still there in
5536 (so I submitted it *again*). Anybody else able to confirm this?


UAC in current Vista seed fails to allow Windows app installer to run
from Mac hard disk

Summary: The last two Vista builds will not allow me to connect from
Vista to an OSX box to run a Windows application installer located on
the OSX box hard disk -- if UAC is on (the default) on the Vista box.
This problem also occurs on client 10.4.x as well as server 10.4.x UAC
must be turned off (which isn't good) to run the Windows app installer.

To reproduce:

Set up clean install 10.4.7 Mac system.
Turn Windows File Sharing on.
Copy Windows application installer to Mac desktop (example: Adobe
Reader 7.0.8 installer)

Set up clean Vista system: NOTE -- must be a build *after* beta 2
Vista system should have User Access Control (UAC) turned on (the
default)

Connect to Mac from Vista machine over the network by typing
\\<hostname>\<account> method

Log into Mac providing Mac account/password

Change to desktop

Double-click on Adobe installer. The following happens:

1) Open File -- Security Warning box (click "run")

2) User Account Control box -- "continue"

3) Cannot Access network resource box -- enter OSX login/password again

EXPECTED RESULT: With Vista Beta 2 (and earlier builds), the Adobe
Reader installer would run.

ACTUAL RESULT: The "Cannot access network resource" box comes up
*again*. And again. And again. And never seems to go away. It is
impossible to run the application installer because this box stops the
progress.

REGRESSION:

1) Is *also* a problem on OSX Server 10.4.7

2) Is *not* a problem if the same Acrobat Reader installer is located
on a Windows Server/Windows XP Desktop machine.

3) If UAC is turned off, only the "Open File -- Security Warning" box
comes up and then the installer runs as expected if hosted on a Mac.

4) The official Vista Beta 2 -- works. "Cannot access network
resource box" comes up once and once credentials are applied, installer
runs. Builds after "beta 2" -- it fails. Clearly, a change was made
to UAC in the later Vista seeds.


NOTE: If it's a *samba* issue, we will need this addressed as it
becomes a "showstopper" issue if Vista users will not be able to run
Windows installer from our OSX Server with UAC on. I do not have the
ability to quickly install one of the later samba builds to test this.