The only way to fix H202 for us was to remap the end users drive to the server name exactly what was in DNS (FQDN) that is hosting the company files. Creating a different DNS record (CNAME) that doesn't match the server name doesn't work. For example, if the server name is SEA-QB01, you have to map the end users drive exactly like that plus the domain.com (SEA-QB01.domain.com). If you do a CNAME like QB>SEA-QB01 that doesn't work. Even setting up another A record that points to the new server's IP address didn't work. Mapping to IP address didn't work either.
