Can't map via hostname

  • 49 Views
  • Last Post 16 February 2017
daemonr00t posted this 08 February 2017

Hi there,   So I got this scenario with a handful of Hyper-V based Server 2012R2 Domain Controllers spread in a couple of sites with good a good connection between them. All involved systems are updated, directory is fully convergent. Now randomly we can’t map shared resources (like the SYSVOL) via hostname and/or FQDN but things work flawlessly with the IP address. Name resolution is ok, firewall was disabled (still rules were in place) and AV exceptions are there too. I found a thread with a similar case, where Microsoft after a while provided a private test fix but that was on 2K8R2… Anyone out there with something to share about this?   ~danny CS
Sent from Mail for Windows 10  

Order By: Standard | Newest | Votes
darren posted this 08 February 2017

Danny-

One possibility—is the TCP/IP NetBIOS Helper service running? I’ve seen this kind of behavior when it was off/disabled.

 

Darren

 

show

daemonr00t posted this 10 February 2017

Thanks for the tip Darren.

The TCP/IP NetBIOS Helpser service was indeed running but I’ll keep this in mind for any future cases.

There was a push as someone had this hunch that one of the DCs was faulty so we end up removing it and guess what… the issue continues.

Now the networking guys have found some “RESET packets” and they are digging into that…

If anything AD related comes up I’ll share it but as I said several days ago this seems to be network related.

 

~danny CS


Sent from Mail for Windows 10

 

show

Atula posted this 16 February 2017

please try https://answers.microsoft.com/en-us/insider/forum/insiderwintp-insiderfiles/unable-to-map-network-drives/a3c1e4a0-8b93-4c6c-be6d-b8ac4533b7ad
-Atul


show

daemonr00t posted this 16 February 2017

Thanks for checking Atul.


After exhaustive sessions with the ISP it turns out it was something on their side ;)


Cheers,







~dannyCS


Sent from my mobile

show

Close