Machine can only ping by IP, not by name.

[mxnerd]

Can anyone tell me what's wrong?

 

[aigomorla]

this one windows 10?

because i had a simular problem and this seemed to fix it..

1/ run cmd as admin
2/ sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
3/ sc.exe config mrxsmb20 start= disabled
Restart and you are done!

 

[mxnerd]

this one windows 10?

because i had a simular problem and this seemed to fix it..

1/ run cmd as admin
2/ sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
3/ sc.exe config mrxsmb20 start= disabled
Restart and you are done!

I just found that I can ping from Windows 10 to Windows 10 using just machine name.

But Server 2012 (workgroup mode) needs to use full qualified name to ping Windows 10 machine. Weird.

Will research / try your advice later.

 

[mxnerd]

Search the net and found these commands will disable SMB 2.0 & 3.0. Microsoft strongly recommends user not doing it.

I did it anyway just for testing. Issued the commands, reboot, it does not help. This server still needs to use full qualified domain name to ping or reach the machine.

The weird thing about this is every other machine on the net had no problem pinging this machine using just simple machine name, be it another Server 2012, Win10, Win7, Server 2008, or even Linux Mint machine.

Anyone has explanation?

 

[razel]

If it is part of a domain or a group you can try the fully qualified name.

 

[XavierMace]

Is the option to append the DNS suffix checked in the IP Config > Advanced DNS settings on the server?

 

[Elixer]

Do IPCONFIG /ALL on the machine in question, and look at the node type, does it show peer-peer?
If so, that is the problem. (assuming you are NOT running wins server)

You can also edit your hosts file to have the correct lookup if you want to go that route, assuming static IPs on the LAN.

 

[mxnerd]

All of the node types are hybrid.

Well, I can always use full qualified domain names.

 

[mv2devnull]

I just found that I can ping from Windows 10 to Windows 10 using just machine name.

But Server 2012 (workgroup mode) needs to use full qualified name to ping Windows 10 machine. Weird.

The nslookup sends a query to the DNS server. Therefore, it tells what the server will answer.

The ping, however, depends on the name resolution on the localhost. I know nothing about Windows name resolver. In Linux the resolver configuration has essentially two items:
* search -- a list of domainnames
* server -- IP of DNS server
For example:

search eng.bar bar gaz
nameserver 8.8.8.8

If I do "ping foo", the resolver would make up to 4 queries to 8.8.8.8:
foo.eng.bar
foo.bar
foo.eng
foo

The first successful query result will be used by the ping.

There is more though, the NSS config has "hosts: files dns"
which means that contents of /etc/hosts is checked before querying 8.8.8.8

The resolver config could be manual/static (just like the content of /etc/hosts is), but is usually created by DHCP. A dhcp client can selectively ignore data though.


The Windows has equivalent of NSS; it can use multiple name services (files, WINS, DNS, etc). The order matters and it can be changed.

I do presume that both the Win 10 and 2012 do receive same options from the DHCP. The question is do they use them and do they use other, higher priority disturbing name services.