ftp://ftp.digital.com/pub/DEC/PCI/faq.txt This doument contains frequently-asked questions and answers, presented at the Fall '95 DECUS Symposium in San Francisco, CA, USA. This document is Copyright (c) Digital Equipment Corporation 1995. All rights reserved. This document is believed to be accurate as of November, 1995. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Top Questions 1 Client 5 OpenVMS(LANMAN) Server 9 OpenVMS(NETWARE) SERVER DSNLink Aricles 13 How to Get NT, WfW, or Win95 To Browse A PATHWORKS v5 Server 15 Getting Windows for Workgroups to Load PWRKS License 17 How To Integrate Windows 95 with PATHWORKS v5.x client 21 Windows 95 Fails to Print to PATHWORKS V5 or V4 Printer 23 Adding PATHWORKS Server to a Windows NT Domain 27 Can't See Files/Directories 31 Basic Redir Connects as Guest to Standalone/Compat Server 33 LICENSE - Problem Resolution Flowchart (PCRFC) FD0108 37 NETLOGON - Call Resolution Flowchart (PCRFC) FD0107 43 Unable to Start All Print Servers ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 1 The PATHWORKS Support Team's Top Client Questions Fall '95 DECUS Symposium QUESTION #1: How do I configure PATHWORKS 5.x with Windows for Workgroups V3.11 WITHOUT using the MS Network that comes with WfW? ANSWER #1: Install WfW with no network installed. Remove the IFSHLP.SYS line in config.sys. Install PATHWORKS V5.x client with the "PATHWORKS Windows Network" option. The Patworks V5.x install will modify the system.ini file and put the PATHWORKS drivers in place. QUESTION #2: How do I configure PATHWORKS 5.x with Windows for Workgroups V3.11 AND use the MS Network that comes with WfW? ANSWER #2: Install WfW with the MS Network for your network adapter card and make certain WfW starts without error. Next, run the PATHWORKS setup program (Setup from the setup disk or Pwsetup from the system file service) and choose one of the two WfW specific templates. The PATHWORKS client software must be version 5.0A or higher for this to work! QUESTION #3 How can I browse my V5 server(s) from a WfW system? ANSWER #3: (see also Page 13) You must either have an NT server in the domain, or make at least one WfW system's workgroup name equal to the V5 server's domain name, with file sharing enabled. This will become the Master Browser, which is what WfW looks to for a list of servers. QUESTION #4: Does PATHWORKS for NT V4.1B support Windows NT V3.51? ANSWER #4: As of 20 November 1995, version 4.1B, which has been shipping since the beginning of April, does. The part number is QA-2K5AA-H*.4.1B (*= 8 for CD-ROM, C for diskette). Also make sure you get the appropriate licenses. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 2 QUESTION #5: Why can't I connect as a specific user from my enhanced redirector, WINNT, WfW, or Win95 client to my PATHWORKS V4.x server? ANSWER #5: The PATHWORKS V4.x server is not a LAN Manager V2.2 or 3.0 server and therefore dosn't understand what an enhanced redirector client is passing. The connections will be made as the client's computername rather than the LAN Manager account that was used to login. You must either make your computer name the same as a valid VMS user name or create a VMS user name that is the same as your computer name. This only works for DECnet connections. QUESTION #6: How do I establish "LAN Manager Identity" on a V5 client? or What does NET LOGON do for me? or Why do I need SETLOGON? ANSWER #6: (see also Page 27) When using the enhanced redirector, the NET LOGIN (or NET LOGON) command establishes your LAN Manager Id regardless of the server compatibility mode setting. If you are using the basic redirector and you are not in backwards compatibility mode, the SETLOGON utility establishes your LAN Manager Id. When the server is in backwards compatibility mode, the first USE command with %VMSUSERNAME PASSWORD syntax sets the LAN Manager Id. Note that SETLOGON does not do any password verification. QUESTION #7: Autoreconnect from WfW doesn't seem to be working. ANSWER #7: There are three things you can check quickly. Delete or rename your PWUSER.INI and let it create a new one. Make sure you are using 5.1 or higher DLLs (not 5.0). Delete or rename CONNECT.DAT and let it get recreated. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 3 QUESTION #8: How can I specify which type of license my client requests (for retail clients)? ANSWER #8: (see also Page 15) Run the license requestor with the "/file:licfile.txt" switch. The "licfile.txt" file should contain the following format: LICENSEnn = XXXPWaabbbccMM.mm For example: LICENSE00 = DECPWLMDOSCC05.00 QUESTION #9: Does PATHWORKS support SLIP? Does PATHWORKS support PPP? ANSWER #9: PATHWORKS for DOS and Windows supports SLIP, just select the "Async #2" template. PATHWORKS Remote (an add-on) and NetRIDER (a standalone product) both support PPP. QUESTION #10: Since upgrading to V5.1, performance has deteriorated for DECnet and TCP/IP sessions, and I have problems with sessions getting disconnected randomly, problems copying large files, etc. ANSWER #10: There were problems with the original code that was designed to allow the enhanced redirector to be partially loaded into EMS. These have been fixed with the latest client patch kit, PWV51E03. QUESTION #11: PATHWORKS for DOS and Windows V5.1 (and V6.0) says that it includes PATHWORKS Mosaic but, after running PWSetup, I can't find it on my PC. ANSWER #11: Look in the \KITS directory on the CD and/or your system serveice; that's where you'll find PWMosaic, along with ObjectBroker, InfoShelf, etc. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 4 QUESTION #12: How can I install PATHWORKS for DOS and Windows V5.1 on my Win95 client? I have an upgraded WfW to Win95 client that is running it but I cannot install it on my new Win95 client. ANSWER #12: (see also Page 17) Although an upgraded WfW to Win95 client can retain V5.1 PATHWORKS capabilities, for a new Win95 install you need to install PATHWORKS for Win95 V1.0 or later. QUESTION #13: How do I add a network printer mapping to my Windows95 client? ANSWER #13: Choose either Wizard and follow the steps to install the driver. Either: START - SETTINGS - PRINTERS - ADD PRINTER MY COMPUTER - CONTROL PANELS - PRINTERS - ADD PRINTER QUESTION #14: When using a Win95/PATHWORKS Win95 client to connect to a V5 server printer share, the printer is reported to be offline and the icon is greyed out. ANSWER #14: (see also Page 21) The PATHWORKS V5.0x server print share and the queue name need to be the same. As a workaround: START - SETTINGS - PRINTERS Select the Printer Icon and right click printer and choose PROPERTIES Select the DETAILS tab Select the ADD PORT button Choose OTHER - LOCAL PORT - OK Under "Enter Port Name" enter \\servername\sharename, OK Under "Print to the following port" select the port you just created Click OK for PROPERTIES Double-click on the printer and check under printer menu and make sure that "Work Offline" is not checked ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 5 The PATHWORKS Support Team's Top OpenVMS(LANMAN) Server Questions Fall '95 DECUS Symposium QUESTION #1: NETLOGON won't start on the server (Service Control Busy) or You were logged on, but have not been validated by a server. Therefore, you MAY not have permission to use some network resources. ANSWER #1: (see also Page 37) You may not be running NETLOGON $ NET START You may not be able to run it $ NET ACCOUNTS You may have a problem $ LMUSER -MP "" GUEST You may have a WAN issue or be TCP/IP in different subnets, etc. QUESTION #2: I get connected to my share but I don't see any files from DOS. I do from DCL. ANSWER #2: (see also Page 27) Security issue. ADMIN/PATH - VIEW - SHARED RESOURCES - PERMIT - PERM The screen is misleading. Make sure each user or group has permission letters ON THE LINE with the name of the user or group. Also, what security mode? If LANMAN and OpenVMS - check RMS permissions. Is the user getting connected as a USER or a GUEST? STATUS - SESSION - GUEST ACCOUNT (YES/NO) QUESTION #3 Unable to load multiple PAKs for PWLMDOSCC05.01 - says its already loaded. (applies to ANY PAK loaded multiple times) ANSWER #3: Using VMSLICENSE, register all PAKs. Ignore any messages about already loaded. After they are all registered, get to DCL. $ LIC UNLOAD PWLMDOSCC05.01 $ LIC LOAD PWLMDOSCC05.01 QUESTION #4: What is the current version of PATHWORKS for OpenVMS(LANMAN)? ANSWER #4: The shipping version is V5.0C. The CSC has V5.0C ECO3 available. That includes 5.0C ECO2 updates 1 and 2. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 6 QUESTION #5: After installing, I get into ADMIN/PATH - VIEW - SHARED RESOURCES - ADD SHARE - DISK/DIRECTORY. I don't see all my disks. ANSWER #5: Check the disk label name ($ SHOW DEV D). If it is greater than 10 characters, you will need to add an entry to the AUTOSHARE = line in LANMAN.INI For example ... AUTOSHARE = VAXVMSSYS061=SYS,DATADISKFOUR=G The rule is 8.3 but AUTOSHARES are hidden shares so they are 8.2$ QUESTION #6: Unable to dismount FAT volume. ANSWER #6: The dismount button is non-functional. STOP SHARING on the FAT share through VIEW - SHARED RESOURCES. If the server is older than V5.0C, the file will stay locked (next time you stop and restart the server it will unlock it - or get 5.0C ECO3). QUESTION #7: When printing from Windows to a print share on V5 that points to a MSAP$SYMBIONT controlled printer, it outputs an error "Undefined Offending Command Flushing Rest of Job" ANSWER #7: MSAF$ECO_006_012 (V1.2-1 ECO6) or 1.3 or $ CREATE CTRLD.PS <04> cvn { } bind def $ LIBRARY SYS$COMMON:[SYSLIB]MSAP$DEVCTL.TLB CTRLD.PS/INSERT/LOG $ DEFINE /FORM PS_PLAIN 1132/SETUP=CTRLD This will add the CTRLD module to the already existing PS_PLAIN form. Now restart the queues QUESTION #8: Are there any special considerations if my server has multiple network controllers? ANSWER #8: YES! There are three logicals you may want to define: $ DEFINE/SYS NETBIOS$DEVICE ESA0: ! NETBIOS(DECnet) $ DEFINE/SYS PWRK$NETBEUI_DEVICE FCA0: ! NETBEUI $ DEFINE/SYS PWRK$KNBDAEMON_DEVICE ERA0: ! TCP/IP ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 7 QUESTION #9: My PC is unable to obtain a license. ANSWER #9: (see also Page 33) On the server ... $ SHOW LIC /BR (is it even loaded?) $ MCR PWRK$LICENSE_MANAGER check under products to see if you have any free licenses available On the client ... If DECnet C:\PW> NCP NCP> DEFINE REMOTE-ADAPTER-NAME PWRK$Lserver NODE server C:\PW> PWLICLM servername If TCP/IP C:\PW> INETNAME PWRK$Lserver xx.xx.xx.xx C:\PW> PWLICLM servername QUESTION #10: How can I change my server passwords? ANSWER #10: On the server side ... ADMIN/PATH - ACCOUNTS - USERS - ZOOM (username) will set both the LAN Manager password and the hostmapped UAF account (if NOT pwrk$default or pwrk$guest). This is the way to sync out of sync passwords. From DCL, the $ NET PASSWORD utility will change both (if they are currently the same). On the client side ... LAN Manager passwords can only be changed from an enhanced redirector client (current exception - WFW - doesn't work yet). NETPASS (when issued in all CAPS from a V5.1 client) will change both LANMAN and UAF. NETD PASS will change the UAF password only. NET PASSWORD and any MS Windows buttons change LANMAN only. QUESTION #11: Whenever I print to a share on my V5 server, I get an extra blank page printed. ANSWER #11: There are several device control libraries that provide reset modules to eliminate blank pages. These are found in SYS$LIBRARY and have names like PWRK$DEVCTL_HP_LASERJET.TLB Do a $ SHOW QUEUE/FULL queuename and look for ... /LIBRARY=PWRK$DEVCTL_HP_LASERJET /SEPERATE=(RESET=(RESET)) If you do not have these qualifiers on your queue(s) you will need to add them utilizing the appropriate module found in SYSLIB. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 8 QUESTION #12: Where are the logfiles for PATHWORKS for OpenVMS(LANMAN) V5? ANSWER #12: LANMAN specific logs and dumps are in PWRK$LMLOGS Non-LANMAN specific logs dumps are in PWRK$LOGS ADMIN/ANALYZE/SINCE and NET ERROR /REVERSE are also sources for error messages. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 9 The PATHWORKS Support Team's Top OpenVMS(NETWARE) ServerQuestions Fall '95 DECUS Symposium QUESTION #1: I am getting an error when I install Pathworks Netware that it cannot be installed on a cluster? What is wrong? ANSWER #1: The version of Pathworks Netware you are installing is version 1.0. This version was not clusterable. This message has been taken out of version 1.0C. (check for open call to get exact error message) QUESTION #2: When I run PWVN$CONFIG must I shutdown my fileserver first? ANSWER #2: Yes you must first shutdown the fileserver. If you do not you will be prompted to shut it down. QUESTION #3: Can the name of my Netware File Server be the same as my VMS node name? ANSWER #3: No. They must be different. By default the name of your Pathworks Netware server is the name of the VMS node with _PNW appended to it. VMS Node Name: Homerj Netware Node Name: Homerj_pnw QUESTION #4: What is this internal network number? ANSWER #4: The internal network number is a number tht differentiates this particular node on the Pathworks Netware network from another node. It needs to be a unique number. Typically you should except the default that is given. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 10 QUESTION #5: What is this external (Network Number)? Can it be anything I want? ANSWER #5: The extenal network number is very important. It is the equivalent to a lane on 285. Each lane represents a frame type. If you have other Netware servers in your network all communicating with Ethernet_II and you are going to use frame type Ethernet_II then you must use the same external network number as the other servers are already using. If you use the same network number as a server that is running Ethernet_802.3 then you will have an accident. QUESTION #6: I am unable to see my server when I try to connect to it from my PC. Why? ANSWER #6: This is typically due to the fact that the wrong frame type is being used. If using ODI drivers check the NET.CFG file. If this user is running both Pathworks Lanman and Netware then he may have two different frame types in his NET.CFG or he/she may have specified the wrong frame type all together. The general rule is to have the netware frame type specified first then Pathworks Lanman frame specified second. If you are using NDIS then you are unable to change the default frame type in protocol.ini file. So you must do one of three things. First copy ECONFIG, a utility developed by Novell off of COMPUSERVE. ECONFIG was primarily used when Pathworks did not support Netware and ODI drivers. It allow you to change the frame type the client is using. The second option is to use a Native Netware server as a router. You can reenterantly (SP?) bind two frame types to the same network card and allow you native netware server to route the packets to the Pathworks Netware server. Server Administration Guide 4-34) The third option is to reconfigure your Pathworks Netware server to use the same frame type as the Native Netware server as well as the clients that are attaching. Pathworks Netware 1.0C ECO01 and earlier only supported Ethernet_II and Ethernet_802.2. ECO02 included support for Ethernet_802.3. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 11 QUESTION #7: When I do a SLIST from a Pathworks Netware Server I do not see any of the other Netware servers out there. What is wrong? ANSWER #7: This means that you are either using the wrong frame type or the wrong external network number. Ask the customer what frame type are the other netware systems using. If it is not the same frame type then reconfigure the Pathworks Netware system or use a Native Netware system as a router. QUESTION #8: Can I run two different license servers in the same cluster? ANSWER #8: NO. You can only have one license server running at a time QUESTION #9 Can I have more than one Pathworks Netware server in my network at one time? ANSWER #9: YES. As long as each has a unique Netware server name and internal network number. QUESTION #10: Why am I getting Intruder Detection Lockout error? ANSWER #10: This can be caused due to a number of reasons. The most common one is that client is requesting the wrong type of license. By default Pathworks Netware assumes that that a PWNWDOSCC05.00 license is what the customer has. This is not always the case. a PWNWDOSCC05.01 or a PWNWFPXXX01.00 could be what the customerhas. See troubleshooting tips on how to troubleshoot this problem. QUESTION #11: Error starting 1 out of 15 print servers? ANSWER #11: (see also Page 43) We have seen a rash of these type errors. There has been a problem with the printserver.exe, but htere are also some tuning parameters that can be adjusted that we have had success with. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 12 ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 13 [PW-VMS,PW-OSF]V5 How to Get NT, WfW, or Win95 To Browse A PATHWORKS v5 Server Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1995. All rights reserved. PRODUCT: PATHWORKS V5 for OpenVMS (LAN Manager) PATHOWRKS V5 for Digital Unix (LAN Manager) OP/SYS: OpenVMS VAX, Version 5.5-2, 6.0, 6.1 OpenVMS AXP, Version 1.5, 6.1 Digital Unix SOURCE: Digital Equipment Corporation PROBLEM: You are trying to get your NT workstation, Windows for Workgroups PC, or Windows 95 PC to browse your PATHWORKS v5 server. There are two different cases of "browsing" that you could mean, each requiring a slightly different set of circumstances. If you can do a manual connect and connect to a file share and a print share but can not see the server when looking from file manager when double-clicking on the domain name, then you need a master browser (see below; this was the original intent of this article). If you can not get a list of the shares when double-clicking on the PATHWORKS server (or specifying \\server in Win95's Start|Run... dialog box), then your PC is probably not properly licensed. Be sure either that the server has a server-based license installed (PWLMVMSCU05.00 or PWOSFCU05.00), or that the client has obtained a license successfully (using the client licensing software provided with PATHWORKS or in the client licensing patch kit (PWV5CLT_FPA_ECO012 at time of this writing - see FM0050 for latest version). SOLUTION: NT, Windows for Workgroups, and Windows 95 use a different method for browsing than does LAN Manager 2.2 (and therefore PATHWORKS). In order to have one of these systems browse a LAN Manager 2.2 domain, you must have one of these systems in the LAN Manager domain to become the "Master Browser" for that domain. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 14 The easiest way to do this is with Windows for Workgroups (WfW) or Windows95. On one PC: o Change the Workgroup name to be the same as the domain name o Enable file sharing o Restart WfW o Wait while it builds the browse list ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 15 [PW-DOS]V5 FastD: Getting Windows for Workgroups to Load PWRKS License Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1994. All rights reserved PRODUCT: PATHWORKS [TM] for DOS & Windows [TM], Version 5.0, 5.0A, 5.1 SOURCE: Digital Equipment Corporation OP/SYS: DOS, V 3.3, 4.0, 5.0, 6.0 Windows for Workgroups 3.11 BACKGROUND: FASTDETAIL FASTLANE detail articles provide detailed information on topics discussed in FASTLANE "master" articles. This article provides detailed information on a FASTLANE MASTER article: FASTM: V5 License Issues Master xFM0046 RELATED ARTICLES: See the MASTER article listed above for related articles. RESOURCES: PATHWORKS Guide to Managing PATHWORKS Licenses ============================================================================= QUESTION: --------- How can a PC running Windows for Workgroups and not PATHWORKS, execute the PATHWORKS licensing software? or How can a PC running Windows for Workgroups and PATHWORKS specify what license it should obtain? ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 16 ANSWER: ------- 1. Using another PC connected to the network, copy PWLICLM.EXE and PWLICLMT.EXE from the PWV50 service's \PCAPP\ directory to a floppy and then copy it to the PC running WFW. This example will place these files in C:\PW directory, you can put them wherever you'd like. If you don't have the PATHWORKS client software, order PWV5CLT_FPA_ECO012. 2. Create a text file in the same directory as the two executables, with a single line as described in Appendix A of the Guide to Managing PATHWORKS Licenses. (Refer to this file in the PWLICLM line as described in step 3.) For example: LICENSE00 = DECPWLMDOSCC05.00 *********************************************************************** ** The example above assumes you have PWLMDOSCC05.00 licenses loaded ** ** on your license server. If you have different license, replace ** ** 'DECPWLMDOSCC05.00' with the license type you have. ** *********************************************************************** 3. Create a batch file in the Windows for Workgroups directory called WINSTART.BAT. This file will contain two commands, the second of which points to the file created in step #2: C:\PW\PWLICLMT.EXE C:\PW\PWLICLM.EXE /FILE:\PW\LICENSE.TXT When Windows for Workgroups starts, it will run WINSTART.BAT (because it does so automatically), which will load the license responder TSR and then the license requester. Optionally, you can specify which license server to get a license from: C:\PW\PWLICLMT.EXE C:\PW\PWLICLM.EXE license_server /FILE:\PW\LICENSE.TXT Note that this only has an effect if the client has not yet obtained a license; after the license has been initially obtained, it will always verify it's license with the same server. PWLICLMT.EXE and PWLICLM.EXE can be copied from the PATHWORKS for DOS and Windows kit or from PWV5CLT_FPA_ECO012 available via DSNLink. NOTE: After using the procedure, if you get error messages indicating that the wrong license is being requested, such as this: LIC0041: Unable to obtain license for PWLMXXXFP05.00 (note that PWLMXXXFP05.00 is being requested, rather than PWLMDOSCC05.00) be sure that the LICENSE.TXT file has the correct product name. The "DEC" at the beginning is important - be sure it says DECPWLMDOSCC05.00 and not PWLMDOSCC05.00 ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 17 [PW-DOS]V5 How To Integrate Windows 95 with PATHWORKS v5.x client Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1995. All rights reserved. PRODUCT: PATHWORKS[TM] for DOS, Version 5.1, 5.0a, 5.0 OP/SYS: Microsoft[R] Windows 95[R] SOURCE: Digital Equipment Corporation ***DISCLAIMER*** For clients running Windows 95 who need DECnet connectivity, Digital PATHWORKS recommends the installation and use of the PATHWORKS for Windows 95 product. This new Digital product provides a PROTECTED mode implementation of DECnet, LAT and other protocols which were specifically written to operate in the Windows 95 environment. In addition, the product contains Win95 versions of the VT320 terminal emulator and Mosaic, an Internet Web Browser. For long-term support, the client should be looking at using PATHWORKS for Windows 95. **CAUTION** Do NOT use the installation procedure described herein if you are installing the PATHWORKS for Windows 95 product!!! On an interim basis, until the customer base can be upgraded to the PATHWORKS for Windows 95 product, Digital will be providing limited support for the real mode DECnet client v5.1, 5.0a, and 5.0 running under Windows 95. This support will only be for file and print access over DECnet. The PATHWORKS real mode DOS and Windows applications may work, but are not supported in this configuration. Digital does NOT support Windows 95 with any PATHWORKS v4.x client software. Microsoft references a "DEC PATHWORKS Windows Drivers Disk" that we can provide at the customer's request. However, Digital has not tested this configuration and will not update any components if it fails to work properly. PROBLEM: How do you install PATHWORKS v5.x DECnet with Windows 95 (WIN95)? **CAUTION** The installation procedure described below refers ONLY to the integration of REAL MODE PATHWORKS V5.x with Windows 95. The installation procedure of PATHWORKS for Windows 95 with Windows 95 is done quite differently and is NOT referenced in this article. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 18 PRE-REQUISITES: #1: The PC must be a PATHWORKS v5.x client already configured and connecting successfully to the PATHWORKS server over DECnet--including obtaining a license (if the PATHWORKS server is v5.x or higher)--using regular DOS 5.0 or higher prior to the Windows 95 upgrade. In addition, the PATHWORKS client must already be integrated with MS Windows[R] 3.1 or MS Windows for Workgroups[R] 3.11. **NOTE: A new PC with Windows 95 (with no prior version of DOS, Windows or Windows for Workgroups, and PATHWORKS) is not supported in this configuration. Obtain the PATHWORKS for Windows 95 CD-ROM. #2: The Windows 95 installation must be an UPGRADE of the previous Windows 3.1 or Windows for Workgroups 3.11 configuration (as referred to in #1). Installation into a new or separate directory will not be PATHWORKS-supported. #3: The Windows 95 upgrade media MUST be the final 950 Build on CD-ROM. The Windows 95 diskette upgrade kit (the 13 diskette kit called the "Home package" by Microsoft) does NOT contain the networking files needed for PATHWORKS. Use of any Windows 95 BETA version is unsupported by Digital. SOLUTION: #1: Be sure all PRE-REQUISITES have been met. (See above) #2: Install Windows 95 (as specified in the PRE-REQUISITES section) and configure network from Control Panel, Network for a minimum of: -Client for Microsoft Networks -Your Network Adapter (must be a Windows 95 supported adapter) -NetBEUI -PATHWORKS V5.0 and above Ethernet #3: Highlight network adapter and click Properties. If your adapter shows the options Advanced and Resources, check these to verify the hardware settings of your card, especially if using a legacy adapter. #4: Click on OK in the Network box, and SETUP will copy PATHWORKS and other networking-related files from the Windows 95 CD-ROM. **NOTE: If you are prompted for the "DEC PATHWORKS Windows Drivers Disk" this means either: a) you tried to install PATHWORKS v4.1, or b) you are attempting to use the Win95 diskette upgrade media rather than the CD-ROM. Neither of these will provide a proper upgrade of the PATHWORKS v5.x client. #5: When prompted to reboot, select NO. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 19 #6: Check your AUTOEXEC.BAT and verify the existence of the following three lines: call c:\windows\_pwmove.bat c:\windows c:\windows\net start call c:\pw\startnet.bat There can be other lines in the file, but the above three lines should be there in the order given. "c:\windows" refers to the Windows directory and "c:\pw" refers to the PATHWORKS v5.x client directory on the PC. #7: Reboot. You should now be able to connect to PATHWORKS servers via DECnet using the Map Network Drive function in Windows 95. KNOWN ISSUES: o The above instructions will allow the REAL mode version of DECnet to run in a Windows 95 environment. This means PATHWORKS components are still loading in conventional memory. If a PROTECTED mode version of DECnet is desired, install the PATHWORKS for Windows 95 client product instead. (Be sure to Remove Protocol real mode "PATHWORKS V5.0 and above Ethernet" and reboot before installing PATHWORKS for Windows 95.) o If the LAT protocol is desired, it must be included in the PATHWORKS v5.x client template before upgrading to Windows 95. o From the Start, Run box, you can enter \\server and see a directory of services on a v5.0 server. You will not be able to run executable files from here. Map the network drive and then run the program from there. o The 5.x version of the VT320 terminal emulator does not function. For a Windows 95 compliant version of the VT320 term program, install the PATHWORKS for Windows 95 product in which the new VT320 is included. o The PATHWORKS STOPNET command will not work. [TM] PATHWORKS is a trademark of Digital Equipment Corporation. [R] Microsoft, Windows, Windows 95, and Windows for Workgroups are registered trademarks of Microsoft Corporation. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 20 ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 21 [PW-W95]V5 Windows 95 Fails to Print to PATHWORKS V5 or V4 Printer Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1995. All rights reserved. PRODUCT: PATHWORKS for Windows 95, Version 1.0 OP/SYS: Microsoft Windows 95 SOURCE: Digital Equipment Corporation PROBLEM: Microsoft Windows 95 (WIN95) is installed with PATHWORKS for Windows 95. Client obtains license and can connect to file shares on PATHWORKS v5 or v4 server but cannot connect to a PATHWORKS printer share. WIN95 reports printer is offline and icon appears greyed out. SOLUTION: PATHWORKS v5.0x print share and the queue name need to be the same. For example: Print share name is \\VAX01\PRINT01 and queue name is LPS17 will not work. Print share name is \\VAX01\PRINT01 and queue name is PRINT01 will work. As a workaround, do the following in Windows 95: 1) Click Start-> Settings-> Printers 2) Select the Printer Icon and right click printer and choose Properties 3) Select the Details Tab 4) Select the ADD PORT button 5) Choose Other-> Local Port-> click [OK] 6) Under "Enter Port Name" enter \\\, click [OK] 7) Under "Print to the following port" select the port you just created 8) Click [OK] for Properties 9) Double-click on the printer and check under printer menu and make sure that "Work Offline" is not checked. Now you should be able to print to the printer. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 22 As an alternative workaround, you can create a generic queue with the name you want to share that points to your print queue by executing the following commands at the VMS prompt on your PATHWORKS v5 server: $ NET SHARE MYSHARE=MYQUEUE /PRINT $! this will create a new generic queue, MYSHARE, which points to $! the execution queue MYQUEUE, then create a share MYSHARE that $! points to the MYSHARE queue. $ NET ACCESS \PRINT\MYSHARE /ADD USERS:Y $ NET ACCESS \PRINT\MYSHARE /GRANT GUESTS:Y ANALYSIS: --------- This is a problem that is specific to the WIN95 redirector and does not effect PATHWORKS DOS clients or PATHWORKS and Windows for Workgroups clients. The WIN95 redirector tries to check the status of the printer by looking for a queue with the name of the print share on the PATHWORKS server. If it cannot find the queue, WIN95 marks the printer "offline" and will not print. For WIN95 to be able to check the status, it needs to have the Share and Queue names the same. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 23 [PW-VMS,PW-OSF] V5 Adding PATHWORKS Server to a Windows NT Domain Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1995. All rights reserved. PRODUCT: PATHWORKS for OpenVMS(LANMAN), Version 5.x PATHWORKS for OSF/1(LANMAN), Version 5.x SOURCE: Digital Equipment Corporation OVERVIEW: This article describes the steps to configure a PATHWORKS for DEC OSF/1(LANMAN) or PATHWORKS for OpenVMS(LANMAN) server into a Windows NT Domain. NOTE that this does not MERGE the existing LAN Manager accounts to the NT Domain - any accounts that exist on the PATHWORKS server will be erased and replaced with the accounts that already exist in the NT Domain. INFORMATION: On the NT Primary Domain Controller: 1. Using the User Manager for Domains, copy the Administrator account to an account called ADMIN and give this account the same password as the PATHWORKS server's ADMIN account. This may or may not be the same as the Administrator account's password. 2. Using the User Manager for Domains, enable the GUEST account and blank it's password. On the PATHWORKS server: 1. Logon as ADMIN. Enter: net logon admin password 2. Blank the GUEST account's password. Enter: net user guest "" ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 24 3. Enter net admin to connect to the NT Advanced Server. Enter the following, substituting the name of the NT Server for nt_server_name.: net admin \\nt_server_name /command 4. Create the user ID for the PATHWORKS server from within the net admin utility. Substitute the name of your PATHWORKS server for pathworks_server_name and an account password for password. Enter: net user pathworks_server_name password /add 5. Create the servers group from within the net admin utility. Enter: net group servers /add 6. Add the PATHWORKS server to the servers group from within the net admin utility. Enter the following, substituting the name of the PATHWORKS server for pathworks_server_name net group servers pathworks_server_name /add 7. Exit net admin. Enter: exit 8. From the PATHWORKS server, temporarily change the role of the PATHWORKS server to standalone. This is so that you can add the local accounts. net accounts /role:standalone 8a. Check LANMAN.INI on the PATHWORKS server - see if the DOMAIN entry (in the [workstation] section) is already the doman name you'll be joining. If not, shut down the PATHWORKS server, change the entry, then restart the PATHWORKS server. 9. Enter the same users and groups for the NT Server as you did for the PATHWORKS server. Enter the following, substituting the PATHWORKS name for pathworks_server_name, and using the same user names and passwords as you did previously. net user pathworks_server_name password /add net group servers /add net group servers pathworks_server_name /add 10. Restore the PATHWORKS server to a backup or member role. To restore the server to a backup role, enter: net accounts /role:backup To restore the server to a member role, enter: net accounts /role:member ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 25 11. Synchronize the PATHWORKS database with the the NT Server database. Enter: net accounts /sync 12. At this point, you should be able to enter this command to see the NETLOGON service started: net start You should also be able to enter this command to see the server's new role: net accounts You should also be able to enter this command to see all the users on the server: net user ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 26 ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 27 [PW-VMS]v5: Can't See Files/Directories Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1995. All rights reserved. PRODUCT: PATHWORKS v5 for OpenVMS(LANMAN) PATHWORKS v5 for Digital Unix (LANMAN) SOURCE: Digital Equipment Corporation PROBLEM: After a successful connection to a v server, the expected files and directories cannot be seen. ANALYSIS: Access to files & directories on a LAN Manager server not only depends upon OpenVMS protections (and only if the server is in a mode other than LAN Manager Only security model) but also on LAN Manager protections. Using the command $ ADMIN/PATHWORKS, go to the Session|Status menu and find entry for the PC with the access problems. Determine which username is being connected and if there is a YES or NO under the GUEST column: --------------------------------------------------------------------------- PATHWORKS V5 for OpenVMS (LAN Manager) - [\\PWRKS(ADMIN)] View Config Status Accounts Utilities Help Sessions on Server \\PWRKS Computer Name User Name Client Type Guest Acct # Open Files Idle T RELIANT ALICE DOS LM 2.1 Yes 0 05:02 DEFIANT STEVEN DOS LM 2.1 No 0 19:33 VOYAGER BOB DOS LM 2.1 No 0 10:10 OK Zoom Discnect Help --------------------------------------------------------------------------- In this example, the person using the PC "RELIANT" has logged into the network using the username "ALICE", which does not exist on this server, and is getting their access via the Guest account. The users on the ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 28 other two PC's, "DEFIANT" and "VOYAGER" both logged in with usernames that are valid on this server. These usernames are set with the SETLOGON (Digital Basic Redirector) or NET LOGON (Enhanced Redirector) command on a PATHWORKS client. Windows NT, Windows for Workgroups, and Windows 95 will pass the username/password used when a user logs onto the system. If the connection is not being made with the expected username and the Digital Basic Redirector is in use, be sure to see the note at the end of this article. Next, use View|Shared Resources... to find the share in question, select the Permit option, then the Perm option. See if the username in question (and/or the GUEST username or GUESTS* group, if there was a YES under the Guest column above) has access to the share, i.e. see which letters, representing the various permissions are INSIDE the box on the same line: --------------------------------------------------------------------------- PATHWORKS V5 for OpenVMS (LAN Manager) - [\\PWRKS(ADMIN)] View Config Status Accounts Utilities Help File Permissions for MYSHARE Default permissions: [To toggle a user's permissions, select that user in the Users With] [Permissions scroll box; press PF1/ESC, then the permission letter.] Users with permissions RWCXDAP Users without permissions GUESTS* ANN USERS* R X BOB STEVEN RWCXDAP CHARLIE DOUG Revoke RevokAll Permit PermAll OK Cancel Audit PrmtTreeRvokTree Help --------------------------------------------------------------------------- In this example, STEVEN has been granted complete access to and control over the files and directories. Other users have been given read-only access. Given the above connections, STEVEN would get full access, BOB would get read-only access (all users are part of the USERS* group), and ALICE would get no access at all, i.e. No Files Found. A personal share would normally only have access granted for one user. If you are a member of a group with read-only access but would like to have greater access to the files, be sure that you're also granted different access than the group. Access defined like this, as in the example above, would allow STEVEN full access to the share even though he is a member of the group USERS*. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 29 Basic Redirector Note --------------------- A Basic Redirector (PATHWORKS v4 or v5) client can be connected to a VMS v5 server in different ways depending upon how the connection was made and whether or not the server is in Backwards Compatability Mode (See Appendix C of the v5 Server Administrator's Guide): username seen by VMS v5 server command on PC compatability mode non-compatability mode ----------------------------- ------------------- ------------------ USE x: \\srv\svc GUEST GUEST * USE x: \\srv\svc GUEST LANManager Username USE x: \\srv\svc%VMSUsername VMSusername ** not allowed * - the SETLOGON command run at the time of STARTNET.BAT, provides a LAN Manager username ** - a LAN Manager Username is created when the Basic Redirector client connects to the v5 server running in backward compatibility, if it didn't exist before. Note that the %VMSusername syntax can only be used once per session; for more information see the following article: [PWVMS]V5 Fastd: Invalid Service or Password (Failed User Context Switch) See also: [PWDOS]V5 FastD: Basic Redir Connects as Guest to Standalone/Compat Server ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 30 ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 31 [PW-DOS]V5 FastD: Basic Redir Connects as Guest to Standalone/Compat Server Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1994. All rights reserved PRODUCT: PATHWORKS [TM] for DOS and Windows [TM] V5.0, V5.1 SOURCE: Digital Equipment Corporation This article provides detailed information for: ----------------------------------------------- FastM: V5 CLIENT ISSUES MASTER xFM0001 (Remove "x" for Search) PROBLEM: -------- A PATHWORKS 5.x Basic Redirector client will connect as GUEST to a PATHWORKS 5.0 server when the server is in BACKWARDS COMPATABILITY MODE. ALL BASIC REDIR CLIENTS ACT AS PATHWORKS 4.1 CLIENTS: 1. If the server is in LAN MANAGER ONLY security mode the only major effect is all shares the users connects to will have to have been given privs to the GUEST account. 2. Since the server is in COMPATABILITY mode the account GUEST needs privs for the existing 4.1 clients connecting. 3. Both 4.1 and 5.0 BASIC REDIR clients can connect to shares with the valid username and password by issueing the 4.1 connection method. USE ?: \\SERVERNAME\SHARENAME%VMS_USERNAME PASSWORD or USE ?: \\SERVERNAME\USERNAME%VMS_USERNAME * SOLUTION: --------- 1. As soon as the PATHWORKS 5.0 License Pak has been installed and all clients have been converted to either 5.0 basic redir or 5.0 full redir clients the server can be changed to one of the following modes: STANDALONE SERVER PRIMARY DOMAIN SERVER ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 32 BACKUP DOMAIN SERVER MEMBER SERVER 2. As soon as the server has BACKWARD COMPATABILITY removed the basic redir 5.0 clients will connect to shares and get validated by the username and password that gets passed when connecting to the share via the redirector. The SETLOGON command sets up the USERNAME/PASSWORD credentials for the BASIC REDIRECTOR. NOTE that only one "User Context Switch" can be made. When the inital connection is made (usually to the PWV50 or similar system service), it is made as GUEST. Once the user issues a USE command with the %VMS_USERNAME syntax shown above, all the connections from that PC to that server are changed to the "User Context" of the newly given username. This "User Context Switch" can have two effects: - If access has not been properly granted to the system service (share), a user who previously had access to files may loose the access they previously had. This can also been seen if a user has connections made to any other share as GUEST (print shares, for example, connected during STARTNET.BAT or AUTOEXEC.BAT) which don't have the proper access. - Once this "User Context Switch" has been made, another one cannot be made. As long as a session is open (any connections exist between the PC and the server), you're connected as that user. You can use $ADMIN/PATHWORKS Status|Session menu to see this: USE D: \\SERVER1\PWV51 I'm GUEST USE E: \\SERVER1\PCCOMMON%ME * Now I'm ME, for both my connections USE E: /D Still ME for my PWV51 connection USE E: \\SERVER1\OTHER Yup, still ME USE F: \\SERVER1\ANOTHER%YOU * This cannot be done; would be a second User Context Switch. This will result in the following error message on the PC: USE0086: Invalid Service or Password and a message in the server's log file. [TM] PATHWORKS and OpenVMS are trademarks of Digital Equipment Corporation. [TM] Windows is a trademark of Microsoft Corporation. All other trademarks and registered trademarks are the property of their respective owners. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 33 [PW-VMS]V5 FastD: LICENSE - Problem Resolution Flowchart (PCRFC) FD0108 Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1994. All rights reserved. PRODUCT: PATHWORKS for VMS, Version 5.0 SOURCE: Digital Equipment Corporation FASTLANE detail articles provide detailed information on topics discussed in FASTLANE "master" articles. This article provides detailed information for: ----------------------------------------------- FASTM: V5 License Issues Master xFM0046 RELATED ARTICLES: ----------------- See the MASTER article listed above for related articles. ============================================================================= This is a simple flowchart style question/answer sheet for license questions. Not all license questions will fall into this chart. ============================================================================= RESOLUTION: "I get an error when I boot my V5 PC saying no license server available". "Do you have any V5 servers -----V4---> ignore message--problem resolved or are they all V4?" | |-V5 | ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 34 | v On the PC, at DOS prompt, type: C:\> use /status | more What transports are loaded on the client? On Server at DCL prompt, type: $ ADMIN/CONFIG What transports are configured for the server? Is there a common transport? ----NO----> Reconfig either end for same | transport. | YES | | v On the server, at DCL prompt, type: $ SHOW LIC/BR ------> No license loaded--load appropriate What PW licenses license. do you have? | | v PWLMDOSCC05.00 is loaded with ------> Should be a number divisible by 100. how many units? Units/100 = num of clients | | v Now from DCL $ @SYS$UPDATE:PWRK$SETINI What is #1 "RUN THE ---NO--> Set it to YES and restart PWKS LICENSE SERVER" set to? (this is the problem) | YES | ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 35 | v Now from DCL type $ MCR PWRK$LICENSE_MANAGER | --error--> if cluster, try another cluster | member, otherwise, contact CSC | for support. v Go under PRODUCTS What do you see? --nothing--> add NEW product PWLMDOSCC05.00 | (this is the problem) | v PWLMDOSCC05.00 is loaded with how many available? --NONE---> Get a additional licenses. | Contact sales representative. | (this is the problem) Plenty available | | v On PC at DOS prompt type: C:\> PWLICLM --Got license--> A keyword for What happens? LICENSESERVER or | LICENSEGROUP exists in | the .TPL file on PC that Same error is incorrect. Remove | keyword(s) from the .TPL | file. v On PC at DOS prompt type: C:\> PWLICLM servername What happens? --Got license--> Problem resolved. | | Same error | v ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 36 Define remote adapter name If DECNET being used, In NCP on PC, type: NCP> DEFINE NODE xx.xxxx NAME server NCP> DEFINE REMOTE-ADAPTER-NAME PWRK$Lserver NODE server for example: NCP> DEFINE NODE 1.100 NAME VMSNET NCP> DEFINE REMOTE-ADAPTER-NAME PWRK$LVMSNET NODE VMSNET If TCP/IP is being used, At DOS prompt on PC, type: C:\> INETNAME PWRK$Lservername xx.xx.xx.xx for example C:\> INETNAME PWRK$LVMSNET 128.64.96.12 (*note* in one version of the manual, this instruction is incorrect) Now at DOS prompt, type: C:\> PWLICLM servername Did it work? ---YES---> This is a WAN. Problem | Resolved. | NO | v Contact the CSC. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 37 [PW-VMS]V5 FastD: NETLOGON - Call Resolution Flowchart (PCRFC) FD0107 Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1994, 1995. All rights reserved. PRODUCT: PATHWORKS V5 for OpenVMS (LAN Manager) SOURCE: Digital Equipment Corporation BACKGROUND: FASTLANE detail articles provide detailed information on topics discussed in FASTLANE "master" articles. This article provides detailed information on the following FASTLANE MASTER article: FastM: V5 VMS Server xFM0006 (Remove "x" for Search) RELATED ARTICLES: Fastd: NET2187: The Service Control is Busy FastD: Lan Manager NET Error Message Number Translation FastD: NETLOGON Will Not Start FASTD: VMS Server - Changing a Servers DOMAIN and ROLE Note: You may easily retrieve the MASTER article by searching on the index number above, without the x, e.g., FMnnnn. Refer to the MASTER article for a list of other related articles. ============================================================================= FLOWCHART - PATHWORKS V5 SERVER NETLOGON PROBLEMS ============================================================================= NOTE: This is a troubleshooting flowchart for a majority of server based NETLOGON problems. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 38 PROBLEM: -------- "The NETLOGON service doesn't run on my V5 server". or "On my PC, when I type my password in, it comes back and says, You were logged on, but have not been validated by a server. Therefore, you may not have permission to use some network resources." PRECURSORY CHECKS: ------------------ NOTE: A PATHWORKS V4 server does not provide the NETLOGON LAN Manager service so V5 PCs running the enhanced redirector will not be validated when running NET LOGON to a V4 server. 1) Also make sure the PATHWORKS V5 server version is current with @SYS$UPDATE:PWRK$VERSIONS. (V5.0C ECO1 will show as image version V5.0-301C) 2) Use the $ NET ERROR /REVERSE and the $ ADMIN/ANALYZE commands to troubleshoot. ANALYSIS: --------- "Do you have a V5 server enabled to be a PRIMARY DOMAIN CONTROLLER (PDC)? Type $ NET ACCOUNTS check for Server role: -----STANDALONE-----+ | | | | | A V5 server's role is STANDALONE by | default after installing. If there isn't PRIMARY a PDC already in your domain, you start | the V5 server as a PDC and start NETLOGON | with $ NET ACCOUNTS /ROLE:PRIMARY | NOTE: See the LAN Manager server role rules | at the bottom of this article. | "Is the NETLOGON Service running? $ NET START will show the running services. ---------YES--------+ | | ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 39 | | | Could be the following: | | 1) A bridge or router is not passing the | NET LOGON request to V5 server. No **NET LOGON issues a NETBIOS broadcast. | | 2) The PC and the V5 server may not be using | the same transport (NET LOGON on the PC only | works over the first transport loaded). It's | recommended to load all possible transports | on the V5 server. Check server transports | with $ ADMIN/CONFIG. Check client transports | C:\PW> USE /STATUS | MORE | If common transport(s), see note on | NETLOGON and WANs at bottom. No common = prob. | | 3) Also, try NETLOGON from DCL. | $ NET LOGON ADMIN | Type the PWRK$LANMAN:LANMAN.INI and make sure NETLOGON is on the "srvservices =" line in the [server] section. Server Role Questions | | What's the desired V5 server role? --- Standalone or Member --+ | | | | Primary or NETLOGON doesn't validate on Member and Backup doesn't run on Standalone. | Change role to PDC or BACKUP | Steps for establishing V5 server as a Primary or Backup if $ NET ACCOUNTS /ROLE: ----- GUEST account --+ fails to start NETLOGON | (See role rules at bottom.) | | $ @SYS$STARTUP:PWRK$DEFINE_COMMANDS | $ NET ACCOUNTS /ROLE:STANDALONE | $ LMUSER -MP "" GUEST | $ LMUSER -MP ADMIN | $ NET LOGON ADMIN | $ NET ACCOUNTS /ROLE:roletype | | | Command completed successfully? +------------------Yes-----------------------+ NO | | | ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 40 | | Check PWRK$LANMAN:LANMAN.INI | If this file contains a line | in the [SERVER] section like: | USERPATH = "diskdrive:[directory]" | Delete this line from the LANMAN.INI | and restart PATHWORKS. | | | $ NET START | NETLOGON should now be running No | | | Check $ NET ERROR /REVERSE Done Look for "Authentication" failures or "Unable to communicate with Domain Controller" - Authentication may mean GUEST account doesn't have null password or is expired. - Unable to communicate with Domain Controller may mean there's a possible transport or NETLOGON problem in a WAN. | | Start troubleshooting WAN issues. (see NETLOGON and WANS at bottom) If this is a Backup Domain Controller, you may have to do the above changes for the GUEST account and role setting for the PDC as well. | | | If the GUEST account had expired and caused NETLOGON to stop working, check the GUEST account on the PDC. It may have been disabled by having the "Lock out accounts" feature enabled (see note below). | | In ADMIN/PATHWORKS under ACCOUNTS, GROUPS. Is there a SERVERS group? --- NO ---+ | | | | YES $ NET ACCOUNTS /ROLE: should | automatically create the SERVERS group. | Try resetting the server's role back to | STANDALONE and then to PDC or BACKUP. | ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 41 | ZOOM on SERVERS. Is the VAX --------- No ---+ node name a member? | | | | Try resetting the role as above. YES | | Check the system time on the PDC and the backup and make sure --- Need to set time ---+ they are within 5 minutes. | | | | $ SET TIME= DONE ROLE RULES: ----------- If server is V5.0 (not V5.0A and above) and in backwards compatibility mode (Check this with $@SYS$UPDATE:PWRK$SETINI, see item #2 on the list of options), the server can only be STANDALONE (remember, NETLOGON doesn't run in STANDALONE mode). If the server is V5.0A and in backwards compatibility mode, the server can be either in PRIMARY or STANDALONE mode (but NOT Backup or Member). NETLOGON and WANs: ------------------ NETLOGON authentication is based on multicasts. It is not routable and most bridges will filter it. Consequently, NETLOGON doesn't work over WANs. Also, if you are using TCP/IP and are in different subnets, you will NOT get NETLOGON validation. How to Change Role: ------------------- You can use ADMIN/PATHWORKS and go under the ACCOUNTS menu to SECURITY SETTINGS, ROLE IN DOMAIN. You can also do it from DCL like so: $ NET LOGON ADMIN $ NET ACCOUNTS /ROLE:roletype where roletype is PRIMARY, BACKUP, MEMBER or STANDALONE. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 42 GUEST account disabled at PDC: ------------------------------ If the GUEST account password has expired and one has set "Lock out accounts" feature in ACCOUNTS -> SECURITY SETTINGS enabled, you may find that the GUEST account has been disabled at the PDC. If this is the case, you will see entries in ADMIN/ANALYZE similar to the following: Event Time: 12-DEC-1994 09:55:53.85 Node: NODE Process Id: 0000011C Event: Netlogon service failed to start Event Source: LAN Manager Server Event Class: Error Text: Netserverreqchallenge failed. GUEST account ok on Primary? Correct this by removing the disabled switch for the account on the PDC. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 43 [PW_NW-VMS] Unable to Start All Print Servers Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1995. All rights reserved. PRODUCT: PATHWORKS[TM] for OpenVMS[TM], (NetWare[TM]) V1.0C OP/SYS: OpenVMS[TM] 5.5 OpenVMS[TM] 6.0, 6.1 DOS, V 3.3, 4.0, 5.0, 6.0, 6.2 SOURCE: Digital Equipment Corporation PROBLEM: PATHWORKS NetWare will not always allow you to start all of your print servers. The error you will see in the PWVN$LOGFILES:PWVN$PSERVER.LOG is failed to start 1 out of 15 print servers check quota. SOLUTION: There are three possible causes for this problem. 1. All printserver names must be less than 15 characters long. If any exceed this limitation it will fail to start. 2. The PRCLM value is also very important. Try increasing this value. Do the following to increase this value: $show system ! Get the PID # of the NetWare PSpawn process $ show process/quota/id=(pid) ! In my case the [SYSTEM] account was the owner. $ MC AUTHROIZE MODIFY SYSTEM/PRCLM=300 $SCONSOLE ! Shutdown & Restart the print server option ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 44 3. If your print servers still do not start then do a $SHOW MEM and see what the current process slot usage is. $ show mem System Memory Resources on 14-AUG-1995 14:12:08.33 Physical Memory Usage (Pages): Total Free In Use Modified Main Memory (320.00Mb) 655360 68988 564605 21767 Virtual I/O Cache Usage (Pages): Total Free In Use Maximum Cache Memory 64603 52552 12051 71310 Slot Usage (slots): Total Free Resident Swapped Process Entry Slots 402 117 285 0 Balance Set Slots 301 18 283 0 If you do not have at least 10-20 Process Entry Slots free, then you are low. SYSGEN parameters MAXPROCESSCNT and BALSETCNT control this. Typically BALSETCNT is set to 2 less than MAXPROCESSCNT. If you set MAXPROCESSCNT to 200 BALSETCNT should be no more than 198. The value of these parameters must be changed and then reboot your system, do a $show mem and see how it affected your slot usage. If it increased your free slots a little, but not enough then increase the values of MAXPROCESSCNT and BALSETCNT and reboot again. ftp://ftp.digital.com/pub/DEC/PCI/faq.txt Page 45