AD-bound servers show fake user homes in share lists

I recently bound a couple of 10.4.8 server to our AD. This is a magic triangle setup, where the OD exists purely for groups and MCX. Since then, when you authenticate to the servers via AFP or SMB with an AD user you get the appropriate list of shares, plus one extra. It appears that the servers are attempting to “patch through” a user’s home directory; for me, the extra share is called MROSENBERG$, corresponding to my username. If I logged into a client Mac with that username, that’s the name the network home would have. The network homes are actually somewhere on big NAS boxes, mountable via SMB from a Mac. The system logs on the servers have tons of entries like these: [code]Mar 19 11:55:43 dcxserv01 automount[28703]: Can't mount REDOUBT.mgmmirage.org:/VHANLEY$ on /private/Network/Servers/REDOUBT.mgmmirage.org/VHANLEY$: Invalid argument (22) Mar 19 11:55:43 dcxserv01 automount[28703]: Attempt to mount /automount/Servers/REDOUBT.mgmmirage.org/VHANLEY$ returned 22 (Invalid argument)[/code] The sequences of entries from the same timestamp is long, and appears to contain these two lines for every AD user who has ever connected with AFP or SMB. Both servers give the entire sequence of errors every few minutes. What’s going on, and how do I stop it?