Question Locked

Unable to ping NetBIOS name, but able to ping FQDN

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi, I have been able to ping the FQDN of a domain (abc.local), but can not ping the NetBIOS name (abc).

I checked WINS and "ABC" domain has the 4 entries needed and flushed the cache using nbtstat -R. Does anyone have any other suggestions of where I could check?

The reason for this is I need My Network Places to see the remote domain. BTW... the computer I am checking from is the DNS/WINS/DC for a Windows 2003 domain and the remote domain is in a DMZ/another subnet.

11 replies

by ic-it

The FQDN of the computer would be something like this;
computername.abc-domain.abc.local

If abc-domain is the domain under abc.local

by sgt_shultz

ping is broadcast so if use tracert (because routers won't pass broadcast traffic)

by puntahacharts

Sgt Schultz... I hope that you are a Marine because I could not live with myself if an Army SGT gave me advice J/K... Semper Fi!!!

I shouldn't need the LMHOST entry because I am using WINS and DNS. WINS has the 4 entries needed for resolution: Domain Master Browser, Workgroup, Domain Controller, and Normal Group Name.

In regards to the previous post, I am trying to ping the domain name, not specific hosts. Thats the funny thing, I can ping any host(i.e. host or host.abc.com), but I can NOT ping the NetBIOS domain name(i.e. abc); although, I can ping the DNS name (i.e. abc.com).

To specify, I need to Backup Exec to see the other domain, which is similar to seeing them in My Network Places. Again, I can ping and get to computers in the other domain fine, it is just that they are not populated in My Network Places.

Please help....

by ic-it

On the server that is not listed, type this at a command prompt.
NET CONFIG SERVER /HIDDEN:NO

Other than that I wonder if it may be a Trust relationship issue.

by andrewb314

Did you ever get it figured out? I *know* it should work, because it worked fine at my last job. Unfortunately, it wasn't me who set that network up.

by puntahacharts

Basically, I did a thorough inventory of the network and found 1 computer that was in a workgroup with the same name as the domain I was trying to access. I disabled NetBIOS from that 1 machine and the other domain came up right away.

I don't know, but it seems that in larger networks, WINS gets confused when workgroups and domains share the same name and won't properly answer client requests.

by andrewb314

The issue was that the netbios name was different than the domain name, and there was no DNS entry for it.

ad.corp.com was the domain name.
corpad was the netbios name.

I could ping "ad" because adpromo added that to DNS. I couldn't ping "corpad" until I also added that as a CNAME for "ad".

Still not clear why the WINS forwarding wouldn't work though.

by mail4yogeh4

I believe you can ping the netbios only in case of a single label domain. In your last company where it worked what was the name of the domain. Was it a fully qualified name like abc.com or a single lable name like abc.

by lnevers

go to the DNS tab, check the "append these DNS suffixes (in order): and then add your FQD suffix (i.e. yourdomain.com)

I was having this same issue. Couldn't ping a remote server by short netbios name but could by FQDN. Added the FQD suffix and could then ping the short name.

This discussion is closed to new replies.