"Failed to Access NBT Driver 1" when using nbtstat IT'S KILLING ME!

[AceHigh1234]

I am setting up a small network with a router & cable modem, 1 windows XP machine, and 1 windows 98 machine. The router sends WINS information over DHCP, and can see the hostnames of each computer. Both computers can access the internet. I can ping machine A from machine B and vice-versa. I am not, however getting successful name resolution. I can't share files or printers, or 'see' the other machines on the network from either machine. nbtstat with any option gives me the message "Failed to Access NBT Driver 1" and the majority of responses upon a google of that phrase are from forign sites. I tried setting up an LMHOSTS file on both machines, but I am still getting no name resolution from either machine on it's own. Thanks for any assistance, I am setting this up for a client and it's driving me crazy. (As a fox?? I'm doing the research on their clock

 

[bcastner]

I am not sure what router supports natively a WINS server, I have never heard of such a thing.

Disable the WINS feature.

 

[AceHigh1234]

bcastner, you've never seen the option in Windows XP under the properties of TCP/IP to use "NetBIOS over DHCP"? Or in Windows 98 the option "Get WINS from DHCP Server" (not positive about the wording of that one, but it's located in the same place as the win XP example) NetBIOS names are resolved by a WINS server. If you have a router installed, and it has a built in DHCP server, and it suports WINS hostnames (D-Link DI-604 is one) then you can use the the routers DHCP server to pass the NetBIOS names. And it doesn't work with WINS disabled. How are the two computers in the workgroup supposed to communicate with each other? Can't use DNS, there is no active directory in a workgroup.

 

[bcastner]

The option is 'enable Netbios over TCP/IP.'
A WINS server is found to my knowledge only on Microsoft server products.

In the absence of a WINS server, Netbios names are resolved through the Computer Browser service, a broadcast based resolution. The router's DHCP server has no role in this whatsoever, other than to keep all the workstations in the same subnet.

But your explanation above may reveal the clue as to the problem. If an ipconfig /all shows a Node Type of anything other than Broadcast, Hybrid or Not defined, Netbios name resolution will fail.

Open a notepad session as node.reg, and copy paste the below into the session:

***** start copy/paste below this line:
REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
"NodeType"=dword:00000008

***** end copy/paste above this line

Save the file and double-click your new "node.reg" to merge the contents with the registry. This sets a Hybrid node type. Change the "8" above to "1" to force a pure broadcast Node Type if you prefer.
Reboot to see the change.

 

[Serbtastic]

And just FYI you CAN use DNS in a workgroup, you only need to setup a DNS server. Active Directory is not required.

 

[bcastner]

A DNS server is possible in a Workgroup, just not from Microsoft unless you install at least one Windows Server package in a Workgroup (non-Domain) configuration. Microsoft does not offer either WINS or DNS servers for a client OS.

I have been playing with Posadis:

http://posadis.sourceforge.net/

 

[bcastner]

I should also note that I have complained about this for two years to the Windows Server Product Group at Microsoft. It seems clear that there will not be a client-hosted DNS or WINS server option ever made available. What does seem likely in the next two years is something IPv6-based even for Workgroups. So no more Netbios, browser issues, and NETBUI.

 

[bcastner]

Let me take the opportunity to correct one statement above:
Quote: "A WINS server is found to my knowledge only on Microsoft server products."

I believe some LINUX implementations offer a WINS server. I just honestly do not know of any more details.

 

[AceHigh1234]

bcastner, I will try the registry edit when the client gets back in to town. Thanks for the assistance, and hopefully when I update you, I'll have something more

 

[bcastner]

AceHigh1234,

Please keep us informed in the Forum.

This is a resolvable issue.

My fellow MVP Hans-Georg has a site that might help:

http://www.michna.com/kb/wxnet.htm

 

[AceHigh1234]

Alright, I tried the registry import and am preparing to reboot. Also, I'd like to note that I can not access shared resources by IP address or share name.

Thanks

 

[AceHigh1234]

Just tried the registry import and am preparing to reboot.
Also, I'd like to note that I can't access shared resources by IP or share name

 

[AceHigh1234]

Actually, the problem was solved. I had the client search out their win98 disk. Then I removed the driver for the Linksys NIC. Rebooted, and pointed the hardware wizard to the location of the NIC drivers on the c:\, and put the Win98 CD when prompted, and whamo - no problems. Durn win 98.. Thanks for your help everyone!