I'm having a hard time figuring out why my app can't access filestream data, after we enable AG listener.
Background info:
Initial environment:
APP Server
Web Server IIS Windows Server 2012 R2
DB Server
Windows Server 2012 R2
SQL Server N1 (named instance N1\SQL2016 port 1434) with DB (APP_DB) (with filestream data). Filestream I/O enabled, filestream data was available to APP (web application (IIS)) - read write OK
Environment changes:
Add new server Node 2 (N2) installed same SQL Server version as default instance
Create failover cluster CL (N1 + N2)
Implemented Always On (DB replication working)
Problem:
When AG listener is created the filestream data is accessed over the VNN name (equal to Listener name) (\VNN\filestream_share_name) and the app can't access the data over the new path.
When accessing N1 or N2 over file explorer \N1\ we can see the filestream share name, but when accessing the VNN name (\listener) in file explorer we can't see the sql server filestream share name.
I have tried to disable and disable / enable filestream I/O on both SQL Server nodes, to recreate the VNN\filestream share name, but no success.