Windows 10: SMB shares accessible via IP but not by hostname works at reboot but shortly after it does not

I'm assuming one of the recent updates broke this but for some reason...


SMB shares are only accessible via internal network IP...eg...


\\192.168.1.50\<share name>


when it should be...


\\<server hostname>\<share name>



I do not have this issue outside of this machine. What could be causing this?

:)

 

SMB-Share not found

Hello together,

i have a problem and i'm troubleshooting since 15 hours.

I installed a new Windows Server 2016 (nano without GUI), added it to my domain, assigned my default GPO also applied on all my other servers, installed the fileserver with work-folders and deduplication.

Now i cannot access the SMB-Shares, neither the default admin shares, nor a newly created smb-share on a different drive for testing. I always receive the message "The network path was not found" (Error Code: 0x80070035)

Event-Viewer shows the event 30803 in the SMBClient:

Failed to establish a network connection.

Error: {Device Timeout}

The specified I/O operation on %hs was not completed before the time-out period expired.

Server name: SERVERNAME

Server address: 192.168.101.24:445

Connection type: Wsk

Guidance:

This indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks TCP port 445, or TCP port 5445 when using an iWARP RDMA adapter, can also cause this issue.

The client tries to access is also Windows Server 2016 or Windows 10, both doesn't work.

Already checked Windows Update, disabled SMBv1, disabled SMBv2 and changed back to SMBv1, opened SMB-Firewall Ports recommended by Microsoft (also tried disable the Firewall, without success)

Permissions are also okay, access won't work with \\Servername\share, \\IP-Address\share, \\servername.domain\share

I can access from the File-Server other SMB-shares without problems, also can open the local shares with IP-Address or Servername

Also checked the Get-SMBServerConfiguration and changed settings similar to my other servers

 

problem accessing smb shares from windows 10

With network discovery on, my ubuntu machine is found (named kodi).

If I check on kodi in the network section of file explorer, it shows my shares.

If I doubleclick on one of the shares, a slow green line crosses the top of the screen and eventually gives the 0x800704cf

If I dont touch this popup, then I can access the share normally.

If I cancel or diagnose (which finds nothing) it is not available.

However if I enter \\ip-address at the top of file explorer it finds the shares and they are immediately accessible.

Also if I turn network discovery off, and type \\kodi at the top of file explorer, it works just like using the IP address

I figure this has something to do with dns, but cannot get network discovery to work properly

Does anyone have any ideas on this? Its only been an issue since the upgrade to windows 10.

Method 1: Run the Network Adapter troubleshooter and check if it helps.

Follow the below steps:

• Type troubleshooting in the search bar.
• Select Troubleshooting.
• Select View all on the top left corner.
• Click on Network Adapter.
• Follow the on-screen instructions to run the troubleshooter.

The issue persists following method 1.

Method 2: Update driver manually.

I suggest you to update the Graphic driver from the Device Manager and check if it works.

Follow the below steps:

• Right click on Start button and click on Device Manager.
• Extend Network adapters driver from the list.
• Right click on the Network driver and click on Update driver Software.

Method 2 shows that the driver is up to date.

 

Hosts File Alias not working with File Share


I can set an alias in the hosts file on a win7 machine and access it just fine but doing the same in Win10 prompts for creds that never work even when entered correctly.
What did win10 change?

hosts file entry:
127.0.0.1 hostname alias

\\ip - works fine
\\hostname -works fine
\\alias - Prompts for creds and creds don't work

I have gone to the extent of fully disabling UAC from reg, same outcome. Network and file sharing is set to password access and not homegroup. Simple file sharing is off.

Something to note. I always disable ipv6 form the adapter but when I ping my hostname it shows the ipv6 loopback. Why is that?
When I ping the alias it returns 127.0.0.1 ipv4 loopback that was entered in the hostname.

Any suggestions are greatly appreciated.
Thanks