Artisoft			Technical Document


Title:		ModemShare Common Problems
Updated:	01/97
Description:	Common problems and solutions.
FileName:	mshrtrbl.txt
FaxReturn#:	4113
Pages:		6


Make sure you have applied the latest update(s) to your version of 
ModemShare.  Updates can be downloaded from the Artisoft BBS, web, and ftp 
sites in the updates file area.  

Computer locks up when you're exiting ModemShare on a LANtastic network
Outdated NetBIOS. Update your NetBIOS.  If using prior to LANtastic 7.0 in 
a DOS/Windows 3.x environment, download NTB600.EXE, extract and copy the 
ailanbio.exe to all machines.

Cannot Load MCLIENT.DLL on my Windows for Workgroups modem server
Make sure that the ModemShare client and server software is installed 
before Windows is installed and after the network software is installed. 
If you're installing your ModemShare software in your AUTOEXEC.BAT file, 
it should be installed before the WIN command and after the NET START 
command.

DOS INT 14 software doesn't connect at speeds at above 9600
INT 14 software will not connect above 9600, this is a DOS limitation.  
See if the software supports NASI as that will go above 9600.

Exception 0E called from MSHARE.VXD when booting up Windows 95
Usually caused by more than one protocol binding although this is a 
generic error, can be caused by incorrect COM or network settings as well.

Inbound services, modem server won't answer the phone
A. If using Windows 95, bring up the parameter editor, select Server 
Parameters, select Group Definitions, click on the group and verify that 
"The Lines in this Group accept Incoming Calls" box is checked
B. If using DOS or Windows 3.1, run the parameter editor, select Station 
Type of Server, Select Groups, choose your group and verify that the 
"Number of Inbound Lines" option is set and that the correct Lines are 
listed for the group.

Lockups when sending or receiving faxes
A. Increase buffer sizes on both the client and the server.  Client try 
8500.  Server try 18500.
B. If using Windows 95, go to the printers control panel, select the fax 
printer driver, select properties, details, spooling options, set to spool 
directly to printer.
C. If using external Modems, verify you are using 16550 UARTS and not 8250 
UARTS (which are not supported).
D. Check the MS Fax document from the same site you obtained this document.

Modem appears to hang in Windows 95 when attempt to use it
Start the Parameter Editor, select Client Parameters and make sure both 
the Queue Connection and Retry Connection check boxes are selected.

ModemShare COM ports show a conflict with the DMA controller and other 
devices
This is normal on Plug and Play machines.  The ports are logical and 
aren't assigned an IRQ, I/O Base, or DMA channel.  Therefore they show as 
DMA 0, which is already being used by the system

ModemShare couldn't activate all  lines.
One or more defined lines couldn't be activated. Check the IRQ and I/O 
Base of each defined line and compare them to the actual modem settings.

Monitor shows data overruns and errors when connecting and getting 
overall  poor performance.
A. Check network driver versions, update if necessary
B. Set the IRQ of the network adapter to a lower priority than the modem.  
Due to cascading IRQs on todays machines, an IRQ of 10 or 15 has a 
higher priority than IRQs 3 or 4.  IRQ's start at 2 then go to 9-15 
followed by 3-8.  This is a common issue.
C. Check network communications, verify reliable communications.

Mserver displays Initialization failed - Network Request
There are more lines defined than your license allows (i.e. two port, six 
port, etc.) Delete lines until the number of lines defined equal the 
number of lines that your license allows.

Mserver displays "Parameter file error."
There's an incorrect parameter in SERVER.CON. Use Parameter Editor 
(Paredit) to correct the error.

Network Failure
1. IPXODI.COM is outdated
	IPXODI.COM should be 10/31/94 or later.  IPX.COM should be version 
3.1 or later.
2. TSR conflict
	Boot the system with the following CONFIG.SYS entries: (along with any 
network drivers)
	Files=100  Buffers=30  Device=HIMEM.SYS 
	Load only drivers needed to load the card and the protocol.  If 
this works, start putting drivers back, until you find the conflict.
3. Network not started before starting ModemShare
	Make sure MSERVER.EXE and/or Mclient(Mlclient) are loaded after 
the network has started.  
4. Outdated NetBIOS
	Update your NetBIOS.  If using prior to LANtastic 7.0 in a 
DOS/Windows 3.x environment, download NTB600.EXE, extract and copy the 
ailanbio.exe to all machines.

No active Modem Servers found by ModemShare
1. Problem with NETWRX.DAT file (IPX network only)
	Put modem server and modem client on same segment and set them to 
a flat network.  If this works you must then manually create the 
NETWRX.DAT file.
2. Outdated IPX or Network Shell drivers
	Your IPXODI driver should be dated 10/31/94 or later.
3. Outdated NetBIOS
	Update your NetBIOS.  If using prior to LANtastic 7.0 in a 
DOS/Windows 3.x environment, download NTB600.EXE, extract and copy the 
ailanbio.exe to all machines.
4. The protocol being used by ModemShare isn't the primary protocol for 
Windows 95.
	Make sure that NetBEUI is the default protocol. This option is set in the 
Advanced tab of the Properties sheet of the NetBEUI protocol. If you 
receive this error message while using Windows 95, you may have excess or 
unneeded components in the Network section of the Windows 95 Control 
Panel. Review your list of network components and remove any that you 
won't need for your network configuration.
5. The protocol being used isn't the first protocol for Windows For 
Workgroups.
	Run Windows for Workgroups network setup from and remove the 
protocol that isn't being used. 

Port Status and Setup will redirect a COM port but can't get it to dial
1. COM port setup for the line doesn't match the setting of the modem.
	Verify the setting of the modem (I/O Base and IRQ). Run Parameter 
Editor (Paredit) and change the line setting to match the setting of the 
modem.
2. There are no modem definitions, or the modem definition needs to be 
made again after ModemShare is installed in Windows 95 only
	Click Start, Settings, Control Panel, Modems and remove the modem 
definition. You may then add a modem definition but allow Windows 95 to 
search for the ModemShare COM port.

Unable to find MCLIENT.DLL
A. Mserver or Mlclient didn't load on a DOS-based modem server. Make sure 
Mserver and Mlclient load after the network and that they're in memory 
before Windows is started.
B. Edit the MCLIENT.INI file and verify the path is correct to the DLL 
files.
C. Also in the MCLIENT.INI file, verify that CommDriver=MSCOMM.DRV and not 
a 3rd party comm driver.  The MSCOMM.DRV is the renamed COMM.DRV that is 
used by Windows.  Also check for the existence of MSCOMM.DRV.  If it 
doesn't exist, than copy the COMM.DRV to MSCOMM.DRV in the Windows\System 
directory.

Windows 95 locks up when you're attempting to use a modem and there are no 
modems available
Windows 95 is retrying the modem connection. Start Parameter Editor, 
select Client Parameters and turn on "Queue Connecting Request."



Artisoft, Inc.
2202 N. Forbes Blvd			 
Tucson, AZ  85745		
				
Internet 
  web:				http://www.artisoft.com	
  ftp:				ftp.artisoft.com
FaxReturn: 			520-884-1397
ArtiFacts bbs:			520-884-8648 (8 bits,No parity,1 
stop bit)
Sales Consultation Center:  	(800) 846-9726  
			  FAX (520) 670-7359
Customer Service:	      	(800) 846-9726
Technical Support Information:	(520) 670-7000

ARTISOFT TECHNICAL SUPPORT
Artisoft offers a wide selection of technical support options.  For
information regarding technical support services, please refer to 
our Directory of Support Services, available where you obtained 
this Technical Note.
Check Technical Support & Services on our Home Web Page, 
request FaxReturn document 4, or download the file DIRLIST.TXT).  
You can also obtain this information by calling Artisoft at (520) 670-7000.

DISCLAIMER:

THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO ARTISOFT 
AND IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER 
EXPLICIT OR IMPLIED.  ARTISOFT DISCLAIMS ALL WARRANTIES AND 
SHALL NOT BE LIABLE FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, 
INDIRECT, OR PUNITIVE DAMAGES, OR LOST PROFITS OR REVENUE, EVEN 
IF IT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.  SOME 
STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR 
CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING 
LIMITATION MAY NOT APPLY TO YOU.

Brand names, company names, and product names are trademarks of their 
respective companies.
