It's often said that storing images and other large binary objects in a database is inadvisable because it makes the data file much larger and therefore less efficient. That is indeed true but later versions of SQL Server have provided a solution to that issue. If you can enable the FILESTREAM feature of the instance then you can write your application to save the binary data directly to the database, just as you would with any other data, but SQL Server will actually store the data external to the MDF file, keeping it lean and mean.

Alternatively, if you want to keep doing things the way you are, you can create a network share on that machine and then use the UNC path of that share as the root of your file path. That way, any machine on the network will be able to retrieve the file using the same path.

I'd recommend the first option as the better of the two but it may be that you can implement the second option with basically no code changes.