If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
When I view "Network Neightborhood" or "My Network Places" under
Windows, a list of computers show up. How can I tell, under the various versions of Windows, which ones are being accessed via NetBUI and which ones are being accessed via TCP/IP? It seems like this ought to be simple (e.g., right-click and select properties - nope, that doesn't tell), but I can't find it. Also (this might be harder) how can I list the other computers which can see (or have viewed) shares from the current computer, and how they're seeing them (NetBUI v. TCP/IP)? Thanks, -Dave |
#2
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
Hi.
Look at this page it written for another issue but it will show you how to find and use protocol availability and binding: http://www.ezlan.net/netbeui.html] Jack (MVP-Networking). "Dave Burton" wrote in message m... When I view "Network Neightborhood" or "My Network Places" under Windows, a list of computers show up. How can I tell, under the various versions of Windows, which ones are being accessed via NetBUI and which ones are being accessed via TCP/IP? It seems like this ought to be simple (e.g., right-click and select properties - nope, that doesn't tell), but I can't find it. Also (this might be harder) how can I list the other computers which can see (or have viewed) shares from the current computer, and how they're seeing them (NetBUI v. TCP/IP)? Thanks, -Dave |
#3
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
Thanks, Jack, that's a nice web page about how to enable NetBEUI
on a Win-XP box, but that's not what I'm looking for. I want to know how to tell which protocol is actually being used for each of the other computers whose shares I can see in Network Neighborhood. "Jack" JackMDS at veriz0n.net wrote in message ... Hi. Look at this page it written for another issue but it will show you how to find and use protocol availability and binding: http://www.ezlan.net/netbeui.html] Jack (MVP-Networking). "Dave Burton" wrote in message m... When I view "Network Neightborhood" or "My Network Places" under Windows, a list of computers show up. How can I tell, under the various versions of Windows, which ones are being accessed via NetBUI and which ones are being accessed via TCP/IP? It seems like this ought to be simple (e.g., right-click and select properties - nope, that doesn't tell), but I can't find it. Also (this might be harder) how can I list the other computers which can see (or have viewed) shares from the current computer, and how they're seeing them (NetBUI v. TCP/IP)? Thanks, -Dave |
#4
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
There is no easy way. A computer that is configured for multiple protocols will
attempt to connect to the remote computer with it's default protocol. For instance if a computer has netbeui configured as it's default protocol for Client for Microsoft Networks, it will attempt to access the remote computer with netbeui for share access and if the remote computer is configured to use netbeui for file and print sharing then the connection would use netbeui. You can use netstat -an to see what your current tcp/ip connections are and connections to port 139/445 TCP could be for network shares. A software firewall. such as Sygate, can be used to log connections on ports 139/445 and the firewall function itself can be disabled. That way you would at least know who is accessing shares on tcp/ip. A packet sniffer, such as Ethereal can also be very useful in examining network traffic between computers and has highly configurable capture filters. --- Steve "Dave Burton" wrote in message m... When I view "Network Neightborhood" or "My Network Places" under Windows, a list of computers show up. How can I tell, under the various versions of Windows, which ones are being accessed via NetBUI and which ones are being accessed via TCP/IP? It seems like this ought to be simple (e.g., right-click and select properties - nope, that doesn't tell), but I can't find it. Also (this might be harder) how can I list the other computers which can see (or have viewed) shares from the current computer, and how they're seeing them (NetBUI v. TCP/IP)? Thanks, -Dave |
#5
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
Why not just make life simple - and get rid of NetBEUI?
-- Noel Paton (MS-MVP 2002-2004, Win9x) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Dave Burton" wrote in message m... When I view "Network Neightborhood" or "My Network Places" under Windows, a list of computers show up. How can I tell, under the various versions of Windows, which ones are being accessed via NetBUI and which ones are being accessed via TCP/IP? It seems like this ought to be simple (e.g., right-click and select properties - nope, that doesn't tell), but I can't find it. Also (this might be harder) how can I list the other computers which can see (or have viewed) shares from the current computer, and how they're seeing them (NetBUI v. TCP/IP)? Thanks, -Dave |
#6
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
Noel Paton wrote:
Why not just make life simple - and get rid of NetBEUI? Geez, if I wanted to make my life simple(and didn't need internet access) NetBEUI would be the ticket. Perhaps you can explain why Microsoft doesn't support it any more. It would be an ideal second protocol for home users, if they wanted to access the internet and also use a second protocol for file and printer sharing. Dick Kistler |
#7
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
http://support.microsoft.com/?kbid=306059
-- Noel Paton (MS-MVP 2002-2004, Win9x) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Dick Kistler" wrote in message ... Noel Paton wrote: Why not just make life simple - and get rid of NetBEUI? Geez, if I wanted to make my life simple(and didn't need internet access) NetBEUI would be the ticket. Perhaps you can explain why Microsoft doesn't support it any more. It would be an ideal second protocol for home users, if they wanted to access the internet and also use a second protocol for file and printer sharing. Dick Kistler |
#8
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
"Noel Paton" wrote in message ... http://support.microsoft.com/?kbid=306059 -- No reasons for discontinuing support there. Yes, it's old. Yes it is used by all those old network clients, so what? Yes it uses the OSI LLC2 protocol and is not routable. Not being routable may be an advantage. I understand that you can still use it. I still use it. I would just like to have a believable explanation of why Microsoft has dropped support for it. Dick |
#9
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
Draw your own conclusions why this is a problem and if any pattern emerges.
Because netbeui is easy for the home user to configure. Because one can deny sharing to TCP/IP if netbeui is used for the home network. Because the XP firewall wasn't designed to protect from netbios attacks. Because it prevents snooping on your home network by "trusted" applications and programs accessing the internet via exclusively TCP/IP. Because the zombies educated by MS were programmed to respond with violent and irrational responses when the phrase "netbeui" was uttered or written as you may have seen so far. Shall I go on? "Dick Kistler" wrote in message ... "Noel Paton" wrote in message ... http://support.microsoft.com/?kbid=306059 -- No reasons for discontinuing support there. Yes, it's old. Yes it is used by all those old network clients, so what? Yes it uses the OSI LLC2 protocol and is not routable. Not being routable may be an advantage. I understand that you can still use it. I still use it. I would just like to have a believable explanation of why Microsoft has dropped support for it. Dick |
#10
|
|||
|
|||
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
"Lil' Dave" wrote in message ... Draw your own conclusions why this is a problem and if any pattern emerges. Because netbeui is easy for the home user to configure. Because one can deny sharing to TCP/IP if netbeui is used for the home network. Because the XP firewall wasn't designed to protect from netbios attacks. Because it prevents snooping on your home network by "trusted" applications and programs accessing the internet via exclusively TCP/IP. Because the zombies educated by MS were programmed to respond with violent and irrational responses when the phrase "netbeui" was uttered or written as you may have seen so far. Shall I go on? Ok, sounds logical to me. Pretty much what I thought. Same guys that worked on Windows PE. Dick Kistler |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using | Dave Burton | Networking | 26 | August 8th 04 07:22 AM |
networking | Sam Gilmore | Networking | 2 | July 5th 04 09:59 AM |
Intermittent Network Neighborhood problems | Pete K | Networking | 2 | July 3rd 04 08:57 AM |
home networking - ICS problem | Bruce | Networking | 7 | July 1st 04 09:38 PM |
BLA indicates 23 second delay for TCP/IP network | BoB | General | 11 | June 28th 04 09:47 PM |