| Feedback from Last Month

  received a few letters this month pointing out corrections or additional information regarding my column last month. Here are a few.

  First, Chris Williams:

  > 1) NetBIOS over TCP/IP (NBTCP) has a number of options that are not obvious in Warp 4, but are critical if you need to internetwork properly with a Windows network running NBTCP and if using routers (which is now becoming quite common). There are actually 3 types of NBTCP nodes, B-Node, P-Node, and H-Node. I won't get into the differences here, but the default type for Warp 4 is B-Node while for Win95 & NT it's H-Node. This is OK if you're all on the same network segment, but it's a problem if there is more than one segment. The problem is with NetBIOS name resolution (a.k.a WINS in the Windows world and RFCs 1000 & 1001 to everyone else). Again, it would take too long to explain here. The fix is to configure Warp 4 as an H-Node on the network.

  > 2) NetBEUI is still a common protocol for small networks, but most people are now really moving fast towards NBTCP in "GatesWorld". This is because you get it automatically if you install the MS TCP/IP stack on a Windows machine. This isn't the case with Warp 4. You need to configure it specifically. Also in Warp 4, if you configure NBTCP, you must have TCP/IP in you stack, but IBM NetBIOS is not required. Warp 4 also will use DHCP to get its TCP/IP address and other information if a DHCP server is available (even an NT DHCP server).

  > 3) I can confirm that Warp 4 does not require a computer account to participate in a Windows NT domain. In fact, a Warp 4 workstation winds up looking to NT's Server Manager like a LAN Manager version 5 server!

  > - Chris Williams

  Next, Brian Futrell:

  > Also, to log onto an NT server, you must use the "Lan Manager Logon" instead of File and Print Client's logon, specifying the NT domain name in the Domain Name field. This will allow connection to any shared resources on the server and any machine connected to it (if the connected machines also have the peer-to-peer components installed properly).

  > - Brian Futrell

-

This page is maintained by Falcon Networking. We welcome your suggestions.

Copyright © 1997 - Falcon Networking