NetBIOS Extended User Interface (NetBEUI) is well suited for use in small networks. You can install a NetBIOS gateway and the NetBEUI client protocol on all servers running Windows 2000 and most Windows clients. Previous versions of Windows NT and Windows 9x and Windows for Workgroups may use NetBEUI. Remember that NetBEUI is not routable and the only option for the protocol is the computer name. This makes it very easy to configure a small office or home office (SOHO) network. NetBEUI is supported by VPNs as well and that means that you can support remote networks or SOHO users running the NETBEUI protocols. Windows 2000 is installed in mixed-mode configuration by default. This means that the NT Lan Manager authentication mechanism can be disabled by switching to native mode. A mixed mode network uses any combination of Windows NT 4.0 and Windows 2000. Here are some examples: (1) Windows NT 4.0 Workstation authenticating to a Windows 2000 domain controller (2) Users in a Windows NT 4.0 domain authenticating to a Windows 2000 domain (3) Windows 2000 Professional client authenticating to a Windows NT 4.0 PDC or BDC Finally Windows NT Lan Manager is the authenticating protocol for computers that are stand-alone servers and workgroups. This is all documented in the Windows 2000 server resource kit.. Lance Ecklesdafer MCSE, CNP, CNE, MCP+I [EMAIL PROTECTED] ----- Original Message ----- From: "Steve Riley (MCS)" <[EMAIL PROTECTED]> To: "'Paul Gracy'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "'netcomm'" <[EMAIL PROTECTED]> Sent: Wednesday, July 05, 2000 4:38 PM Subject: RE: Win2K > Which protocols are used depends on what the needs of the traffic are. > Windows 2000 uses TCP/IP as its default protocol -- unlike NT 4, NetBEUI is > no longer installed. NetBIOS -- over TCP/IP -- is used when two machines are > doing file and print sharing. SMB (Server Message Block), the file/print > sharing application protocol, requires NetBIOS, which in turn runs over > TCP/IP. > > Unlike what you may have heard, typically you can't expunge NetBIOS from > your network. If you're not using any services that require SMB, *and* > you're not running Windows 2000 Advanced Server clusters, it's *possible* to > turn off the TCP/IP-NetBIOS helper and shut down the server service, which > would eliminate NetBIOS. > > And yes, you can have trusts between Windows 2000 and NT 4 domains. Your > Windows 2000 domains can even run in native mode. The only time you need to > keep your Windows 2000 domains in compatibility mode (actually called "mixed > mode") is if you have to keep some NT 4 BDCs in the same domain. > > ___________________________________________________________ > Steve Riley > Microsoft Telecommunications Consulting in Denver, Colorado > [EMAIL PROTECTED] > +1 303 521-4129 or [EMAIL PROTECTED] > www.microsoft.com/isn/ > Applying computer technology is simply finding the right wrench to pound in > the correct screw. > > > -----Original Message----- > From: Paul Gracy [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 5, 2000 11:55 AM > To: [EMAIL PROTECTED]; 'netcomm' > Subject: RE: Win2K > > > Adding an NT 4.0 box requires that the Win2K machine run NetBT, aka NetBIOS > over TCP/IP. It does not require the horrid, evil, 1980's based NetBEUI. > This is called 'compatibility mode'. > > -----Original Message----- > From: netcomm [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 29, 2000 6:11 AM > To: [EMAIL PROTECTED] > Subject: Win2K > > > > Hi > > just started working on Win2k. I have install one win2k domain controller > and wish to include one more win2k machine in that domain. ( like a member > server concept in earlier version). Now my concern is what would be the > protocol for the traffic between these win2k macines. I hope it is not > netbios??? > Is it possible to have a one way trust relation ship between win2k domain > controller and WinNT4.0 domain controller.?? > > any info or pointers are welcome.... > > TIA > Madhur > - > [To unsubscribe, send mail to [EMAIL PROTECTED] with > "unsubscribe firewalls" in the body of the message.] > - [To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe firewalls" in the body of the message.]
