Help Essay Research Paper CLIENT FOR NETWARE free essay sample

Help Essay, Research Paper CLIENT FOR NETWARE Windows 95 and NetWare 3.12 and 4.01 Waiters Opening Files on NetWare 3.11 Waiters Lowercase Extended-Character Passwords on NetWare 4.1 Waiters Client for NetWare and Programs That Use External Files Novell NetWare Login Scripts Installing Novell Client32 Overwrites NetWare Directory Services Files Upgrading Over an Earlier Beta Version of Windows Printing to NetWare Directory Services Printers Plug AND PLAY NETWORK CARDS AND 16-BIT REAL-MODE DRIVERS INTEL ETHEREXPRESS 16 NICs AND PCI COMPUTERS WINDOWS FOR WORKGROUP SHARES Run WINDOWS 95 FROM A SERVER To Install Windows 95 over Previous Physiques Support FOR THIRD-PARTY NETWORKS LANDESK 2.0 SunSelect PC-NFS Banyan VINES DEC Pathworks Artisoft LANtastic Printing TO A NETWORK PRINTER PROBLEMS PRINTING TO POSTSCRIPT PRINTERS OVER A NETWARE NETWORK ISSUES AND INSTALLATION OF MS-DLC WITH WINDOWS 95 MICROSOFT TCP/IP PROOL USER PROFILES OVER THE NETWORK NETWORK BACKUP AGENTS Arcada Backup Exec Network Backup Agent Cheyenne ARCserve Network Backup Agent REAL-MODE PROOLS: Warning ICONS ON YOUR NETWORK ADAPTER USING AN IBM THINKPAD WITH A DOCK II INTEL ETHEREXPRESS PRO /100B CARD NOT CORRECTLY DETECTED Setting UP A WINS SERVER INTERLNK Exploitation COMSPEC VARIABLES POINTING TO NETWORK COMMAND. We will write a custom essay sample on Help Essay Research Paper CLIENT FOR NETWARE or any similar topic specifically for you Do Not WasteYour Time HIRE WRITER Only 13.90 / page COM FILES CLIENT FOR NETWARE ================== Windows 95 and NetWare 3.12 and 4.01 Waiters # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8211 ; Windows 95 with Microsoft Client for NetWare can see jobs with NetWare 3.12 and 4.01 waiters if package explosion is turned on. This is a known job with these waiters that Novell has fixed and posted on their forums. Download the file Pburst.exe from the Novell NetWare Forum on Compuserve or the Novell Web site ( Ftp.Novell.com ) . Pburst.exe contains the spot for the affected waiters. Opening Files on NetWare 3.11 Waiters # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; Plans that open a big figure of files consecutively in rapid sequence might hold occasional jobs opening files on NetWare 3.11 waiters. This can besides go on when opening a file in a booklet for which you do non hold file scan rights, such as an MS Mail shared station office. Possible mistake messages: # 8220 ; File non found # 8221 ; mistake on a file you know exists # 8220 ; Sharing misdemeanor # 8221 ; or # 8220 ; Lock misdemeanor # 8221 ; mistake # 8220 ; Unable to open file # 8221 ; mistake # 8220 ; File in use # 8221 ; mistake There are two solutions to these jobs: Obtain a spot file from Novell for the NetWare 3.11 waiter. Using FTP, connect to ftp.novell.com. Travel to /pub/netware/nwos/nw311/osnlm and run 311ptd.exe. This plan will pull out the file os2opnfx.nlm. Then, load the.nlm file onto the NetWare 3.11 waiter. ( # 8221 ; load os2opnfx.nlm # 8221 ; ) Disable long filename support in Client for NetWare. This means that you will non be able to utilize long file names on any NetWare waiters from Windows 95. To disable long-filename support, carry out the following stairss: 1. Snap the Start bill of fare, click Run, and so type Regedit. 2. Travel to HKEY_Local_MachineSystemCurrentControlSetServicesVxDNWRedir 3. Make a new binary value named supportLFN with a value of 0. Lowercase Extended-Character Passwords on NetWare 4.1 Waiters # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; In a NetWare 4.1 environment, Client for NetWare does non back up watchwords that use certain small letter extended characters. Users demand to alter their watchword to all uppercase characters. Client for NetWare and Programs That Use External Files # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; If you are utilizing Microsoft Client for NetWare, and you run a plan that needs to entree an subsidiary file, your plan will hold jobs if the subsidiary file is on a thrust other than the one the plan is on. This is because merely the current thrust is searched for subsidiary files ; the hunt way is non searched. If you experience this job, do certain the plan and any subsidiary files are on the same thrust. Novell NetWare Login Scripts # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; The Login Script Processor for the Microsoft Client for NetWare should right process all bids in your login books. However, you can non lade memory-resident plans ( TSRs ) from these books. Installing Novell Client32 Overwrites NetWare Directory Services Files # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; When you install Novell Client32, the Novell apparatus plan replaces the Microsoft file Netdef.inf and renames it Netdef.bnw, and deletes the NDS apparatus file Nwnds.dll. The consequence is that after uninstalling Novell Client32, Service for NetWare Directory Services will non install. To work around this job, carry out the undermentioned stairss: 1. Find the file Netdef.bnw and rename it Netdef.inf. 2. Copy the Nwnds.dll file to the WindowsSystem directory on your your difficult disc by transporting out the undermentioned process: 1. Insert your Windows 95 installing Cadmium into the CD-ROM thrust. 2. Open an MS-DOS window. 3. Change to the Win95 directory on your CD-ROM, and so type the following at the bid prompt: extract /l degree Celsius: windowssystem precopy2.cab nwnds.dll Upgrading Over an Earlier Beta Version of Windows # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; If you upgrade this release of Windows over an earlier beta release, and you have Service for NetWare Directory Services installed, you will be prompted about version struggles for the undermentioned files: Nwnp32.dll ( v. 4.0.969 ) Nwlsproc.exe ( v. 4.0.968 ) Netware.tmp ( v. 4.0.968 ) When you see the version struggle prompt, click No. After Windows is installed, you need to reinstall Service for NetWare Directory Services. To make this, carry out the undermentioned stairss: 1. In Control Panel, double-click the Network icon. 2. Click Add, click Service, and so snap Add. 3. Follow the instructions on your screen. Printing to NetWare Directory Services Printers # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8211 ; You can non put in Client for NetWare Networks and Service for NetWare Directory Services ( NDS ) during the same installing session. If you make, your NDS pressmans will look to be offline. If your pressmans appear to be offline, seek transporting out the following stairss: 1. In Control Panel, double-click the Network icon. 2. Remove both Client for NetWare Networks and Service for NDS. 3. Restart your computing machine. 4. In Control Panel, double-click the Network icon. 5. Add Service for NDS. 6. Restart your computing machine. Note: If your local country web is utilizing NetWare 4.1 or subsequently, there is no demand to put in Client for NetWare Networks individually. When you install Service for NDS, it besides installs the Client for NetWare Networks. Plug AND PLAY NETWORK CARDS AND 16-BIT REAL-MODE DRIVERS ======================================================== When you run the 16-bit real-mode driver for your Plug and Play web interface card ( NIC ) , your Plug and Play card might look non to map. The ground the card appears to malfunction is that on most computing machines, the Plug and Play card is inactive until Windows 95 enables it. 16-bit NIC drivers load before Windows 95 can turn on Plug and Play cards. Some 16-bit NIC drivers do non acknowledge Plug and Play cards ( most NE2000 Plug and Play ringers fall into this class ) . In this instance, follow these stairss to utilize your Plug and Play card with a 16-bit NIC driver: 1. Run the Softset public-service corporation that comes with your Plug and Play card, and so put the card to non-Plug and Play manner. 2. Remove the web card from the list of devices in the Device Manager listing: In Control Panel, double-click the System icon, snap the Device Manager check, select the web card, and so chink Remove. 3. Reinstall the web card utilizing the Add New Hardware icon in Control Panel. When you install a 32-bit protect manner NIC driver in the hereafter, you can rebroadcast Softset to turn on Plug and Play manner for your card. This job does non go on if you are utilizing a 32-bit protect-mode NIC driver. INTEL ETHEREXPRESS 16 NICs AND PCI COMPUTERS ============================================ If you are utilizing an Intel EtherExpress 16-network interface card ( NIC ) in a PCI computing machine that has a Diamond Speed Star PCI video card, your system might hang or non initialise decently. These jobs, harmonizing to Intel client support, are non related to Windows 95 and go on on a assortment of runing systems. If you have one of the undermentioned picture cards, reach your seller to obtain a new picture BIOS update: * Diamond Speed Star PCI video card with BIOS version 1.01 * Diamond Viper PCI VGA Video Adapter * Diamond Stealth picture card, BIOS v1.03 Other PCI picture cards might besides do jobs with this Intel NIC. In general, if you experience jobs with your EtherExpress 16 in a PCI computing machine other than those described above, delight replace the card before describing the job to Microsoft. WINDOWS FOR WORKGROUP SHARES ============================ When you upgrade to Windows 95 from Windows for Workgroups, your portions are non maintained. The folders/directories you shared in Windows for Workgroups need to be reshared. Run WINDOWS 95 FROM A SERVER ================================ Windows 95 can be set up to run from a web waiter. The Windows 95 Resource Kit contains complete instructions for put ining Windows in this environment ( see Chapter 4, # 8220 ; Server Based Setup for Windows 95 # 8243 ; ) . The undermentioned constellations are supported: Booting from difficult disc utilizing: # 8211 ; Client for Microsoft Networks # 8211 ; Client for NetWare Networks # 8211 ; Novell Workstation Shell 3.x ( NETX ) # 8211 ; Novell Workstation Shell 4.x ( VLM ) # 8211 ; Banyan VINES DOS/Windows client Booting from a floppy disc utilizing: # 8211 ; Client for Microsoft Networks # 8211 ; Client for NetWare Networks # 8211 ; Novell Workstation Shell 3.x ( NETX ) # 8211 ; Novell Workstation Shell 4.x ( VLM ) # 8211 ; Banyan VINES DOS/Windows client Booting from a distant boot waiter utilizing: # 8211 ; Client for NetWare Networks # 8211 ; Novell Workstation Shell 3.x ( NETX ) # 8211 ; Novell Workstation Shell 4.x ( VLM ) To utilize one of the Microsoft clients, your web card must hold both an NDIS2 ( 16-bit existent manner ) *AND* an NDIS3 ( 32-bit protect manner ) driver. If your web card is a PCI, EISA, or ISAPNP card, you must run Windows over a real-mode client. To Install Windows 95 over Previous Physiques # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; To put in this concluding version of Windows 95 on web computing machines that are already running Windows 95, you have two picks: Make a clean install on each computing machine ; -or- Ascent each computing machine utilizing the undermentioned process: 1. Shut down any clients running from the waiter. 2. Windows 95 must be installed on the waiter into the same booklet that you were utilizing for old physiques. Delete everything in the shared Windows 95 booklet, and so run Netsetup.exe to put in this construct into that booklet. 3. Restart the client to a bid prompt. 4. If you are utilizing the Microsoft Client for NetWare Networks and utilize map rooted thrusts, you must get down either NETX or VLM to run Setup. 5. Map drives to the machine booklet and shared Windows 95 booklet as earlier. These must utilize the same thrust letters as used in the old physique, and map roots should be to the same booklet degree. 6. Run Setup for the new physique. Support FOR THIRD-PARTY NETWORKS ================================ To put in support for a third-party, real-mode web, you must be running the web when you run Windows 95 Setup. Windows 95 does non support installing of a real-mode web after Setup, unless you have a Windows 95-specific.inf file from your web seller. For illustration, FTP includes a Windows 95.inf in their 32-bit NFS client. Although Windows 95 supports other webs, web constituent files for webs other than Microsoft webs are non included with Windows 95. You must already have the files for the web you want to put in. LANDESK 2.0 # 8212 ; # 8212 ; # 8212 ; # 8211 ; LANDESK version 2.0 uses a TSR named Usertsr.exe that might do Windows 95 to halt reacting when you use the Microsoft IPX/SPX- compatible protocol ( Nwlink.vxd ) or file and pressman sharing for Microsoft Networks ( Vserver.vxd ) . LANDESK version 2.01 holes this job, and the spot is available on Intel # 8217 ; s BBS or from Intel merchandise support. For the BBS and merchandise support telephone Numberss, consult the certification that came with your transcript of LANDESK. SunSelect PC-NFS # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; Windows 95 supports versions 5.0 or greater of SunSelect PC-NFS. If SunSelect PC-NFS is installed utilizing an NDIS 2 LAN driver or an ODI LAN driver, so SunSelect PC-NFS can be installed as an extra 16-bit web client along with 32-bit protected-mode clients. If you are utilizing a SunSelect PC-NFS LAN Driver, Windows 95 can back up PC-NFS merely as the primary web. Additional 32-bit web suppliers are non possible in this instance. Banyan VINES # 8212 ; # 8212 ; # 8212 ; # 8212 ; If you see a message during startup that the VINES version is non the latest, edit the Vines.ini file in the Windows booklet so it contains the undermentioned lines: [ NEWREV ] dontcopy=1 vines.version=5.5x ( x ) USA ; where x=your version windows.version=3.95 If you receive the message, # 8220 ; Vines NDIS Interface mistake: 1021. See NDISBAN.DOC for an mistake description, # 8221 ; during startup, run the VINES public-service corporation PCCONFIG to alter Banyan drivers to NDIS drivers. Besides, do certainly the subdivision name matches the driver name in the Protocol.ini file. DEC Pathworks # 8212 ; # 8212 ; # 8212 ; # 8212 ; Windows 95 provides support for upgrading over bing DEC PATHWORKS V5.0, V5.0A and V5.1 constellations. This makes it possible to run your bing real-mode PATHWORKS constituents while migrating to Windows 95. However, it is strongly recommended that you upgrade to DEC # 8217 ; s PATHWORKS for Windows 95, which contains protected-mode constituents. Restrictions: PATHWORKS must be started before running Windows 95 Setup to automatically detect and upgrade PATHWORKS constituents. If PATHWORKS is non started or is non automatically detected, you will see startup mistakes when you run STARTNET. To rectify this, add the appropriate # 8220 ; PATHWORKS V5.0 and above # 8221 ; protocol, utilizing the Network icon in Control Panel. Once a system has been upgraded to Windows 95, you can non alter your PATHWORKS constellation utilizing PWSETUP. However, all bing templet constellations present when you upgrade are converted to work under Windows 95. PATHWORKS Native, DLC, X.25, and ISDN datalinks are converted to utilize an NDIS driver, if available, during the ascent. If the replacing NDIS driver is non configured right or is non runing, startup will expose an mistake and prevent burden of other PATHWORKS constituents. To rectify this, double-click the Network icon in Control Panel, and verify that the arranger driver is configured right. If any alterations are made to the arranger constellation, you must take the # 8220 ; PATHWORKS V5.0 and above # 8221 ; protocol and add it once more. PATHWORKS NetWare client licences ( CCS or FPA ) are non presently supported with Windows 95. If you are utilizing the Microsoft Client for NetWare Networks to link to PATHWORKS for OpenVMS ( NetWare ) or PATHWORKS for OSF/1 ( NetWare ) waiters, the waiter must hold PATHWORKS FPS licences. Long filenames do non work right on PATHWORKS waiters up to and including version 5.0b. You will be able to make and cancel LFN files and do and take LFN booklets, but the files and booklets will non look when you use the DIR bid, or when you open an Explorer window to the PATHWORKS waiter. PATHWORKS server version 5.00 EC01 corrects this job and is available from DEC. Artisoft LANtastic # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; The LANtastic waiter can non be run when Windows 95 is puting up. LANtastic besides can non be run in concurrence with networking support for other webs. Printing TO A NETWORK PRINTER ============================= You might hold jobs puting up a pressman that is shared by a third- party web waiter. The solution is to airt LPT1 through an MS-DOS window to the third-party portion, and so utilize the pressman apparatus for LPT1. For illustration, if a web pressman is connected to LPT1, follow these stairss: 1. At the MS-DOS prompt, type: cyberspace usage lpt1: servernamesharename ( This bid might be different on the web you are utilizing. Check the merchandise certification to happen out how to airt an LPT port. ) 2. Get down Control Panel, double-click Printers, and so double-click Add Printer. PROBLEMS PRINTING TO POSTSCRIPT PRINTERS OVER A NETWARE NETWORK ========================================= If you have jobs when publishing to a PostScript pressman over a web, ( mistake messages on the pressman ; no end product is printed ) , it might be due to falsely configured Banner Pages. To work out this job, you can make one of the followers: Disable streamer pages by taking the cheque grade from the Banner Pages box on the Capture pressman belongingss ( open the Printers booklet, chink the icon for the pressman you are utilizing, and so snap Properties on the File bill of fare ) ; -or- Ask your web decision maker to right configure streamer pages on the Netware waiter for a PostScript pressman. ISSUES AND INSTALLATION OF MS-DLC WITH WINDOWS 95 -========================= Windows 95 contains MS-DLC and support for put ining over an bing MS-DLC or IBM-DLC installing. Setup will observe DLC and do the appropriate alterations to your constellation files for these. Refer to the Windows 95 Resource Kit, Chapter 10, for a complete description of DLC support. MICROSOFT TCP/IP PROOL ========================= If Microsoft # 8217 ; s TCP/IP is the lone protocol you have loaded on your system, the IP Address will non be added during Setup. If you have a DHCP waiter, unfastened Control Panel, double-click the Network icon, and so shut it. This will update the IP Address. ( If you don # 8217 ; t cognize if you have a DHCP waiter, look into with your web decision maker, or look into if your IP reference is already entered. ) If you don # 8217 ; Ts have a DHCP waiter, get down Control Panel, double-click the Network icon, double-click TCP/IP, click the IP Address check, and so come in your IP Address. If you are non updating from a old Windows 95 installing ( you are making a # 8220 ; clean install # 8221 ; ) , to utilize DNS or LMHOSTS name declaration, do certain you have DNS enabled in the Network belongingss. To enable DNS, double-click the Network icon in Control Panel, double-click TCP/IP, click the DNS constellation check, and so snap Enable DNS. USER PROFILES OVER THE NETWORK ============================== If you are utilizing user profiles over a Windows NT or Novell NetWare web, and you include Start Menu/Programs, Network Neighborhood, and/or desktop icons in your profile, the waiter must hold long filename support to guarantee that these parts of the user profile work over the web. NETWORK BACKUP AGENTS ===================== Arcada Backup Exec Network Backup Agent # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; To utilize the Arcada Backup Exec web backup agent included in Windows 95, you must hold Arcada Backup Exec version 5.x. Cheyenne ARCserve Network Backup Agent # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8212 ; # 8211 ; To utilize the Cheyenne ARCserve web backup agent included in Windows 95, you must hold Cheyenne ARCserve version 5.01F. You might besides use earlier versions if you obtain updated NLMs from Cheyenne Software. REAL-MODE PROOLS: Warning ICONS ON YOUR NETWORK ADAPTER ========================================================== If you install a web that does non utilize protected-mode protocols, such as Novell Netware 3.x, you might see a xanthous warning icon next to your web arranger in Device Manager. You can disregard this warning ; your web is to the full functional. To take the warning icon, use the plan, Extract.exe on Setup disc 1 to pull out the file Ndis.vxd from your Windows 95 discs. Then, transcript Ndis.vxd into your WindowsSystem booklet. When you reboot your system, the xanthous warning icon will no longer appear. USING AN IBM THINKPAD WITH A DOCK II ==================================== If you enable 32-bit PCMCIA support, and your web cards do non look to work decently when inserted into the Dock II # 8217 ; s PCMCIA slots ; or, if you have an ISA web card in the Dock II that has a # 8220 ; Code 10 # 8243 ; mistake in its belongingss in Device Manager, name the IBM Help Center. They will supply you with a file to rectify this job. INTEL ETHEREXPRESS PRO /100B CARD NOT CORRECTLY DETECTED ======================================================== Windows 95 does non right detect an Intel EtherExpress Pro /100B card during Setup or hardware sensing. After Setup, an entry for # 8220 ; PCI Ethernet accountant # 8221 ; appears under Other Devices in Device Manager, which shows that the device is working decently ; nevertheless, the card doesn # 8217 ; t work. To decently put in the card, take the PCI Ethernet accountant from Device Manager, and so re-start your computing machine. The card will so be detected ; the Update Device Driver ace will look. Insert the driver disc that came with the card, and so snap Next. The ace will seek the disc and happen drivers for the Intel 82557-based PCI Ethernet. This is right. Click Finish and the card should work. Setting UP A WINS SERVER ======================== To put up a WINS waiter, carry out the undermentioned stairss: 1. In Control Panel, double-click the Network icon. 2. Click TCP/IP, and so snap Properties. 3. Snap the WINS Configuration check. 4. Make certain that both the Primary WINS Server and Secondary WINS Server boxes are filled in. If you have merely one WINS Server, you must come in the indistinguishable information in both the Primary WINS Server and Secondary WINS Server boxes. If you do non make full in both boxes, your WINS scene will be changed to Disable WINS Resolution when you restart your computing machine. INTERLNK ======== The InterLnk networking merchandise contained in MS-DOS 6.x does non map decently in MS-DOS manner if you are utilizing FAT32. Exploitation COMSPEC VARIABLES POINTING TO NETWORK COMMAND.COM FILES ============================================================= If you are on a web and are presently mapping your compspec to distant web file waiters, you may acquire # 8220 ; wrong DOS version # 8221 ; mistakes ( and an account of the version transporting with Windows 95 version 4.00.950 B being an updated ver 7.1 etc. ) . You need to map the comspec to the local transcript or to a compatible version on the web.