Thanks, face. That seems to have been the issue; however, the fix was not exactly intuitive and may prove problematic in the long term. Since OSX uses SMB as the default sharing protocol (as of Mavericks), I had to jump through some hoops. I had the shares set up as accessible via either AFP or SMB so I could access them from both Windows and Mac systems. Even when I manually connected to the AFP version of the share via the Finder's Connect to Server command or an Apple Script, Alfred would not find the files. I had to completely disable SMB connections on each share in order to get things to work. Since I am using OS X Server on the system with the shares, I used Server.app to modify the settings.
For those interested, the steps are:
Log in to server.app and go to the File Sharing sheet. Select the share and click the edit button. Uncheck SMB. Repeat for all shares. Restart the client Mac just to clear out everything in memory. This may not be absolutely necessary, but since a reboot takes just a few seconds, no big deal.
We'll see what happens when I need to bring my work-issued Windows laptop home. I'm not sure if connecting to AFP will work from Windows 7 -- it used to be next to impossible to connect to AFP from older versions Windows, hence the original dual protocol share. Fortunately, other than the work-issued laptop, I've eliminated PC hardware in my house and switched to running Windows through Parallels VMs for my personal systems. Also, the change seems to have broken all of my iOS connections to the the shares since everything I was using was based on SMB. This last issue, could be a real problem for me.