Shared drive network troubles

May 12, 2006 2:56 PM

Why is it that I cannot see shared drives on other machines on my home network unless I install "NetBEUI Protocol" on each participating machine's network configuration?

My network connection is a generic Sprint DSL modem, which feeds to a Linksys BEFSR81 Ethernet router, which feeds to a Linksys WRT54G router. Some devices are on Ethernet to either router, some devices are on a WiFi connection. Most of my machines are running Windows 2000 SP 4.

The problem is I cannot connect across the network to any shared drives (even though they are shared). Typically what I'll get if I go to Network Neighborhood and look at a stubborn machine is just "Printers" and "Scheduled Tasks"; no drives. And yes, I already have File and Print Sharing included on each network connection.

The only thing that works and allows me to see other drives, map drive letters, and so forth is if I bring up the network connection under Start > Settings > Network > [Connection] > Properties > Install and add NetBEUI Protocol. Only then does everything work correctly. But I know a few years ago my home network didn't require anything like this.

I know NetBEUI has been around forever... I have no idea what it is, whether it's inefficient, redundant, unsecure, or what. I figure I'd better do this the right way and fix the underlying problem.

Is there something in the router configurations that might be causing the machines to not see each other? Or should I just not look a gift horse in the mouth and settle for NetBEUI?

posted by chef_boyardee to computers & internet (10 comments total)

That's what Microsoft's drive-sharing uses so that Windows machines can talk to each other.

It doesn't matter whether it's inefficient, unsecure, etc. What you need to know is that it isn't redundant, and it isn't dispensable.
posted by Steven C. Den Beste at 3:19 PM on May 12, 2006

Based on this page I don't think netbeui is needed for ms drive sharing, drive sharing uses smb, which goes over tcp/ip, though i don't know why it only works when it's turned on in your case...
posted by killyb at 3:29 PM on May 12, 2006

and a bit more info on the need for netbeui and file sharing
posted by killyb at 3:30 PM on May 12, 2006

You should be able to run SMB over TCP.
posted by b1tr0t at 3:31 PM on May 12, 2006

I only have TCP/IP (no NetBEUI) installed on my Windows XP boxes. They have no trouble sharing files between themselves or with OSX (implemented by Samba?).
posted by b1tr0t at 3:33 PM on May 12, 2006

chef, i know this may sound silly...but all machines that are connected have an ip correct...either an internal or wan ip, netbeui is an ipless propotol so if they don't have an ip, then no tcp/ip/ thus only netbeui would be the only thing that works...
posted by killyb at 3:38 PM on May 12, 2006

What we have accomplished here is to make sure the "netbios protocol" is enabled on these PCs. This is what the Windows Networking runs on top of. netbios used to run only over netbeui in the old days, but these days, we run it over TCP/IP. On the XP systems, you can verify that the netbios over TCP/IP is installed and enabled by going to TCP/IP Properties entry in the Network Connection Properties Window, highlight it, and click on Properties, then go to the Advanced button, and then finally, the WINS tab - make sure netbios over TCP/IP is enabled. It should be there by default, but some techies recommend running netbios over netbeui, which makes for a very secure network. via

ill sit on my hards now...sorry to keep jumping in
posted by killyb at 3:46 PM on May 12, 2006

It doesn't matter whether it's inefficient, unsecure, etc. What you need to know is that it isn't redundant, and it isn't dispensable.

This is incorrect. As long as all the machines have NetBIOS configured to use TCP/IP, you can share drives. NetBEUI is a broadcast protocol that was created for use with NetBIOS, but you can use NetBIOS with IP, IPX, whatever.

The problem is I cannot connect across the network to any shared drives (even though they are shared). Typically what I'll get if I go to Network Neighborhood and look at a stubborn machine is just "Printers" and "Scheduled Tasks"; no drives. And yes, I already have File and Print Sharing included on each network connection.

If the traffic is in fact being routed, you will have to allow SMB traffic through the router (TCP/135, UDP/135, TCP/137, UDP/137, UDP/138, TCP/139 for standard SMB or TCP/445 for "direct host" SMB over TCP/IP without using NetBIOS). However, I doubt that's your problem, since NetBEUI is nonroutable by default if I recall correctly.

Instead, I suspect that your NetBIOS settings are simply preventing the advertisement of shares. What happens if you open a command prompt and type the following?

net use \\othermachine\ipc$ * /user:othermachine\somelocaluser

That should all be on one line, and the values for othermachine and somelocaluser will obviously need to be changed, and you'll need to enter that user's password.

I would be very surprised if that doesn't then let you view the shares using this command:

net view \\othermachine

Anyway, in a business environment, nobody uses NetBEUI any more; everyone uses NetBIOS or direct SMB over TCP/IP for their Windows Networking needs. But honestly, it won't hurt anything (except perhaps your sysadmin pride) for you to use NetBEUI on your home network.
posted by me & my monkey at 4:23 PM on May 12, 2006 [1 favorite has favorites]

some techies recommend running netbios over netbeui, which makes for a very secure network

Ugh. This is terrible advice (not blaming you, but "some techies" instead). Using a different protocol means you need two sets of monitoring tools to see what's happening on your network. Using a separate protocol for internal network traffic is the worst form of security through obscurity, and provides so little obscurity anyway - if an internal machine is compromised, NetBIOS commands can easily be used to attack other machines.
posted by me & my monkey at 4:25 PM on May 12, 2006

As above, NETBIOS is needed to broadcast your computer names, and those are needed for sharing to work easily. Do this (rehash of much advice above):

On (let's call it "Computer A"), in your Start menu, right-click on My Computer, then select Properties from the context menu. From the dialog that appears, select Computer Name. Take note of the "full computer name". This is also called the hostname, and it's the answer to me & my monkey's "othermachine" above.
Also take note of the Workgroup name. Close this box.
Now open Control Panel, and open Network Connections. Select the network connection that is most likely labeled "Local Area Connection", and right-click it. Select Properties from the list.
Double click the Internet Protocol line in the window, and click the Advanced button. Select the WINS tab, then set the radio button for Enable NETBIOS over TCP/IP. Click OK, and OK again, to dismiss these dialogs until you're back at Local Area Connection Properties. Remove the NETBEUI protocol, click OK, and if asked, allow the machine to restart.

Now go to Computer B. In the My Computer/Computer Name area above, take note of the computer name, and make sure the workgroup is the same as Computer A's workgroup. Change it if it's not. Then go to the network connection as above, and enable NETBIOS. Dismiss the dialogs.

On either machine, open My Computer and in the address bar, type \\computerA\sharename.

All should be well. Your files should show up as expected.
posted by disclaimer at 7:08 PM on May 12, 2006