JSC 36381 Baseline Operations Local Area Network (OPS LAN) Interface Control Document International Space Station Program February 2000 National Aeronautics and Space Administration International Space Station Johnson Space Center Houston, Texas
JSC 36381 Baseline MARCH 30, 2000 INTERNATIONAL SPACE STATION Operations Local Area Network (OPS LAN) Interface Control Document 02/00 REVISION AND HISTORY PAGE REV. DESCRIPTION Baseline Release ii PUB.
JSC 36381 Baseline MARCH 30, 2000 INTERNATIONAL SPACE STATION Operations Local Area Network (OPS LAN) Interface Control Document 02/00 The contents of this document are intended to be consistent with the tasks and products to be developed by International Space Station participants. The SSC Operations Local Area Network (OPS LAN) Interface Control Document shall be implemented on new activities and may be implemented on existing projects by an authorized change request.
JSC 36381 Baseline MARCH 30, 2000 LIST OF CHANGES The following table identifies the document paragraphs, tables, and figures that have been changed, per version, as a result of approved Change Requests (CR’s). The CR’s listed below for each version were written against the precursory version of the document (e.g., Version 2.0 changes were made from CR’s written against the Version 1.0 document). Paragraph 3.3.
JSC 36381 Baseline MARCH 30, 2000 INTERNATIONAL SPACE STATION Operations Local Area Network (OPS LAN) Interface Control Document 02/00 SUPPORT POLICY Independent network users of the Operations Local Area Network (OPS LAN) are strongly encouraged to supply the Station Support Computer (SSC) engineering staff their task-specific software for integration into the applicable SSC software load.
JSC 36381 Baseline MARCH 30, 2000 This page intentionally left blank vi
JSC 36381 Baseline MARCH 30, 2000 INTERNATIONAL SPACE STATION DL42 / Station Support Computers Operations Local Area Network Interface Control Document 02/00 Table Of Contents 1 OVERVIEW........................................................................................................ 1-1 1.1 Topology .................................................................................................................................1-1 1.2 Networking Protocols ............................................
JSC 36381 Baseline MARCH 30, 2000 2 STANDARDS.................................................................................................... 2-1 2.1 Timekeeping Standard ........................................................................................................2-1 2.2 Device Naming Convention ...............................................................................................2-1 2.2.1 Windows NT Domain ...........................................................................
JSC 36381 Baseline MARCH 30, 2000 3.1.3.1 IMS...............................................................................................................................3-2 3.1.3.2 HazMat .......................................................................................................................3-2 3.1.4 Crew Mail (E-Mail) Handling........................................................................................3-2 3.1.5 General Network Support .........................................
JSC 36381 Baseline MARCH 30, 2000 4.4 Special Purpose Accounts ...................................................................................................4-1 4.4.1 KFX ....................................................................................................................................4-1 4.4.2 OCAGround .....................................................................................................................4-1 4.4.3 Guest Account..........................................
JSC 36381 Baseline MARCH 30, 2000 Appendices HARDWARE TECHNICAL DATA.................................................................A-1 A.1 ThinkPad Model 760 - Technical Guide & Configuration .........................................A-1 A.1.1 BIOS .................................................................................................................................A-1 A.1.2 ThinkPad Type 9546/9547 – Features and Locations ..............................................A-1 A.1.3 SSC IRQ Plan ...
JSC 36381 Baseline MARCH 30, 2000 CHECKLISTS .......................................................................................................F-1 F.1 PAYLOAD CONFIGURATION CHECKLIST FOR OPS LAN CLIENT.................. F-1 Tables TABLE 2-1 SSC CLIENT DRIVE MAPPING SUMMARY ....................................................................2-3 TABLE 4-1 OPS LAN GLOBAL GROUPS ..................................................................................4-2 TABLE 4-2 OPS LAN LOCAL GROUPS..........
JSC 36381 Baseline MARCH 30, 2000 Introduction Purpose This document formally defines the Operations Local Area Network (OPS LAN) and all operational interface requirements. The OPS LAN ICD provides details of the network’s hardware, software, and connectivity configuration.
JSC 36381 Baseline MARCH 30, 2000 This page intentionally left blank 2
JSC 36381 Baseline MARCH 30, 2000 Chapter 1 1 Overview The OPS LAN Interface Control Document describes the architecture, operation and management of the ISS operations laptop computer network. The OPS LAN is capable of facilitating routine electronic data processing tasks, such as data transfer / storage, procedure viewing, electronic mail (e-mail) and general office automation. 1.1 Topology The OPS LAN uses a multipoint Ethernet bus topology for network communications.
JSC 36381 Baseline MARCH 30, 2000 1.3 Network Devices The structure of the OPS LAN will extend to include the File Server, various client laptops, RF access points, a mass storage device, printers, routers. and any other device that might need to interact with the network. The following sections describe devices already planned for deployment. For the latest information about network devices and their software content, consult the S-POCCB Manifest and Usage web page (see Appendix B.4 ). 1.3.
JSC 36381 Baseline MARCH 30, 2000 1.3.4 Orbital Communication Adapter (OCA) Router After Mission 5A.1, a router will replace the ECS/OCA to provide a true network connection between the ground and OPS LAN. This means that ground personnel will be able to log into the OPS LAN domain and participate in network activity. This OCA Router will be an IBM ThinkPad 760XD mounted on an IBM SelectaDock I docking station and connected to the coax backbone in the U.S. Lab.
JSC 36381 Baseline MARCH 30, 2000 1.3.7 RF Access Point After Mission 5A, two RF access points will be attached to the coax backbone in the U.S. Lab. An access point is a MAC layer bridge that relays data packets between devices on the coax backbone and RF nodes, which are primarily SSC Clients equipped with RF network adapters. One access point utilizes a directional antenna aimed down the central corridor of the ISS.
JSC 36381 Baseline MARCH 30, 2000 To immunize against RF interference and unauthorized eavesdropping, Spread Spectrum technology (also know as “Frequency Hopping”) is employed. In Frequency Hopping, the radio signal “hops” from frequency to frequency within a specified band (ISM 2.4000 – 2.4825) over a set time. Both the transmitter and receiver know the hopping pattern which is called a “channel”. Proxim RangeLAN2 products provide 15 frequency hopping sequences that are orthogonal patterns.
JSC 36381 Baseline MARCH 30, 2000 Chapter 2 2 Standards The information presented in this chapter is based on the deliberations and decisions made by the S-POCCB (Station – Portable Onboard Computer Control Board). Standards chosen for naming and identifying OPS LAN components are subject to change. 2.1 Timekeeping Standard OPS LAN timekeeping devices will be set to and adjusted for GMT (Greenwich Mean Time) without adjustments for daylight savings.
JSC 36381 Baseline MARCH 30, 2000 2.2.3 Windows Networking Workgroups Because every networked Windows NT-based computer (including Windows 95 computers) is a member of a workgroup, clients must be assigned to a workgroup. Member computers of a particular workgroup are visible in Network Neighborhood. SSC clients, including the ECS/OCA, will be members of the SSC workgroup. Any MEC client will be assigned to workgroup CHeCS. 2.2.
JSC 36381 Baseline MARCH 30, 2000 2.3 Drive Mapping Summary Though not required since Network Neighborhood provides resource access, any shared hard disk resource can be assigned a drive letter for convenience. For consistency, each SSC client laptop will follow the drive mapping standards defined below. Note that each laptop will not be mapped to its own internal drive. (See Table 2-1 SSC Client Drive Mapping Summary).
JSC 36381 Baseline MARCH 30, 2000 folder. When the crewmember logs in, the drive letter H: is automatically mapped to the crewmember’s personal home directory folder (see 4.2 Logon Scripts). 2.5 TCP/IP Communication As noted earlier, OPS LAN communicates in the language of the Internet, TCP/IP (Transport Control Protocol/Internet Protocol). A system of logical addresses (as opposed to network adapter hardware addresses) identifies each host, or end station on a TCP/IP network.
JSC 36381 Baseline MARCH 30, 2000 2.6 Radio Frequency (RF) Networking 2.6.1 RF Setup Each device operating with a RangeLAN2 RF network adapter must be set up in either a “station” or “master” mode. The SSC File Server (FServer) will function as the RF master until the RF Access Points arrive onboard Station. 2.6.2 RF LAN Parameters Proprietary Table E-3 RF PARAMETERS SUMMARY lists device settings for the RF portion of OPS LAN.
JSC 36381 Baseline MARCH 30, 2000 This page intentionally left blank 2-6
JSC 36381 Baseline MARCH 30, 2000 Chapter 3 3 Operation Support 3.1 OPS LAN CAPABILITIES Onboard tasks that OPS LAN actively supports include: • Procedures viewing • Timeline event viewing • Database access and management • Crew mail (E-Mail) handling • General network support • Hosting crew support applications • Web-based services support 3.1.1 Procedures Viewing The Manual Procedure Viewer (MPV) is an OPS LAN application that manages and exhibits Operations Data File (ODF) procedures.
JSC 36381 Baseline MARCH 30, 2000 3.1.3 Databases Access and Management Utilizing the OPS LAN, crewmembers will be able to access database information from anywhere in the ISS. Database systems supported by the OPS LAN include IMS and HazMat. 3.1.3.1 IMS Equipment and material aboard the International Space Station will be cataloged and stored in Microsoft SQL databases that will reside on the OPS LAN File Server.
JSC 36381 Baseline MARCH 30, 2000 3.1.5 General Network Support 3.1.5.1 OPS LAN Time Synchronization To synchronize timekeeping across the network, the OPS LAN Time Synchronization utility executes the server-based program Tardis for two minutes. Tardis broadcasts the server’s current time as the network time source. A complementary program on the client, K9, accepts the time broadcasts during this interval and updates the client clock.
JSC 36381 Baseline MARCH 30, 2000 3.1.7.1 Inventory Management System (IMS) To execute IMS, enter //fserver/ims in Internet Explorer’s URL address field on any client laptop. 3.1.7.2 Execute Package (EP) To execute the EP, enter //fserver/ep in Internet Explorer’s URL address field on any client laptop. 3.
JSC 36381 Baseline MARCH 30, 2000 3.2.6 Norton AntiVirus Auto-Protect This service begins the automatic scanning for viruses when the File Server starts. (Automatic startup) 3.2.7 Net Logon The NetLogon service provides users with a single access and authentication point to the OPS LAN NT domain. 3.2.8 PC Card Director The PC Card Director is an IBM-supplied utility that lets you use a PC Card with "Plug and Play" capability. 3.2.
JSC 36381 Baseline MARCH 30, 2000 are maintained for a period sufficient to propagate the information to all WINS servers, after which the extinct name is removed from the WINS database. If a computer has released its name through an orderly shutdown, WINS knows that the name is available and the client can immediately re-obtain the name when it reenters the network. If a computer is not shut down in an orderly fashion, its name reservation remains active in the WINS database.
JSC 36381 Baseline MARCH 30, 2000 Chapter 4 4 Administration 4.1 Administrator Accounts Two administrator accounts have been established for the OPS LAN NT Domain (see Proprietary Table E-5 OPS LAN ADMINISTRATOR ACCOUNTS). Ordinarily, most users will never have to log onto the OPS LAN NT Domain as an administrator, unless directed to do so for troubleshooting or unplanned maintenance. Contact an SSC Engineer for further details. 4.
JSC 36381 Baseline MARCH 30, 2000 4.4.3 Guest Account Due to security concerns, the Windows NT Guest account is disabled. 4.5 Groups Groups simplify network administration by assigning access rights and permissions to a predefined group of users, rather than to a list of individual users. Two types of groups 4.5.1 Global Groups A global group consists of several user accounts from one domain, which are grouped together under an account name.
JSC 36381 Baseline MARCH 30, 2000 Groups Description Account Operators Members who can administer user and group accounts in the OPS LAN Domain. Administrators Members who can fully administer the OPS LAN Domain. Backup Operators Members who can bypass directory- and file-level security to back up files. Guests Users granted guest access to the OPS LAN Domain. INET_User Anonymous IIS User (Needed for SQL Server). MTS Impersonators Microsoft Transaction Server trusted process identities.
JSC 36381 Baseline MARCH 30, 2000 describe the permissions that may be assigned to Windows NT directories and files. Determining the effective NTFS permissions for any network resource may be complicated by a combination of rights assigned to groups and specific individuals. The following three rules can help predict the effective access permission to a network resource: 1) Inheritance Permissions granted to container objects, such as file folders, are inherited in any down-line resource.
JSC 36381 Baseline MARCH 30, 2000 NTFS Permission ( )( ) Meaning No Access Absolutely no access to the directory or its files. Overrides any other NTFS permissions assigned through other group memberships. (none) (none) List (RX) (not specified) Read (RX) (RX) Add (WX) (not specified) Add & Read (RWX) (RX) Change (RWXD) (RWXD) Full Control (all) (all) Special Directory The contents of a directory may be viewed, and subdirectories may be navigated.
JSC 36381 Baseline MARCH 30, 2000 NTFS Permission ( ) Meaning No Access (none) Absolutely no access to the file. Overrides any other NTFS directory and file permissions assigned through other group memberships. Read (RX) The contents of the file may be viewed. Program file may be executed. Change (RWXD) Data files may be edited and deleted. Full Control (all) In addition to capabilities granted in the Change permission, the permissions for that file may be changed and ownership taken.
JSC 36381 Baseline MARCH 30, 2000 only restriction involves home directory folders: users that have a home directory may not access the home directories of other users. The S-POCCB reserves the right to further restrict directory and file access, as conditions warrant. 4.9 Client Security Client laptops are formatted with the Windows 95 FAT32 file system in a single partition. The FAT32 partition, designated the C: Drive, is shared out across the network.
JSC 36381 Baseline MARCH 30, 2000 @ECHO OFF REM Map H to user’s home directory NET USE H: \\FSERVER\$ /YES > NUL REM Map K to data drive (D:) on File Server NET USE K: \\FSERVER\D /YES > NUL REM Map O to C: Drive on OCA machine NET USE O: \\OCA1\C /YES > NUL REM If logging on to the File Server, no further mapping is performed IF Windows_NT == %OS% GOTO EGRESS REM Map M to C: Drive on Medical CHeCS machine NET USE M: \\MEC1\C /YES > NUL :EGRESS EXIT Table 4-7 USER LOGON SCRIPT FILE #2 4.
JSC 36381 Baseline MARCH 30, 2000 or bat) may be uplinked and placed in the File Server Stage Folder (C:\Stage). The UnpackNT application will then automatically run the uplinked files. 4.12 Virus Scanning SSC provides Norton AntiVirus scanning software to accomplish virus scanning on client and server systems. The program will be loaded upon start-up and will run continuously in the background. The program will be set to examine all disk drives continuously also.
JSC 36381 Baseline MARCH 30, 2000 4.15 User Rights Policies These policies pertain largely to various administrative duties for the server or domain. They can be found on the Policies menu in User Manager for Domains. There are eleven regular policies and sixteen advanced policies. The User Rights Policy manages the rights granted to groups and user accounts. The regular user rights policies appear in Table 4-8 REGULAR USER RIGHTS POLICIES.
JSC 36381 Baseline MARCH 30, 2000 User Right Allows those assigned: Assigned To: 1. Access this computer To connect to the computer through the network. Administrators, Everyone 2. Add workstations to domain To add workstations to the domain so that it can recognize the domain’s user and global accounts. (none), but this is a predefined right for all members of the Administrators and Server Operators local groups that cannot be revoked. 3.
JSC 36381 Baseline MARCH 30, 2000 4.16 Auditing Windows NT Server maintains three event logs to which entries are added in the background – the System log, the Applications log, and the Security log. The OPS LAN administrator can set up security auditing of a number of events on NT Server in User Manager for Domains to help track user access to various parts of the system. To enable security auditing, pull down the Policies menu and select Audit.
JSC 36381 Baseline MARCH 30, 2000 intervention, backups will be scheduled during periods of low OPS LAN activity. If necessary, the File Server may be removed from the OPS LAN to shorten the time needed to perform the backup.
JSC 36381 Baseline MARCH 30, 2000 Shuttle Docking Missions to ensure that all affected laptops are consistently reconfigured. 4.19 Software Distribution ThinkPads configured with SSC software loads are located in various JSC organizations, such as the Crew Office and Training Facilities. To facilitate reloads or updates to these machines, special diskettes are issued to the qualifying organizations.
JSC 36381 Baseline MARCH 30, 2000 Appendix A A Hardware Technical Data A.1 ThinkPad Model 760 - Technical Guide & Configuration A.1.1 BIOS Model Date Version 760XD 3/12/98 1.47 760ED 3/12/98 1.54 Table A-1 IBM ThinkPad 760XD IRQ Settings A.1.2 ThinkPad Type 9546/9547 – Features and Locations Front View: http://servicepac.mainz.ibm.com/eprmhtml/epr2c/5307.htm Rear View: http://servicepac.mainz.ibm.com/eprmhtml/epr2c/5308.htm A.1.
JSC 36381 Baseline MARCH 30, 2000 settings are automatically configured when AutoLoader is used to load an SSC laptop. A.2 Calluna PC Hard Card Data can be written to and read from a PC Card (i.e., CallunaCard), via the ThinkPad PCMCIA port. Presently, only Calluna model #CT521RM is certified for flight. On SSC Clients, follow appropriate procedures for removal and insertion of PC Cards to prevent operating system failure.
JSC 36381 Baseline MARCH 30, 2000 PHYSICAL CHARACTERISTICS Height Length Width Weight 0.41" (10.5mm) 3.37" (85.6mm) 2.13" (54.0mm) 2.82 oz (80g) 0.41" (10.5mm) 3.37" (85.6mm) 2.13" (54.0mm) 2.
JSC 36381 Baseline MARCH 30, 2000 Power Requirements Operating voltage +5 V ± 5% @ 50 mA Mean time Between Failures (hours calculated) 3C589D-TP PC Card 40 °C (104 °F) benign environment 50 °C (122 °F) benign environment 40 °C (104 °F) mobile environment 50 °C (122 °F) mobile environment 346,440 228,608 62,602 53,818 FCC Certification Part 15, Class B A.
JSC 36381 Baseline MARCH 30, 2000 A.5 Proxim RangeLAN2 Model 7520 Access Point Image Network Interfaces Data Rate Media Access Protocol Ethernet Compatibility Frequency Band Independent Channels Output Power Size ETSI Testing Operating Temperature UL Listed Power Supply n/a Ethernet 10BASE2 (Thin) BNC Ethernet 10BASET (Twisted-Pair) 1.6 Mbps – RangeLAN2 10 Mbps – Ethernet RangeLAN2 CSMA/CA Ethernet packet types and Ethernet Addressing 2.4-2.483 GHz (in the U.S.
JSC 36381 Baseline MARCH 30, 2000 A.8 SanDisk PC Card II ATA (85MB) Power Requirements DC Input Voltage, Commercial Typical Power Dissipation Temperature Operating Non-Operating 3.3V ± 5%, 5V ± 10% Sleep 200 µA (3.3V) 500 µA (5V) Read 32-45 mA (3.3V) 46-75 mA (5V) Write 32-60 mA (3.3V) 46-90 mA (5V) 0 - 60°C -25 – 85°C A.
JSC 36381 Baseline Bus Interface Printing Speed Resolution Network Interface Weight Collapsed Size Operating Temperature Power Requirement Power Consumption MARCH 30, 2000 PCMCIA PC Card Standard 2.1 compliant B&W – 7 ppm Color – 8 ppm 720 dpi 10Base2, 10BaseT 14.3 lbs. 7.4 in. x 18.7 in. x 10.7 in. 10 to 35 °C 115 VAC 400 Hz 120 VDC 28 VDC (w/external power supply) 21.5 W – maximum 18.3. W – printing 9.7 W – idle < 10 min. 7.0 W – idle > 10 min. 1.9 W – off A.
JSC 36381 Baseline MARCH 30, 2000 This page intentionally left blank A-8
JSC 36381 Baseline MARCH 30, 2000 Appendix B B References B.1 SSC Engineering Staff Name Telephone E-Mail Dobek, George S. (281) 244-0210 george.s.dobek1@jsc.nasa.gov Dorman, Robert A. (281) 244-0234 robert.a.dorman1@jsc.nasa.gov Lenio, James A. (281) 483-5795 james.a.lenio1@jsc.nasa.gov Michel, John M. (281) 244-1124 john.m.michel1@jsc.nasa.gov Qureshi, Saera T. (281) 483-8125 saera.t.qureshi1@jsc.nasa.gov Sandison, Douglas P. (281) 483-7715 douglas.p.sandison1@jsc.nasa.
JSC 36381 Baseline MARCH 30, 2000 B.3 Related NASA Documents Interface Definition Document for the Orbiter Communications Adapter (OCA) Kevin Hames/EV21, Project Manager, (281) 483-8592 JSC 28337 Orbital Communications Adapter (OCA) Operations Concept Fisher Reynolds/DO45, III, Book Manager, (281) 244-1172 JSC 28403 SSC Software Management Plan Robert A. Dorman/DL42, Book Manager, (281) 244-0234 JSC 48531 B.
JSC 36381 Baseline MARCH 30, 2000 Appendix C C Glossary Autoloader TBD Backup TBD Disk Imaging TBD Disk Mapping TBD DNS Domain Name System. This vitally important system provides distributed, redundant directories that map numeric IP addresses to easy-to-type, easy-toremember domain names. (For example, 209.185.180.170 is the numeric IP address for the whole wide Web.) Domain In Windows NT, a logical administrative unit used to simplify network management.
JSC 36381 Baseline MARCH 30, 2000 ODF An Operations Data File (ODF) procedure is a set of instructions used by ground controllers, the on-board crew and for the on-orbit procedures executor software to fulfill specific tasks. These are the tasks needed to operate and maintain station systems, payloads, and attached vehicles under both nominal and off-nominal conditions.
JSC 36381 Baseline MARCH 30, 2000 Appendix D D Acronyms ASP BNC BIOS CGI CHeCS CMOS CPS CPU CSMA/CA DOS DVD ECS FAT FGB GMT HTML HTTP IDE IIS IMAP IMS IOL IP IRQ ISA ISS JIN KFX LAN LED MAC MACE MDM MEC MPV NASA NAV NetBEUI NetBIOS NTFS OPR OCA OPS LAN OSTPV Active Server Pages BayoNet Connector Basic Input / Output System Common Gateway Interface Crew Health Care System Complementary Metal Oxide Semiconductor Color Printer Subsystem Central Processing Unit Carrier Sense Multiple Access/Collision Avoi
JSC 36381 Baseline PCI PCMCIA PCS RF ROM RTC SCSI SM SMTP S-POCCB SQL SSC SSL SSP TBD TDR(S)S TCP/IP URL Win95 WinNT WINS MARCH 30, 2000 Peripheral Component Interconnect Personal Computer Memory Card International Association Portable Computer System Radio Frequency Read-Only Memory Real-Time Clock Small Computer Systems Interface Service Module Simple Mail Transport Protocol Station - Portable Onboard Computer Control Board Standard Query Language Station Support Computer Secure Socket Layer Space Statio
JSC 36381 Baseline MARCH 30, 2000 Appendix E E LAN Configuration Details This appendix contains local area network configuration details which include IP addresses and login ID’s. Due to the sensitive nature of this information, it is under limited and controlled distribution. To obtain a copy of this appendix, please contact the S-POCCB or SSC point of contact.
JSC 36381 Baseline MARCH 30, 2000 This page intentionally left blank E-2
JSC 36381 Baseline MARCH 30, 2000 Appendix F F Checklists F.1 PAYLOAD CONFIGURATION CHECKLIST FOR OPS LAN CLIENT 1. Submit an S-POCCB CR to request SSC OPS LAN network resources, such as IP addresses (http://fltproc.jsc.nasa.gov/s-poccb/Cr-dr/). Contact the S-POCCB office for CR system access privileges. Reference Chapters 1-4 of this document for network connectivity rules and guidelines (e.g: network parameters, IRQ’s Drive mappings etc.). 2.
JSC 36381 Baseline MARCH 30, 2000 NOTE DO NOT EJECT FLOPPY DISK, PRESS ANY UNNECESSARY BUTTONS, OR DISCONNECT POWER SUPPLY DURING COURSE OF PROGRAM. _____ Boot laptop from the AutoLoader floppy disk and allow program to execute. _____ Select Option 2 (“Configure CMOS settings for SSC Client, PCS, MPSD, or CPSD”) _____ Allow program to execute. _____ AutoLoader Reconfiguration Summary _____ _ for message “Current CMOS Configuration valid for: SSC Client, PCS, MPSD or CPSD.”.
JSC 36381 Baseline MARCH 30, 2000 NOTE CONTACT SSC OFFICE FOR YOUR NETWORK PARAMETERS _____ Specify IP address ( Network Neighborhood | properties) for computer by selecting TCP/IP _ Proxim RangeLAN2 7400 PC Card Adapter | properties. ⇒ IP Address: _____________, ⇒ Subnet Mask: _______________ _____ Select OK and reboot. 7. Install RangeLAN2 Site Survey and Configuration tools using the following steps: _____ Use RangeLAN2,Win95/NT, P/N 9450.0132 Rev. B floppy disk. _____ Run | a:\setup.
JSC 36381 Baseline MARCH 30, 2000 _____ Select Clients for Microsoft networks for the primary network logon. _____ Under the ‘File and Print Sharing’ button, select the appropriate/required settings. _____ Sel OK and reboot. 10. NOTE CONTACT SSC OFFICE FOR YOUR NETWORK PARAMETERS In Network Properties, configure your Win95 load network component ‘Client for MS Networks’ to ‘Logon to WinNT domain’, Domain = _________. Also set ‘Quick logon’ as the logon option.
JSC 36381 Baseline MARCH 30, 2000 NOTE CONTACT SSC OFFICE FOR YOUR NETWORK PARAMETERS. _____ In Network neighborhood | properties select TCP/IP _ Proxim RangeLAN2 7400 PC Card Adapter | properties. _____ _IP address ________________, Subnet mask _______________________ _____ _DNS disabled by clicking at the DNS configuration tab. _____ _’Client for Microsoft networks’ and ‘File and print sharing’ check boxes are enabled by clicking the binding tab.
