Discover computers on network with NetBIOS and NOT WSD.. how?
I have a peer-to-peer network that's been working fine. We are adding/changing some user profiles to Standard Users and want the network to be stable during that process.
I notice that most computers are Discovered via NetBIOS. But a few are Discovered via WSD.
I would just as soon have them ALL be Discovered by NetBIOS.
All of the things I find talk to going in the other direction.
So, how can this be done?
Turning off network discovery isn't a likely option.
I notice that most computers are Discovered via NetBIOS. But a few are Discovered via WSD.
I would just as soon have them ALL be Discovered by NetBIOS.
All of the things I find talk to going in the other direction.
So, how can this be done?
Turning off network discovery isn't a likely option.
Last Comment
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Also, I do not even use Web Services Discovery in my normal work with computers and NetBIOS is now getting old.
So I am not even sure of your objective.
So I am not even sure of your objective.
ASKER
My original post says:
I expect to use IPV4 for some time. That said, what is the alternative for peer-to-peer network name service in an IPV6 context?
I notice that most computers are Discovered via NetBIOS. But a few are Discovered via WSD.Is "I would just as soon" not state an objective?
I would just as soon have them ALL be Discovered by NetBIOS.
I expect to use IPV4 for some time. That said, what is the alternative for peer-to-peer network name service in an IPV6 context?
I expect to use IPV4 for some time.Then you will have to turn off IPV6 on newer computers and do without the services that depend on it. I don't know what the alternative is at the moment.
I have not ever seen a computer discovered with WSD - only printers. And NETBIOS is not even listed on my computer.
Most computers today work with and are discovered with TCP/IP.
So I remain at a loss .
Most computers today work with and are discovered with TCP/IP.
So I remain at a loss .
ASKER
Well, this isn't something that I'd noticed before either. But I found that the network list has a column called Discovery Method. Here is an example that prompted my question:
and here's another:
Note that TCP/IP isn't on the list of methods in either case. So, I rather doubt that TCP/IP is a "discovery method" in this context at all.
Perhaps this is all normal and not a cause for concern. But I am very curious as to how these discovery methods come about and might be controlled.
and here's another:
Note that TCP/IP isn't on the list of methods in either case. So, I rather doubt that TCP/IP is a "discovery method" in this context at all.Perhaps this is all normal and not a cause for concern. But I am very curious as to how these discovery methods come about and might be controlled.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I see the same thing as you now that I am at a client. Any new machines (like my own Windows 10 machine) show up as WSD and some others (less than half) show up as NETBIOS.
It does not make any difference; there is nothing wrong; and eventually NETBIOS will disappear.
So you just need to allow the discovery method each machine reports and do not try to force it all one way.
It does not make any difference; there is nothing wrong; and eventually NETBIOS will disappear.
So you just need to allow the discovery method each machine reports and do not try to force it all one way.
ASKER
To follow up on an earlier comment:
what is the alternative for peer-to-peer network name service in an IPV6 context?
what is the alternative for peer-to-peer network name service in an IPV6 context?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Also it does not matter peer-to-peer or domain. The machines are going to give you what they have and use. You just have to adapt. Things are moving and changing.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Looks like NETBIOS is "API" driven too e.g.
- netbios-ssn (port 137/139): NetBIOS normally runs over TCP/IP via the NetBIOS over TCP/IP (NBT) protocol
- microsoft-ds (port 445): NetBIOS is completely independent from SMB. It is an API that SMB, and other technologies can use, so NetBIOS has no dependency to SMB.
Moving forward, tis becomes the WSD is the next generation of Simplified Services Discovery Protocol (SSDP) and Universal Plug and Play (UPnP), but with added security. With port shared - TCP 5357 - WSDAPIEvents, TCP 5358 - WSDEvents Secure and UPD 3702 - WSD publishing
- netbios-ssn (port 137/139): NetBIOS normally runs over TCP/IP via the NetBIOS over TCP/IP (NBT) protocol
- microsoft-ds (port 445): NetBIOS is completely independent from SMB. It is an API that SMB, and other technologies can use, so NetBIOS has no dependency to SMB.
Moving forward, tis becomes the WSD is the next generation of Simplified Services Discovery Protocol (SSDP) and Universal Plug and Play (UPnP), but with added security. With port shared - TCP 5357 - WSDAPIEvents, TCP 5358 - WSDEvents Secure and UPD 3702 - WSD publishing
ASKER
I would expect a domain to have active directory and get name service using AD.
How does that relate to this very useful discussion?
How does that relate to this very useful discussion?
It does not matter Domain or Workgroup. WDS is new and NETBIOS is old and going out. That's all.
ASKER
Thanks for the insights into the details of the technology!
You're welcome. It was a bit confusing going thru all the options or versions that Microsoft has provided over the last 15 years.
Windows Networking
The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.
51K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER
I would like all of the computers to show as discovered by NetBIOS and not the other way around.
The question is how to assure this and not how to block it.
Maybe I misunderstand the answer?