I DID enable in in the TCP/IP Advanced WINS tab under my ethernet adapter's properties. It remains enabled in that menu. However, when I run ipconfig /all in the command prompt it tells me that it is disabled. I even went into the registry and found the value that controls this, as specified here:

http://technet2.microsoft.com/WindowsServer/f/?en/library/40c09844-a669-463c-94dc-7ccf7214083d1033.mspx

All the keys for all network adapters were set to 1, except one that was set to 0. Still, I changed the 0 to a 1. It made no difference, ipconfig still showed NetBIOS over TCP/IP as disabled. And I still cannot access the other computers on my network, though I can ping them.

Thanks in advance

where in ipconfig /all does it talk about netbios????

what does nbtstat -n say?

Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

Here is a screenshot of my command prompt when I type iponfig /all:

http://i1.tinypic.com/2lcv47d.jpg

nbtstat -n simply says "Failed to access NetBT driver - NetBT may not be loaded."

I have found two websites that directly address my problem, but niether offer a working solution:

1. http://www.techspot.com/vb/all/wind...
2. http://www.chicagotech.net/netbios&...

any further help would be appreciated

1) Is there another part to this thread around here somewhere? The first post reads like a response to someone else's response to an original post.

2) To talk to other clients on your LAN you have to:

- have the same Workgroup name for all clients. Capitalization counts.

- enable File sharing on each client you want to talk to

- Set up a user account for each person you want to have access to that shared resource

- Enable Sharing for the resource (file, folder, drive, printer)

- in each Share explicitly allow that user account (or any group that user account is registered to) access.

You also have to configure software firewalls, if any, to know they're on a LAN client and it's OK to accept connections from other clients.

NETBIOS isn't routable so unless you're Sharing a printer you don't really need NETBIOS bound over TCP/IP (NETBT) on your LAN. However if you do, one common error is to have a 2nd networking protocol installed (IPX/SPX usually), have NETBIOS enabled to that as well, and have that protocol above TCP/IP in the order of binding. If you do the best thing to do is get rid of the 2nd network protocol, go TCP/IP all the way. Alternately reverse the order of binding.