A new SQL Server 2017 (CU31) was just brought up at our company. It is hosted on a Windows Server 2019 Datacenter on a VM.
For the most part, everything is working fine but there is a weird latency issue in one part of our ERP system that needs to be resolved.
When I select * from sys.servers I see the following name (example): MySQLServer-NEW
We cannot connect to MySQLServer-NEW via SSMS, ODBC, or remote desktop. Only by the "aliases" such as MySQlServerOld or MySQLServer.
Per our Sys Admin MySQlServerOld and MySQLServer are the only valid host names on the VM. Was told that "SQL Server added this" and it won't work with Active Directory or Kerberos authentication.
I'm seeing queries in our monitoring tool that select from the new server name noted in sys.servers though and these are successful.
Example
Select *
From [MySQLServer-NEW].[databaseName].dbo.TableName
Does something need to be renamed in SQL Server? I do not understand how most things are working with a name that isn't really available
Our ERP system requires named pipes and the doc indicates that it should be set first before TCP/IP.
When looking at SQL Server Config Protocols I see SQL Native Client 11 (thought there would be something newer) although Named Pipes is enabled here.
Named Pipes is disabled under MSSQLServer which is what the SQL Server service runs as.
My searches didn't find anything that seemed related. Obviously on my own here and don't know what I'm looking at...