Did you know dear friends that when logging onto a Windows 98 system the OS does not care about the case sensitvity of your password, From that 98 system, with your incorreclty enttered (Let's just say you entered it upper case, and it's really lower case) you are able to access a share on Windows 2000 Professional system that an account for you has manually be created on (with the correct lower case password) but you are unable to connect to the Windows 2000 Server accross the WAN or the SQL server it also houses. So the next time your .Net app loads from the file share, but can not authenticate with SQL this might just be why. Who knew?
On that note, to allow that .Net app to run from that file share you might need to make use of the following:
>caspol -machine -addgroup 1 -url file://machinename/sharename/* FullTrust
And now I know.