I recently completed an in-place upgrade from Server 2012 R2 to Server 2016 on a file server.
This file server serves SMB shares that are accessed both locally (via drive maps from session host servers on the same domain serving virtual desktops) and remotely (via drive maps from remote machines connected via VPN but NOT on the domain).
Since the upgrade, the machines which are not on the domain and which accessed the shares via from a remote location can no longer do so.
I have several other servers which I can browse to and map drives to from the remote location via the VPN, but not this upgraded file server.
I've been trying to resolve this for a while now and here are the main things I've noted...
- I can still ping the machine from the remote location.
- I can still browse to and map drives to the file server locally from my session host servers (within the domain)
- I cannot browse in file explorer to the file server in question remotely.
- I cannot map drives to the file server remotely.
- I can browse to and map drives to other 'non-upgraded' (ie cleanly installed) Server 2016 machines from the remote location.
Windows firewall is not enabled on any of these machines.
Has anyone got any suggestions as to what may cause this issue or on how I can resolve this?
Thanks in advance!