NWC2TIP.TXT 25Jun96 NOTE: These tips assume that you have applied NWC203, NWC204, and NWC205! General Questions ----------------- GQ1. What information does Tech Support require to troubleshoot a CLIENT problem? GA1. Send in the following files: - CONFIG.SYS - AUTOEXEC.BAT - C:\NWCLIENT\NET.CFG - C:\WINDOWS\WIN.INI - C:\WINDOWS\SYSTEM.INI Plus listings of the following directories (showing file sizes and dates): - C:\NWCLIENT - C:\WINDOWS - C:\WINDOWS\SYSTEM In addition, MSDOS 6.X includes MSD.EXE can produce files which help troubleshoot most client issues. To run MSD: 1. Type MSD at the DOS prompt 2. Press 3. Select the "Print Report" option. 4. Press the "Space Bar" to select REPORT ALL. 5. Press the Tab key until the "File" option is highlighted 6. Enter the path and file name of the file. The default path is the one you ran MSD from, and the default filename is REPORT.MSD. GQ2. What information does Tech Support require to troubleshoot a SERVER problem? GA2. Two things are particularly useful: 1. A CONSOLE.LOG | - LOAD CONLOG near the top of your AUTOEXEC.NCF (after MOUNT ALL) | - then, after your server comes up and Netware Connect has started, type UNLOAD CONLOG. This will create a CONSOLE.LOG file in the SYS:ETC directory. 2. A CONFIG.TXT A When you call Tech Support, you will be told how you can obtain the current version of CONFIG.NLM. Once you have CONFIG.NLM, at the server console, type LOAD CONFIG /DS. This will create a CONFIG.TXT under the SYS:SYSTEM directory. GQ3: After dialing into a NetWare Connect 2.0 server, the users were able to login to the Connect server, but not the other NetWare 4.1 servers on the network. Any ideas? GA3: Run DSREPAIR.NLM and verify that NDS does not have any problems. Also, if you have a Cubix box or a Compaq, it may be using an integrated NIC card, which is loading PCNTNW.LAN dated June 1995, which can cause this type of problem. Get an different version of this driver (earlier is OK) from the manufacturer. Can you RCONSOLE into other servers, after logging into the Connect server? If not, this may be an SPX problem. Apply the latest STRTLn.EXE patch to the Connect server, or increase SPX parameters on your client's NET.CFG. - Or, this could be a driver problem, download LANDRn.EXE for the latest LAN drivers. GQ4: I tried to install NetWare Connect 2.0 on a NetWare 3.11 server but it wouldn't. What versions of NetWare can I install NetWare Connect on? GA4: NetWare Connect 2.0 includes runtime versions of NetWare 3.12 and NetWare 4.1. NetWare Connect 2.0 is supported only when installed on NetWare version 3.12 or 4.1. (Some customers have reported successfully using NetWare Connect on a thoroughly patched NetWare 3.11 server but, that is not a "supported environment".) GQ5: Some applications on my file server also use BTRIEVE.NLM. What parameters should I specify for BTRIEVE? GA5. load BTRIEVE -U=1 -P=4096 -F=20 -H=60 -L=20 -C If the other application uses different values, use the highest value. NOTE: The parameters are not case sensitive. Migrate Issues -------------- Q: Do I need to de-install NetWare Connect 1.0 or 2.0 before I upgrade a server using the MIGRATE utility? A. Yes. NetWare Connect will NOT work correctly after the MIGRATE utility is used. (future documentation will include such a warning) - Under 1 scenario the symptoms are that you are unable to connect to NetWare Connect and use its services. In the NetWare Connect configuration the following entries in NWCCON will be seen upon selecting "Configure NetWare Connect", then "Services" under the "Configuration Options" menu to display the available "NetWare Connect Services": @F4010064ARAS @F4010064NCS @F4010064PPRNS ARAS NCS PPPRNS SOLUTION: If you have already run Migrate without de-installing NetWare Connect; delete the SYS: volume and reinstall both NetWare 4.1 and NetWare Connect 2.0. This is required (partially because PRODUCTS.DAT will be corrupted). ConnectView Questions --------------------- CVQ: How do I unload the BREQUEST.EXE from memory? CVA. At the DOS prompt type "BREQUTIL -STOP" Macintosh Client Issues (MAC2NCS) --------------------------------- MACQ1. When trying to enter SETUP in MAC2NCS, I receive the following error messages: "The operation could not be completed because no NWC NCS server was found. .. 233." IPXNETSTAT (utility that comes with MAC2NCS) couldn't see 394 or 591 SAPS. Also, I can't login to the NWC server from the same Mac. (even though PC's can use WIN2NCS with no problems) MACA1: The Macs are on their own Ethernet segment and the PC's are on a different Ethernet segment. On the Mac segment, AppleTalk was the only protocol bound, so no IPX/SPX traffic was passed. MAC2NCS requires IPX/SPX to operate. Bind IPX to the Mac's Ethernet segment NIC to enable IPX/SPX on that segment. MACQ2. When selecting MAC2NCS setup from within Chooser, I get the following error message: "The operation could not be completed because no NetWare Connect NCS server was found. Check your connection to the NetWare LAN, the integrity of the LAN itself and/or contact your network administrator. 233." Also, in IPXNetStat (the utility which comes with MAC2NCS, the SAP Query says that no services of type 394 were found. MACA2: Please do the following: 1. GO to Control Panel 2. Select MacIPX 3. Click on Ethernet (this will bring up a screen with frame types). 4. Ensure there is no X in the Always Auto-Configure Frame Type box 5. Select the frame type which matches the IPX Frame type on the NWC server (to find this information, type CONFIG at the NWC server's console prompt and look for the LAN protocol: IPX and see what Frame type is there, i.e. Ethernet_802.2). If this is set to the wrong frame type, the NCS saps will not be seen by the Mac. MACQ3: Redirecting a modem port using MAC2NCS on a Power Mac 7200, locks the Mac when I try to download a file. Why? MACA3: Some Power Mac 7200s were recalled by Apple, due to a faulty motherboard. Apple offers a free upgrade to the newer board if the Power Mac has a serial number in a certain range. If experiencing problems, call Apple Tech Support to find out if you have one of the bad motherboards. MACQ4: When using for dialing out with Mac2NCS, if port 1 is busy, and no other NCS port is available. MACA4: Download MAC20.HQX. MACQ5: Can I redirect ARA using Mac2NCS? MACA5: Yes, if you have applied MAC20.HQX. PPP/PPPRNS ---------- 1. Things to check when a successful PPPRNS connection results in the user not being able to access any network resources. The items marked with an Exclamation Point are the most common problems. Try those first and move on to the other issues if you are still unsuccessful. This list is not exhaustive. We will try to add new items as they become apparent to us. Issue NetWare 3.12 NetWare 4.x ----- ------------ ----------- NET.CFG SPX Connections = 60 ! ! Preferred Server = ! ! Preferred Tree = ! Name Context = "" ! Network Protocol = NDS, Bind ! Network Protocol = Bind, NDS ! NOTE: The Network Protocol statement may also specify one protocol only if the server environment is homogenous (all NetWare 3.x or all NetWare 4.x servers). CLIENT CONFIG.SYS Files = 50 (minimum) X X Buffers = 35 (minimum) X X NetWare 4.10 client loaded PRIOR to dialers? ! ! NWCCON Set Security for NWCAP only (do NOT Disable) ! ! Home Server list MUST be empty ! PPPRNS address MUST be unique ! ! Set data rate to 19200 when using AIOCOMX X X SERVER (if applicable) DIGI driver of 1.10 or newer X X NODE=0 parameter when loading DIGI driver ! ! Try modem on COM port to eliminate adapter X X Set Reply to Get Nearest Server = OFF ! ! Apply 312PT*, 312IT*, LIBUP*, LANDR* patches X Use latest version of DS (41NDS*.EXE) X Drop DCE to DTE data rate to 57600** X X Set Connect Rights Level is set correctly ! The * symbol refers to the generic name of these files. The actual file name will include a number instrad of a *. ** This process requires the modem script editor. There is one on the CDROM. (NWC20\DISK4\MODEM\WINDOWS\MDMWIN) PQ1. Is NETBIOS supported under PPP? PA1. No. NETBIOS requires a peer-to-peer layer in the protocol stack. It would require a third party driver written to NetWare Connect's PPPRNS spec. No such driver exists. A work around is to use PC Anywhere with the needed physical media and NETBIOS support and use NASI or WIN2NCS to obtain the service, make the connection via the PC Anywhere host. Other NetWare Client Issues --------------------------- Q1. When trying to use NetWare Connect and WIN2NCS (or other dialers) to dial-in and I have underscores in my container under the directory Services on the server, I am not be able to authenticate to the server. i.e. USER.MY_CONTAINER.ORGANIZATION A1. Instead of using an underscore, use a space. i.e. USER.MY CONTAINER.ORGANIZATION Q2. Can I use NetWare Client 32 for DOS/Windows with the NetWare Connect Dialer? A2. Yes, read 32DWIN.TXT (in NWC203.EXE) for instructions. Client Issues - TCP/IP, IPX/SPX, ARAS, NASI ------------------------------------------- CIQ1: When trying to dial via PPP and get both IPX and IP connections, I get an IPX connection but not a IP connection. The message said that TCP/IP had not been loaded, yet I did a MEM /C and saw that it had. I also received an error message after TCP/IP loaded: "LSL Buffer Size Too Small" I could get the IP connection if IPX was not enabled. CIA1. TCPIP.EXE (normally in the \NET\BIN directory) must be dated at least 4/30/95. If you have an older TCPIP.EXE, reinstall the NWC client. CIQ2: On a new install of NetWare Connect 2.0, ARA users cannot dial into ARAS unless the network administrator has set a remote client password for them. The same user CAN dial in via PPP using PAP security and get in without any password. CIA2. By default, the remote client password is enabled and set to No Password for PPP (PAP security only). But for ARAS, a user cannot dial in until a remote client password has been set for them. To correct this problem, at the server console load NWCCON, under security, set a remote client password for all ARA users. If you choose to use no password (not recommended), select the ARA user and press [ENTER] twice. CIQ4. Why can't I see any NASI ports when I use the DISTINGUISHED name with NASIDIAG.EXE? CIA4. One Answer For Netware 4.10 users, if you run the NASI command line option, ex. i.e. NASI /N=".JOHN.NOVELL" /P="PASSWORD" /S="SESSION1" Using NASI command line parameters: /N parameter - only put in the COMMON name, not the COMPLETE name. The COMMON name can be up to 40 characters long. i.e. NASI /N="JOHN" is valid. NASI /N=".JOHN.NOVELL" is not valid. When you specify the COMMON name in NASI /N, NASI will attach that to your NAME CONTEXT from your NET.CFG to make the COMPLETE name. *NOTE* NASI will ALWAYS look at NET.CFG, even if you do a CX to a different context after logging in. Another Answer Verify that you are not loading IPXODI with the /d parameter to disable ipx diagnostics. CIQ5: When trying to dialin via PPP, the NetWare Connect server thinks it is an ARAS connection, and the connection drops. CIA5: ARA 1.0 has the same header as a V.42 modem compression header, so a PPP client with a V.42 modem can be seen as an ARA 1.0 client. (ARA 2.0 has a differnt header) SOLUTION: Ports which are configured for ARA 2.0, only, will not have the problem. If you do, you will be able to dial in with ARA 2.0 and PPP. Any ports required for ARA 1.0 should be configured only for ARA 1.0. DOSDIAL ------- DDQ1. With a Toshiba laptop containing an OLICOM PCMCIA card. If DOSDIAL is used to dial the NetWare Connect 2.0 server and login to the network, an attempt to enter Windows results in the client station immediately returning to the DOS prompt. Why? DDA1. OLICOM driver (COCXCRD.386) is required for Windows. This driver conflicts with NCOMX. The only way we've found to resolve this problem is to use another vendor's PCMCIA modem card (such as a MEGAHERTZ or COMPAQ) instead. DDQ2. What causes the client station to not make the connection, time-out and, display the following error: "DOSDIAL (1110) : Time-out waiting for modem response" A: On the server, make sure: 1. The user's HOME SERVER LIST is empty. 2. The IPX address for NetWare Connect is unique - i.e. not the same as any card the server is bound to; or any internal IPX network number on any server. 3. REPLY TO GET NEAREST SERVER is set to ON. 4. IPXRTR.NLM is loaded. 5. The modem scripts for NetWare Connect are the most current. (the latest are always in NWCMOD.EXE) On the workstation: 1. NET.CFG should have: SPX CONNECTIONS = 60 PREFERRED SERVER = NETWORK PROTOCOL = NDS, BIND 2. CONFIG.SYS should have: FILES = 50 BUFFERS = 35 3. The DOSDIAL modem scripts should be the most current 4. DOSDIAL security should be set to NWCAP 5. Do not load both a NIC driver (i.e. NE2000.COM, 3C5X9.COM, etc.) and a NCOMX driver. DDQ3. My DOSDIAL connection drops every time I start Windows. Why? DDA3. In your windows setup, try changing your mouse driver from Logitech to Microsoft compatible. DDQ4: An attempt to connect to the Connect server appears to make a connection and then immediately disconnects with the following error: "DOSDIAL (1720) : The modems have been disconnected." DDA4: There is not a definite answer: Perhaps there is a bad or mis-configured COM port, or a hardware conflict may exist. - Try selecting another port number - Verify the COM ports configuration. - The serial port may be faulty. Client Issues - PC's and Windows -------------------------------- CQ1: When an IPX and IP connection is made in the Windows dialer, I am unable to establish an IP connection. If only IP is selected, I am able to get an IP connection until I minimize the NWC dialer window, then the connection drops. CA1: Some applications install a TCPIP.EXE on the workstation, which is not compatible with NetWare Connect and provide a path statement pointing to this "wrong" file. Check to make sure that NET/BIN has a TCPIP.EXE dated 4/30/95 and that this is the only TCPIP.EXE with a path. (you may have to reinstall NetWare Connect to straighten this out) CQ2. The remote workstation displayed the following error" "DIALER (-1114): An IPX connection was requested, but the IPXODI protocol stack was not loaded. Exit Windows and load IPXODI.COM before trying again." CA2. Verify that IPXODI.COM is loaded and can be seen in memory using the MEM /c/p command. If it's loaded, open the SYSTEM.INI file with an editor and verify that the NETWORK.DRV line is not remarked out. Win2NCS ------- WQ1. If WIN2NCS is running when a I exit Windows, the workstation hangs displaying a black screen (Black Screen of Death) and the station must be re-booted. WA1. This is caused by a load order conflict between WIN2NCS and NETDDEX.EXE. Open the WIN.INI file (in your \WINDOWS directory) and find the reference to NETDDEX.EXE (a file that Workgroups for Windows installs for its use.) Move this line so it is positioned AFTER the LOAD line for ATTNASI.EXE. WQ2. When using the Freelance mail package, which launches Terminal, to send mail files to and from recipients, and upon attaching a file and attempting to send it, Terminal locked the system. WA2. There are two possible solutions. 1. Apply the latest Win2NCS (v2.0.B in WNCS2B.EXE). 2. If you have version 1.11e of Win2NCS: under Options, "Global Mapping Options"; disable "Group assist on writes" and "Timing assist on writes". They are enabled by default.. WQ3. When loading Windows 3.1, with Berkeley Systems Afterdark 3.x screen saver, I get a "Stop Box" with the error message: "Could Not Enable NASI Redirection" Attempts to start the NASI redirector from WIN2NCS or ATTNASI fail with a similar error. WA3. Load Win2NCS BEFORE you load the screen saver by modifying your LOAD statement on the WIN.INI file and verifying that the file "\WIN2NCS\ATTNASI.EXE" is loaded before the "\afterdrk\adw30.exe.". i.e. load=nwpopup.exe C:\WIN2NCS\ATTNASI.EXE c:\afterdrk\adw30.exe WQ4. Even though SPX Connections = 60 is included in the workstation's NET.CFG, a attempt to "MAP COMMUNICATION PORTS" in WIN2NCS (any version), may result in the following error messages: OUT OF SPX CONNECTIONS, or NETWORK ERROR REPORTED. SPX IS NOT INSTALLED. PLEASE EXIT. WA4. You may have an incorrect NetWare for Windows Client installation. Install the latest 4.1 NetWare Client files *AFTER* you install Windows on your workstation. Third Party Client Issues ------------------------- TPQ1. Is it possible to call in to a ReachOut host through NetWare Connect and then have the ReachOut host dial back in order to reverse long distance charges or provide tighter security? TPA1. It is possible to use the Callback feature of ReachOut v5.0 with NetWare Connect. However, there are some caveats to doing this. In order to use Callback, the Host must either be connected directly to a physical port, or be using NASI.EXE instead of WIN2NCS. The NASI configuration of ReachOut allows for both an Inbound configuration and an Outbound configuration. When NASI.EXE is being used, the Host initializes itself based on the Inbound information. However, it will use the Outbound information when initiating the Callback. WIN2NCS does not support separate Inbound and Outbound configurations since it is simply redirecting a serial port to a given NetWare Connect port. Because of this, the Host MUST be connected directly to a physical port. The DIAL-IN port cannot be used since one cannot dial-out through the DIAL-IN virtual port. To use the DIAL-IN port and do Callback; use the Dial Back support built in to NetWare Connect. Since NetWare Connect is in direct contact with the ports, it can properly route a dial-back request so that it gets to a physical port rather than the virtual DIAL-IN port. This information relates specifically to ReachOut v5.0. Other 3rd party Remote Control applications and versions that have Callback features would have to be tested on an individual basis. Not every application supports separate Inbound and Outbound port configurations. TPQ2. If when TNVT220 loads, I type "open ", the system locks up. If this is done in a Windows DOS box, I am able to kill the window when it locks up and go on. TPA2. This happens because both TELAPI and NASI use Interrupt 6B. To avoid the problem: - pre-load TELAPI using the switch "TELAPI -nn" for "not nasi". or - load your application and set it for a com port before loading TNVT220. TPQ3 How do I setup a remote control type application with NetWare Connect? A: First meet the following requirements: - A server running NetWare with NetWare Connect and a modem attached. - A workstation connected to the LAN backbone. - A workstation with a modem that can be used to dial in. Then follow these instructions: 1. On a workstation logged in to the network run either NASI or WIN2NCS. For information on setting up either of these protocols see TID1006848. 2. Using a third party application that supports remote control, place your machine in host mode. The ports that you will select are part of the DIALIN service. 3. Choose the; - server name - service name of DIALIN - the specific name of SERVERNAME_DIALIN This will register the host with the NetWare Connect Service Selector. 4. Once the host is waiting you can use the same application on the other workstation to attach to the host. 5. When the connection has been established you will see the NetWare Connect Service Selector. This will appear on your screen as: "Welcome to NetWare Connect Service Selector 2.0.XX on Port #########" where XX is the revision of NetWare Connect that you are running and ######## is the port that you are attached to. 6. It will ask you for a user name and then will allow you to select the host that you wish to connect to. NOTES: A. The user name that you use here, is the user name that NASI was loaded with. You may also load NASI with the /PS switch or with the public session checked on the WIN2NCS screen, so that any valid NetWare username you enter, at the service selection screen, will allow you to grab that host using NASI/PS. Once a selection has been made, if NASI DIAL-IN SECURITY has been enabled, you will get a prompt for the REMOTE CLIENT PASSWORD. This is the password that is set up in the configuration of NWCCON. After the password authentication has taken place you will be connected to the host you have chosen. B. Verify that you disconnect properly from your application. Improper disconnections can cause port re-initialization problems. C. If you enter a COMMON username and can not see your host, try entering the COMPLETE name. TPQ4. I am unable to get PC Anywhere 5.0 to come up in host mode. PC Anywhere complains that it can't find the modem. It then times out and will not enter host mode. TPA4. PC Anywhere is probably not configured properly. Load PC Anywhere and create the following configuration: 1. From the PC Anywhere main menu, select "Configure..." 2. Select "System Hardware..." 3. Select "Modem" 4. Select "Device/Port:" 5. Set the device port to "NASI/NCSI" 6. Set the "Server:" option to the name of the NetWare Connect server. (Normally, this will be the first 8 characters of your file server name.) NOTE: If you changed the ALIAS SERVER NAME in NWCCON, you must specify the new ALIAS SERVER NAME. 7. Set the "Service:" option to "DIALIN", 8. Set the "Port:" option to "SERVER_NAME_DIALIN", 9. Set the "Select Later" option to "No". 10. Select the modem type as HAYES COMPATIBLE. (This is the CORRECT modem type when using the DIALIN group. TPQ5: When attempting to initialize the modem through PC Anywhere 32, an error was returned at ATB0. This was true if the command was sent through MS Terminal and NASIDIAG as well. However, using AIOTERM.NLM, the same AT command would return OK. TPA5: Evidently, PC Anywhere 32 now has a Modem Independence feature that restricts what commands can be sent to the modem. ATB0 is not a valid command under modem independence. Do not run Modem Independence unless using the "Hayes Compatible" script in PC Anywhere 32. Other scripts will have problems due to the restricted command set. Server Issues ------------- SQ1. I get "Undefined Public Symbol" errors relating to AIOMGR when attempting to load NWCCON. The server also seems to be unstable, with intermittent ABEND's. SA1. If a product like FAXServ v2.01 or ArcServ v6 is installed after NetWare Connect, they may replace NetWare Connect's AIO.NLM with a different AIO.NLM. The current proper AIO.NLM for NetWare Connect 2.0 is v6.02h, dated 7/13/95, 45,132 bytes. If the server has any other AIO.NLM, replace it with 6.02H and reload AIO.NLM. ArcServ v6 does not seem to be able to use the NetWare Connect AIO.NLM this may mean that ArcServ v6 and NetWare Connect cannot run on the same server. SQ2. With NetWare Connect 2.0 and PowerChute (American Power Conversion) installed in the server, a problem occurs when attempting to address the serial ports. SA2. PowerChute needs to own one of the server's serial ports and NetWare Connect tries to take full ownership of all ports. Configure NetWare Connect to not use the port needed by PowerChute, by doing the following from the Server Console: 1. Load NWCCON 2. From the NetWare Connect Options menu; a. Select Configure NetWare Connect b. Select Ports, (from Configuration Options menu) Port Name Description Status AIO_10000 Available AIO_11000 PowerChute 3. Write down the Port Name that is assigned to PowerChute 4. Hit the escape key twice, returning back to the NetWare Connect Options menu. 5. From the NetWare Connect Options menu, select Set Up NetWare Connect 6. From the System Setup Options menu, choose Select NetWare Connect Ports 7. From the NetWare Connect Ports menu, a. Highlight the Port that you noted from line 3 (the PowerChute port). b. Delete that port from the NetWare Connect Ports menu. 8. Hit the escape key three times and exit NWCCON Once this process is completed, PowerChute can utilize the port and Netware Connect will no longer take full ownership of it. SQ3. Do you have any examples of a properly configured NetWare 3.12 NetWare Connect's AUTOEXEC.NCF? SA3.Example of an AUTOEXEC.NCF on NetWare 3.12 Runtime server: Server Name CA-SALES ipx internal net C123AAAA set maximum packet receive buffers = 2000 mount ALL ;commands for NetWare Runtime only load NLICLEAR set reply to get nearest server = OFF ;loading console log to troubleshoot load CONLOG ;loading support NLM'S for NetWare Connect load BTRIEVE -U=1 -P=4096 -F=20 -H=60 -L=20 -C ;loading LAN Drivers load NE2OOO port=300 int=3 frame=Ethernet_802.2 name=LAN bind IPX to LAN net=ClBA2222 ;loading aio drivers load AIO load AIOCOMX int=4 port=3f8 node=1 load AIODGXI port=100 mem=d0000 name=digi01 node=0 size=8k ;loading AppleTalk on EtherTalk 2.0 networks load APPLETLK net=4409 zone={"CA-ENGR", "CA-MKTG"} load NE2000 port=300 int=3 frame=Ethernet_snap name=ESNAP bind APPLETLK to ESNAP net=1676-1676 zone={"CA-ENGR"} unload CONLOG NOTE: NLICLEAR.NLM should NOT be loaded on any server with more than two licenses. SQ4. With NetWare Connect 2.0 on a NetWare 4.1 an a WNIM+ card, we could see all of the ports but after going to extended function TTY we could send modem commands but we did not get any response from the modem. SA4. Flow Control must be set to HDW/OFF, SW/ON. If it is not, change and reinitialize the ports. SQ5. All my 24 ports have the same name, but when I looked at the ports available in NWCONN, it only showed 8 ports. SA5. Some groups may have been carried over from NetWare Connect 1.0 (when you upgraded) such as the "dialin", "dialout" and "any_port" groups. To correct the problem, remove all groups, except for the "Any_Port" group, and you should see only the ports you have installed. SQ6. What AIO ports does NetWare Connect use as default? SA6. Netware Connect will use all AIO ports available, unless its told not to. This can be a problem if other NLMs also use AIO ports. For example, with the following AUTOEXEC.NCF: # Load UPS support for COM1 load AIOCOMX name=SERIALCOM1 load CPQUPS name=SERIALCOM1 # Load Lotus Notes support for COM2 load AIOCOMX name=SERIALCOM2 #load Lotus Notes load NOTESSRV # Netware Connect load AIODGXI port=220 mem=c800 size=8k NWCSTART In such a situation you would want NetWare Connect to use the Digiboard ports, and the applications to use the serial ports on the motherboard. Netware Connect will use the Digiboard ports, however, when Connect is started it takes over all the ports. Lotus Notes and the UPS would then have no ports to use and give errors. SOLUTION In NWCCON, go to Configure Netware Connect Choose the port used by the other programs and press enter Move the cursor to "Additional Parameters" and press enter Move the cursor down to "Applications allowed" Change from "Any Application" to "AIO" by; pressing insert, typing "AIO" and pressing AIO should show up instead of "ANY" Press ESC Change modem types to none Save changes Exit NWCCON NWCSTOP Reload AIO and the AIO drivers Fax --- NetWare Connect's Fax ability is severely limited. - Is some environments, fax support is not possible. - Even under optimal conditions, do not expect NetWare Connect to successfully send fax documents longer than a single page, as fax program routines for queuing subsequent pages generally cause the transmission to end.) However, NetWare Connect is able to coexist on a server with some fax products and share a communication board with them but not a port.