Answer to XP vs. Windows NT Domain Logon

[Renee Gibson]

I'm so goooooooood! Took me a while to figure this out,
but for all who are having trouble getting Windows XP to
talk with a Windows NT Server, here's the deal. You have
to install NetBEUI on the XP machine. Support has been
discontinued, but it's easy to install.

1. Go to your Windows XP CD: ValueAdd\Msft\Net\NETBEUI.
2. Copy nbf.sys to %systemroot%\system32\drivers\.
3. Copy netnbf.inf to %systemroot%\inf\.
Where %systemroot% is WINNT, Windows, or whatever name
you gave it during installation.
4. Go to Network Connections, right-click on your NIC
card, and click on Properties.
5. Click install protocol, and 'Have Disk'. Browse to %
systemroot%\inf\ and click OK.
6. You will see NETBEUI as a protocol. Select this, and
click OK.
7. Reboot your machine.

VIOLA!! Your XP machine should be talking to your
Windows NT 4.0 machine. Make sure to have Service Pack 6
installed on the NT machine. Hey, I need some bucks;
anybody care to pay me for solving their problem?
Hahahaha

Have fun!

P.S. If you do any major reconfigurations, service
packs, etc., on the XP machine, make sure to go into the
Device Manager, on the View link, select show hidden
devices, and make sure NetBEUI is still running, and
doesn't have a yellow exclamation point, or red x next to
it. If it does, go back to Network Connections,
Properties of your NIC card (or RAS connection),
uninstall NetBEUI, and start the above process all over
again. It'll come back like mine did. Don't uninstall
it with the Device Manager; it will still be there when
you list the properties of the NIC-LAN connection. Caio!

 

[Ron Lowe]

I'm so goooooooood! Took me a while to figure this out,
but for all who are having trouble getting Windows XP to
talk with a Windows NT Server, here's the deal. You have
to install NetBEUI on the XP machine. Support has been
discontinued, but it's easy to install.

That's only going to help if the NT4 server is running NetBEUI.

Most don't, and are configured for TCP/IP only.
In which case, adding NetBEUI won't help and
you need to configure TCP/IP on the XP box correctly.

Inability to find a domain is almost always a name resolution issue.
WINS / NetBIOS for NT4 domains;
DNS for 2k / 2k3 domains.

 

[Renee Gibson]

Well, with my configuration, it was important that my XP
machine see everything on the NT Server, and the problems
people have been having will be resolved this way. My
Server is really running Small Business Server 4.5 with
Windows NT 4.0 underneath, and it automatically puts
NetBEUI in the internal NIC card configuration. It would
be nothing to put NetBEUI on the Server. Name resolve
issues are the job of DNS and WINS Servers, and I'm not
as experienced with those products. This will keep folks
happy in the interim.

 

[Bob Cerelli]

If NetBEUI is needed for network access it is generally for a few different
reasons:

1. TCP/IP is not configured correctly on at least one computer
2. There is misconfigured firewall software which NetBEUI doesn't see.
3. TCP/IP is corrupted and simply needs to be removed and reinstalled.

In well over 15 years networking, I have yet to see a network that needed
more than TCP/IP. Everything from the old DOS network days until now. Just
don't need it.

If NetBEUI is making your network function, that is just masking some
misconfiguration somewhere, not really solving the underlying problem.

Bob Cerelli
http://www.onecomputerguy.com