TCP/IP Node type and network neighbourhood

Hmm. I think there is a lot of merit in what you say.

 

For those interested in how NetBIOS works and how to get it to work at its best, I'd strongly recommend a read of the relevant sections of TCP/IP Fundamentals for Microsoft Windows (see this thread). They are:

• Chapter 11 "“ NetBIOS over TCP/IP p309-330
• Appendix C "“ Computer Browser Service p503-end

I think this again points towards the same two conclusions: Keep a PC on to act as a master browser or maintain LMHOST files.

Note that the book details both how to ensure that use of LMHOSTS files are enabled and how to set up a common LMHOSTS file.

 

Perhaps I'm way off base here, but firewalls seem to have been mentioned only in passing. In my (admittedly limited) experience, the use of the ZoneAlarm free firewall on each of my computers almost requires the use of static, rather than dynamic, IPs on my home LAN.

Both of my computers run XP Pro, and on both the Node Type is "Unknown" (see screenshot).

My desktop computer connects to the LAN and the internet by Ethernet via a D-Link DI-524 wired/wireless router, using a static IP. Using a static IP precludes the use of DHCP, so it shows in the screenshot as not enabled.

Because my laptop needs to connect via either wireless hotspots or Ethernet when I'm traveling, DHCP and Autoconfiguration are enabled in the TCP/IP properties for both NICs, allowing the use of dynamic IPs. At the same time, static IPs are set up on the TCP/IP properties Alternate Configuration tabs for connection to my home LAN (again, because of the ZA firewalls on each computer).

I can't tell you why, but it all seems to work seamlessly.

Re using Network Neighborhood to connect one computer on a LAN to another, I have always used shortcuts, and never have had to resort to Reggie's suggested use of \\computer_name and \\IP_address.

 

Hi Jim

I have a number of shortcuts on my XP for quick views to kids attached w98. All of these shortcuts begin with the path value \\W98\ which is the kids computer name. What do your shortcuts start with?

 

Dennis ...

Good catch! It never occurred to me that the shortcut targets for the two computers were \\computer_name1 and \\computer_name2. What I should have said was that I never have found it necessary to type \\computer_name or \\IP_address into Windows Explorer's Address Bar (which I don't normally use, or even have visible).

 

I'm with you. I have on cmd screens, just to see if it works.

 

The problems with browsing the network via Network Neighbourhood is not universal. Many networks do not have this problem.

My feeling having looked at this problem for a couple of weeks is that you can use this rule of thumb:

The more the network changes each day, the more likely that you will have problems.

So DHCP, turning the router off a lot, and not having a PC running for very long is most likely to lead to problems. A network using static IPs, keeping the router switched on, having a PC on all the time to act as master browser is least likely to have problems.

If you don't have problems, splendid; you don't have to worry about this issue. However, if you do have this problem I'd recommend making sure you keep your router switched on all the time as the first step to trying to deal with the problem. If that doesn't work, you can either try moving to static IPs, keeping a PC on for long periods, or (as mjg1973 suggests) tweaking the master browser settings. Or, if none of those options appeal to you, get used to using the \\computer_name method.

Oh and once again, the "Unknown" node type was a red herring. I no longer think this is a problem. XP defaults to "Broadcast" mode even when showing "Unknown "

 

When I type ipconfig /all into command prompt the display window comes up but disappears so fast that I cannot see it. What can I do to make it stay around so that I can see it?

 

Type command first to bring up the command windows. Then enter ipconfig /all. However, you may want to read the rest of the thread first

 

Thank You Command prompt worked. I have Hybrid and will enter that in the poll .

Windows XP Sp2 - Do not have a network - Single PC user, Connect via Cable Modem

 

Splendid - thank you.

 

jorjab ...

If I read you correctly, you were typing ipconfig /all into the Run window, not into a Command Prompt window. Reggie's suggestion will work, but it opens the old 16-bit command processor from MS-DOS days, which has limited capabilities.

XP sports a much more extensive 32-bit command processor; to access it, type cmd, rather than command. Among other improvements, it supports long filenames and additional command options.

 

Jim,

Thank You.

Initially I had typed ipconfig into the Run window.

After Reggie's suggestion, I did actually use the accessories command prompt and then the ipconfig which brought up the correct one. Did not type "Command" into start run line. Tried using RUN to see the difference between "CMD" and "Command" in Run - interesting to see the difference including the part about the tag length.

We can always learn something new.

Georgia

 

Useful info here: Computer Browser

There's a registry fix about half-way down, but I think it applies after a reboot - otherwise the Browser service has to be stopped as well.

Browser election can cause serious network visibilty problems in a mixed OS network, as 2K/XP will force an election on joining the network. I had this problem with a mixed W95/98SE/2K network some years ago. I had some success with power-up order, but the problem only disappeared when all PCs were upgraded to W2K, with the Browser service enabled only on the server.

 

Georgia ...

We've gotten a bit off the subject of Reggie's original thread, but this might be worth a mention. The Accessories > Command Prompt icon actually runs C:\Windows\System32\cmd.exe, which opens the Command Prompt window. Using the RUN window is just a quick and easy way to open a Command prompt window without going through the hassle of locating the icon.

To make my life easier, I've placed shortcuts for all of the various system tools in a TOOLS folder on my Start menu. That way, I don't have to think about where they are, and they're right at hand.

 

Personally I am not a great fan of NetBEUI. That comes from installing a lot of small business networks and coming across the problems that are inherent to the NetBEUI protocol suite. However, I have to admit on a very small network - 2 or 3 PCs it works OK and is certainly simple. Also NetBEUI is very closely tied into NetBIOS, so when it does work, NetBIOS works well too and therefore so do applications that rely on it like Network Neighbourhood.

The main problem with NetBEUI is that it totally relies on broadcasts. That means when you transfer data via NetBEUI, every computer on the network receives the data and has to processes it (look at each packet and unless they are the target PC, reject each packet). And because it is using a broadcast MAC addresses the Network card cannot block the packets and has to pass them up to the computer.

That means if you pass a 100 Mb file over a NetBEUI network, every computer on the network slows down until the file is transmitted. When you only have a couple of computers that isn't a problem. When you have ten computers on the network it is quite a problem.

The other issue related to broadcasts is that you cannot route NetBEUI so it is no good for connecting between two or more networks. Also because the protocol uses the broadcast MAC address, switches are flooded and act as hubs - in fact, act as slow hubs because they have to receive the packet, read the broadcast MAC, and then decide to send the packet out on all ports (flood). A hub does not need to make that decision and just relays the signal out to all ports.

So if NetBEUI works for you good. However, be aware of its limitations and if you install a network that is larger than 2 or 3 computers, I would recommend using TCP/IP instead.

 

Interesting network you have there Tony. Its good to see people using a variety of systems.