Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 371
  • Last Modified:

netbios name resolution is not working

I have very strange issues with my desktop which is part of my domain. Win7 64 bit
DNS resolution is working fine and I can see other machines with either IP or FQDN
While NetBIOS names are not resolved any longer  (was working fine a couple of weeks ago) even though that I have correct WINS server configured. I tried to rebuild my IP stack and flash DNS and arp and still no luck.  Any other desktop works resolves NetBIOS names without problems. I had to place all of my servers to the hosts file to make it to work for a time being. I don’t want to do a major windows reinstall and I tried all basic troubleshooting: rebuild IP stack, flash DNS,  assign static and switch to DCHP etc….tried system restore Any meaningful suggestion from a REALl expert will be appreciated.
0
leop1212
Asked:
leop1212
3 Solutions
 
Neil RussellTechnical Development LeadCommented:
Firstly why do you have WINS configured at all?  You said this computer was part of the domain? AD DNS should do ALL of your name resolution and that should be all you need unless you have some very old legacy systems on your network.

WINS is ONLY included still for backwards compatibility with WINNT.
0
 
Rob HutchinsonDesktop SupportCommented:
make sure NetBIOS is enabled, see printscreen
netbios.jpg
0
 
leop1212Author Commented:
i do have netbios enabled and I do need Netbios working  for few legacy application : quick windows sharing and remote desktops
with comp_name instead of comp_name.mydomain.com as well as \\comp_name instead of \\comp_name.mydomain.com
as i said in my question i use hosts file as a workaround around with the manual entries for few server/desktiop however i'd like to figure out what is wrong with netbios.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
leop1212Author Commented:
I just found the cause of this problem
somehow another DNS server was added to my "append this DNS suffix in this order"  prior to my domain .
"qiesnet.org" that is scary.
0
 
QlemoC++ DeveloperCommented:
Still, WINS should have found it, and DNS should not have worked at all for incomplete names. WINS and DNS are asked at the same time, so whoever knows something about the name answers.

Anyway, having the correct DNS suffixes appended automatically should be all you need.
0
 
Neil RussellTechnical Development LeadCommented:
"quick windows sharing and remote desktops with comp_name instead of comp_name.mydomain.com as well as \\comp_name instead of \\comp_name.mydomain.com"

You dont need WINS for that, just a correctly configured DNS and NIC setting that know about your domain correctly.

If I do \\neilspc\c$ then I get what I expect and I have NO WINS configured at all.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now