OK...I found out what the problem was. The network admin was granting permissions on the wrong server. Once I got him to set the permissions on the share on the correct server, everything worked great!

In case anyone is wondering, the permissions granted to the SERVICE_ACCOUNT on the target share were:
- Modify
- Read & Execute
- List Folder Contents
- Read
- Write

This is probably...

Are you writing an ASP.Net application with VB.Net on the back-end or are you writing a VB.Net Windows Forms application?

I would recommend a design modification. Assuming you're creating something of an "Issue Tracking" system, I'd create one table to hold the issue details (including an IssueID field) and then a separate table for logging the notes. In the notes table, I'd inclue the IssueID (foreign key), the name of the person adding the note, the date and time that the note is created, and the text of the note.

I have created a Windows service application in C# that utilizes a FileSystemWatch er object to monitor changes to files in a directory specified in a configuration file. This service is being hosted on a Win2K3 server. The folder to be monitored is specified using a UNC path to a named share on a different Win2K3 server. The service is configured to run using a domain account that was created specifically for this service to run under.
...