---------------------------------------------------------------------------- The Florida SunFlash NetBIOS and IPX for PC-NFS SunFLASH Vol 43 #14 July 1992 ---------------------------------------------------------------------------- This SunFlash article consists of two articles by Dave Pool of Syry (dave@spry.com (206) 286 1412). As questions from Sun users about interoperating with PC servers are common, I hope that you will find this information useful. The first article describes using NetBIOS with PC-NFS and the second describes using Novell's IPX with PC-NFS. -johnj ---------------------------------------------------------------------------- Spry NetBIOS for PC-NFS What is NetBIOS: * Network Basic Input-Output System * A service mechanism. * A software interface What does NetBIOS do? * Provides both connection-oriented (session) and connectionless (datagram) services. * Broadcast and multicasts are supported. * Participants are identified by names, which are assigned in a dynamic and distributed manner. NetBIOS Mechanisms (NetBIOS Service) can: * Locate resources. * Establish connections. * Send and receive data * Close connections. NetBIOS End-Nodes: Three types of end-nodes are defined: * Broadcast "B" nodes * Point-to-point "P" nodes * Mixed mode "M" nodes * "B" nodes use UDP datagrams (broadcast as well as directed). Most commonly implemented is the "B" nodes for TCP connections. Limitation are lack of ability to pass through routers. Solution: implement a NetBIOS Name Server. TCP/IP and NetBIOS RFC 1001/1002 - NetBIOS over TCP/IP RFC 1001: Describes ideas and general methods used to provide NetBIOS on a TCP/UDP foundation. RFC 1002: Contains detailed descriptions of packet formats, protocols and defined variables/constants. NetBIOS establishes connections by polling hosts for their NetBIOS Network name. This process is called name registration. Name registration maps a user-friendly name such as SUN-1 to the phisical address of a network adapter. Implementation: Spry will implement NetBOIS over PCNFS . NetBIOS over PCNFS using the XTI or OPI (Open Protocol Interface) interface. NetBIOS Operations To use NetBIOS you must first load PCNFS then load NetBIOS, then start your application program. To start NetBIOS: netbios [-n] [-s scope] -s scope option This allows you to change the scope string from the default to another string. We will set our scope string to "NFS" When you use NetBIOS implementation from two or more vendors, the scope identifier must be the same. Option "-n" This function will allow you to disable timeouts. Multiple operation on the client will delay the return message. This will allow the netbios packet to not time out due to the delay. Note: Netbios (1001/1002) must be running over TCP/IP on both sides of the communications path. ie: NetBIOS over Novell Netware will not communicate with NetBIOS over TCP/IP due to the different transport protocols IPX/SPX and TCP/IP. -------------------------------------------------------------------------------- The technical advantages of SUN PC-NFS with Spry Concurrent over Novell LAN Workplace for DOS. -------------------------------------------------------------------------------- 1) Using Spry Concurrent and PC-NFS you gain file services from both the SUN Server via TCP and the Novell server via IPX. Your PC still has over 600k left of conventional memory. Example: McDonnell Douglas needs to copy files from the Novell Server to the SUN Server using Microsoft Windows. Using Spry Concurrent and Sun PC-NFS you have virtual drives mounted on both systems and can copy files using standard copy commands in file manager. 2) Client server applications written to the SUN PC-NFS XTI specification are transport independent. Example: GE Aerospace is writing applications to PC-NFS and are going to move to OSI. With PC-NFS you do not need to re-write the application to interface to OSI thus saving the customer valuable programming time and money. 3) Using Spry Concurrent you gain concurrent Novell access with PC-NFS and you also can run a third or fourth protocol such as DECnet or NetBIOS. LAN Workplace for DOS only supports ODI and DECnet; NetBIOS only supports NDIS. Example: From a single PC on the Network a user may access Novell, Sun Servers, DEC Pathworks, and LAN Manager. Without rebooting the PC. Configuration for running PC-NFS and Novell Netware at the same time and still having 600k left over. Novell Netware and Sun PC-NFS Configuration (Sample configuration using MS DOS 5.0, Quarterdeck's QEMM386, and a 3COM 3c503 network interface card) AUTOEXEC.BAT SET TZ=PST8PDT PATH C:\;C:\DOS;C:\NFS;c:\utils\qemm SET TEMP=C:\windows\TEMP prompt $p$g set comspec=c:\dos\command.com c:\lanman\ipx c:\lanman\netbind SET NFSDRIVE=C PRT * NFSRUN c:\lanman\emsnetx f: login CONFIG.SYS device=c:\utils\qemm\qemm386.sys RAM x=B000-B7FF ARAM=DC00-DD10 files=30 buffers=30 DEVICE=c:\utils\qemm\loadhi.sys /r:2 /res=4208 /sqf c:\dos\ansi.sys device=c:\lanman\protman.dos /I:c:\lanman\ rem *** NDIS driver for 3Com 3c503 *** device=c:\utils\qemm\loadhi.sys /R:1 C:\LANMAN\elnkii.dos DEVICE=C:\UTILS\QEMM\LOADHI.SYS /R:1 C:\NFS\PCNFS.SYS DEVICE=C:\UTILS\QEMM\LOADHI.SYS /R:2 C:\NFS\SOCKDRV.SYS device=c:\lanman\nfs-ndis.sys lastdrive=e SHELL=C:\DOS\COMMAND.COM C:\DOS\ /p /e:256 dos=high PROTOCOL.INI [PROTOCOL MANAGER] Drivername = PROTMAN$ ; - MAC Drivers ------------------------------ ;3Com 3c503 [ETHERLINKII] Drivername = ELNKII$ Interrupt = 5 IOAddress = 0x300 DMAChannel = 1 MaxTransmits = 8 Transceiver = ONBOARD ; - Protocol Drivers ------------------------- [SPRY CONCURRENT] Drivername = SPRY$CONCURRENT Bindings = ETHERLINKII [NFS-NDIS] Drivername = NFSLINK1 Bindings = ETHERLINKII With this configuration of SPRY Concurrent, Sun PC-NFS, DOS 5.0, and Quarterdeck's QEMM386, there is almost 600k left in conventional memory to run your applications. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ For information send mail to info-sunflash@sunvice.East.Sun.COM. Subscription requests should be sent to sunflash-request@sunvice.East.Sun.COM. Archives are on solar.nova.edu, paris.cs.miami.edu, uunet.uu.net, src.doc.ic.ac.uk and ftp.adelaide.edu.au All prices, availability, and other statements relating to Sun or third party products are valid in the U.S. only. Please contact your local Sales Representative for details of pricing and product availability in your region. Descriptions of, or references to products or publications within SunFlash does not imply an endorsement of that product or publication by Sun Microsystems. John McLaughlin, SunFlash editor, flash@sunvice.East.Sun.COM. (305) 776-7770.