Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Under windows the mechanism that allows hosts to resolve each others names when typed in, is different from the machanism used to collect all the system names into a list and distribute it, know as the Windows Browser. The windows browser can take up to 45 minutes to register a new host, or notice that its gone. It also behaves strangley when there is a clash of Master Browsers. In short, its crap, ignore anything the browser shows you unitl you have tested from the command line.
Mapping drives is good, but there are other things which could make this fail. The best commands to use to test that Netbios hosts can all see each other is nmblookup on Linux and the windows equivalent nbtstat. nbtstat -A <IP ADDRESS> will tell you if the host is listening on the netbios ports, nbtstat -a <hostname> will show that the hosts are resolving. You can then use smbclient -L <host> and net view \\host which will show you available shares on hosts.
Only once this lot is doing what it should should you take any notice of the browser.
Having said all that, if the XP hosts are configured to use the WINS server, the horrible windows browser system is bypassed and the browse window should show you only what the WINS server knows about.