Extended error - Can't connect using hostname to a 2003 Server

Nathan Pinotti 0 Reputation points

Hi All My scenario: Domain 2012 R2 Functional Level Win2012 R2, 2019 as DCs 2012R2, 2019 and 2003 as member server Legacy Application running on 2003 server (No, it's not possible to upgrade it to a newer version) From a Windows 10 device If I'm able to connect to a share folder on 2003 Server using \IP but can't connect using \hostname. The weird part is that...if my device/user is using a DC 2012 R2 as LogonServer, the connection works. If it uses a DC 2019 the connection fails with a generic error: An extended error ocurred What I already checked/changed with no success:

  • Name resolution is working fine. I can ping hostnameW2k3 and get the correct IP address
  • SMBv1 is enabled
  • Reverse DNS zone is Ok
  • ping -a is also working fine
  • regedit lsa\lmcompatibilitylevel = 3 (on workstation and DCs)
  • Eventvwr does not state anything that could help (checking on SMBClient logs) Any suggestion is appreciated
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,410 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 44,046 Reputation points

    Hello there, Have you made any recent updates? There are reports that November update have caused this issue. If you can only access the system by IP and not name, this is a DNS issue. What DNS are your clients using and is the 2003 machine domain joined or at a minimum have a DNS record in your AD? Instead of ping computer, try ping -a IPofMachine, does it return the same name, if not your rDNS is missing/wrong. That said, I'm sure you're aware 2003 has been long since out of support, so being able to get to it by IP or FQDN should still be an option. Hope this resolves your Query !! --If the reply is helpful, please Upvote and Accept it as an answer--