|
Troubleshooting: 3Com Megahertz XJEM3336 and CCEM3336 Ethernet Modem User's Guide
Back to Contents Page
Troubleshooting: 3Com® Megahertz® XJEM3336
and CCEM3336 Ethernet•Modem User's Guide
Windows 95
| Symptom or Message |
Possible Solutions |
| Modem is recognized, but Multi-function
adapter is not listed in Device Manager. |
Go to the Windows\INF directory,
and delete the SMEG*.* files. Go into My Computer,
Control Panel, System, then Device Manager
and remove the modem definition. Then re-insert the card, and follow the
Windows 95 prompts to correctly install the card. |
| Error, Windows
95 Detected |
Do not run SETUP.EXE from the
Megahertz Installation Diskette! Reboot the computer with the Ethernet
Modem inserted in the PCMCIA slot, and follow the Windows 95 prompts to
complete the installation. |
| Card is installed, but you cannot see
anything on the Network. |
Go into Control Panel, Network
Properties, Advanced, then Connector. Verify that the
Connector Type is correct (either 10BASET or 10BASE2). |
| In the Control Panel, under System,
a yellow exclamation point appears next to the Modem or Multifunction
Adapter definition. |
Use the Device Manager to remove the PC
Card definition. Restart Windows 95 and follow the prompts to complete the
installation process. |
| PC card is not recognized as new hardware
upon insertion. |
Check the PCMCIA Socket device in Device
Manager. Right click My Computer, choose Properties and then
Device Manager. Double-click the PCMCIA Socket icon in the
Device Manager list. If there is a yellow ! mark or red X on the
device line, the socket controller is not working properly. Call the computer
manufacturer. |
|
Windows 95 does not recognize the modem.
No beeps are heard when the card is inserted into
the laptop.
Beeps may or may not be heard when the card is removed
from the slot.
|
- Make sure the card is inserted all the way in
the slot.
- If you have more than one PCMCIA slot, remove
the card and try it in the other slot.
- If no beeps are heard when the card is inserted
in the laptop, but beeps are heard when it is removed, the modem may
be defective. Call Customer Support.
|
|
The laptop locks up during the installation, upon
insertion of the card, or at some other point during the boot process.
You receive a General Protection Fault or Windows
Fatal Exception Error.
|
Remove the card and reboot the system. Once the system
is fully booted, click Start and then Run. On the run line
type SYSEDIT and click OK. Choose
the SYSTEM.INI file. Move your cursor to the last line of the [386ENH]
section. Insert a blank line and then the following line:
Emmexclude=C800-CFFF
If the memory range of C800-CFFF does not work, try
CA00-CFFF. Save the file, close the System Configuration Editor and turn
the power off. With the power off, reinsert the Ethernet•Modem. Turn
the power on and let the computer boot.
|
| Network adapter has an "!" on it in the
Device Manager. |
- Double-click Multifunction, Multifunction
Adapter, then Change Resources, and change the COM port or
IRQ.
- In the Device Manager, highlight Multifunction
Adapter and click the Remove button. BE SURE NOT TO DELETE
THE NETWORK ADAPTER! Look also under Other Devices and Modem
for references to the Megahertz card and remove them. Physically take
the card out of the computer and reboot. Insert the card after Windows
95 is booted up. Insert any required disks.
|
| Other computers on the network cannot
see my computer. |
- Go to Start, Settings, Control
Panel, then Network. Click the File and Print Sharing
button. Select File Sharing and Print Sharing (optional).
- Go to Start, Settings, Control
Panel, then Network. Select the Identification tab.
Make sure that the workgroup specified is the same as the workgroup
on your network.
|
| Cannot see other machines on the network. |
Go to Start, Settings,
Control Panel, then Network. Select the Identification
tab. Make sure the workgroup specified is the same as the workgroup on your
network. |
Windows NT
| Symptom or Message |
Possible Solutions |
| Megahertz Ethernet Modem is not recognized
|
Check the version of Windows NT you are
using. The Megahertz Ethernet Modem is compatible with NT 3.51 and 4.0 only.
Your computer's PCMCIA controller may not be recognized in Windows NT. We
recommend that you contact your computer vendor, or Microsoft Corp. for
more information. |
| The file OEMSETNT.INF
is not valid for the current configuration |
Your laptop may not have PCMCIA support enabled. To
correct this;
- Go to Main, Control Panel, Devices,
then PCMCIA.
- Change Startup to Boot.
- Save the changes and reboot the computer.
Also, your computer's PCMCIA controller may not be
recognized in Windows NT. We recommend that you contact your computer
vendor, or Microsoft Corp for more information.
|
| Error, Windows
NT Detected. |
Do not run SETUP.EXE from the Megahertz
Installation Diskette! Reboot the computer with the Ethernet•Modem
inserted in the PCMCIA slot, and follow the Windows NT configuration procedures
in either "Setup for the Microsoft Windows NT
4.0 Operating System" or "Setup for
the Microsoft Windows NT 3.51 Operating System" to complete the
installation. |
Running Setup under Windows for Workgroups
| Symptom or Message |
Possible Solutions |
| Error: Incorrect version of Card
and Socket Services detected. |
Setup requires PCMCIA standard 2.1 or
greater Card and Socket Services (C&SS). Contact your computer vendor for
an updated version of C&SS; and after installing the new C&SS, rerun SETUP.EXE.
|
| Could not find a PC Card to install.
|
No PC Card is inserted in the slot. Insert
a functioning card. |
| Could not enable the card as a LAN
or a Modem! |
The card cannot be configured. Contact
Customer Support for more information. |
| Conflict with modem configuration.
From the screen where you select Drivers, select Setup and designate new
COM port or IRQ settings. |
- Reinsert and reconfigure the modem.
- Verify that the COMPORT specified in the PROTOCOL.INI
file is the same as the COM port specified during the setup.
|
Modem Functions
| Symptom or Message |
Possible Solutions |
|
Cannot hear modem or speaker.
|
- Make sure the modem�s speaker is turned on (ATM1).
- Turn your speaker volume up (ATL3).
|
| Unable to find XJACK® connector. |
- Make sure you have the XJACK
model of PCMCIA modems.
- Push the XJACK connector in
to extend, in again to retract.
|
| XJACK connector is recessed too far back
in the PCMCIA slot when it is not extended. |
Attach the nub to the end of the XJACK
connector so the connector is accessible when not extended. |
| Modem does not dial correctly. |
- Make sure the number you dialed is correct.
- Be sure you placed a 1 before your number when
dialing long distance.
- If you are required to dial a prefix such as 9,
make sure you dialed it first.
- See the dialing instructions in "Using
Your Modem."
- The other line could be busy or not answering.
Make sure it is available to answer before calling
- If you are dialing internationally, your modem
may not recognize the dial tone. Try the command ATX3DT and the telephone
number.
- If you have Call Waiting, disable it (usually
*70).
- Verify that the modem's cable connections are
secure. The connection to the phone line could be incomplete, or the
phone cable might need to be replaced.
- Verify no other phone extension has been picked
up on the same line.
- Verify that you are using a standard analog telephone
line. You might receive an error if you are trying to connect to a digital
phone system or a Public Branch Exchange (PBX).
- Make sure the phone line is in working order by
connecting a standard telephone to that line and dialing a working number.
|
| Modem will not fax. |
- Try selecting a different fax class in your communications
software.
- Make sure that you do not have another communications
software package open.
- Try changing the flow control. You should usually
use RTS/CTS (hardware) flow control for fax class 1, and XON/XOFF (software)
flow control for fax class 2.
|
| Modem will not connect. |
- Try disabling error correction and data compression.
- If you have trouble communicating with one specific
modem, the problem may be with the other modem.
|
| Modem connects, but characters are garbled. |
- Try disabling error correction and data compression.
- If you have trouble communicating with one specific
modem, the problem may be with the other modem.
- Make sure the parity, modem speed, word length,
and stop bits are set up according to specifications or try setting
your connect rate lower (see "S-Registers").
- Make sure your Terminal Emulation settings match
those of the modem you are connected to.
|
| NO DIAL TONE. |
- Check all the modem's cable connections and make
sure they are secure. The connection to the phone line could be incomplete,
or the phone cable could need to be replaced.
- Verify that the telephone line you are using is
not in use by someone else.
- Verify that you are using a standard analog telephone
line. If you are trying to connect to a digital phone system or a Public
Branch Exchange (PBX), you may receive an error message.
- Try a different phone line.
- Verify that the phone line is in working order
by connecting a standard telephone to that line and dialing a working
number.
|
| DIGITAL LINE ERROR |
You are trying to connect to a digital
phone system or a Public Branch Exchange (PBX). Change lines to connect
to a standard analog telephone line. |
| Modem clicks repeatedly, but does not
connect. |
- You are trying to connect to a digital phone system
or a Public Branch Exchange (PBX).
- Change lines to connect to a standard analog telephone
line.
- Ordinarily, you would get a DIGITAL LINE ERROR
message, but if the current is under 100mA, the modem may click repeatedly
but the message will not appear.
- The modem cable may not be seated securely. Check
both cable connections to the modem and to the phone jack or cellular
phone.
|
| Card is hot after being used. |
Because of the lack of air flow inside
a laptop computer, components get warmer than their desktop counterparts.
The typical operating temperature of Megahertz PCMCIA cards is from 0� to
70� C (32� to 158� F). The modem is designed to run at very high temperatures.
|
ODI Network Operating Systems
| Symptom or Message |
Possible Solutions |
| Server not Found |
- Verify that all cable connections to the Megahertz
Ethernet Modem are secure.
- Try specifying a different Frame type in the NET.CFG,
then reboot your laptop. The first frame specified should be your server
type (usually Ethernet_802.2 or Ethernet_802.3), followed by Ethernet_II
if you have TCP/IP support.
- Verify that the LASTDRIVE statement in your CONFIG.SYS
is one logical drive below your first network drive if you are using
NETX (usually E).
- Verify that the LASTDRIVE=Z in your CONFIG.SYS
if you are using VLMs.
|
| LSL is not loaded. |
LSL must be loaded before MHZETH (ODI).
LSL.COM should be located in the same directory as MHZETH. Drivers
must load in the following order: LSL, MHZETH, IPXODI, NETX (or VLMs). |
| The Frame type specified in the NET.CFG
file is not supported. |
Try specifying a different frame type
(listed below) in your NET.CFG: ETHERNET_802.2, ETHERNET_802.3, ETHERNET_II,
or ETHERNET_SNAP. |
| The Adapter did not initialize. MHZETH
did not load. |
This is a general error message that may be displayed
after another error.
- Try manually loading LSL, MHZETH, IPXODI and NETX
(or VLM.EXE) to see if they load.
- Try specifying a different IRQ or LAN Base Address
by rerunning SETUP.EXE
|
| The board cannot be found. MHZETH could
not find an active Card. |
Make sure the LAN I/O Address and IRQ
settings in the ENABLE.INI and the NET.CFG files match. |
| Unable to access more than one Network
drive. |
- If you are using VLMs, make sure you have the
Netware DOS Requester section specified correctly in the NET.CFG.
- Use the Megahertz Installation diskette to run
DIAGNOSE.EXE, which will give you information about your Ethernet
Modem.
|
| You receive a
Not enough memory message when logging in to the network. |
Try adding a SHELL=
COMMAND.COM /E:2048 /P statement to the CONFIG.SYS to add
more environment space. |
| Cannot register with SuperEnabler! |
Enable cannot allocate the LAN IRQ because
it is being used by some other device. Try rerunning SETUP.EXE and
specify a different IRQ. |
| Cannot find SuperEnabler that is needed
to configure LAN! |
- ENABLE.EXE, which initializes the PC Card,
was not loaded before MHZETH.COM. Rerun ENABLE.EXE. (See
DOS Enable.)
- If ENABLE.EXE is in your CONFIG.SYS
file, make sure the /o switch is removed. (See DOS
Enable.)
|
| MHZETH bank select port failed to respond.
|
The IOBASE address value in the NET.CFG
file is not available for use. Try another port address such as 300, 320,
340, 360. Be sure the same port is specified on the ENABLE.EXE line.
(See DOS Enable.) |
| MAC7: Invalid Media= parameter. |
The value for the keyword Media is not
correct in the NET.CFG. The value should be MEDIA="TENBASET" or MEDIA="AUI"
(for 10BASE2). |
| Card Services Cannot Allocate Lan Mem
Address |
- Edit the CONFIG.SYS file. Check the memory
exclusion on the EMM386.EXE line.
- Edit the NET.CFG file from the directory
where your network drivers are located. Change the mem statement to
match the EMM386.EXE line (i.e., if it was x=d000-dfff, then
it would be mem d000).
|
| Card Services Cannot Allocate Lan IRQ |
Edit the NET.CFG file from the
directory where your network drivers are located. Change the INT statement
to a different number. The most common are 5, 7, 9, 10, 11, and 15. |
| Card Services Cannot Allocate Lan IO PORT
Base Address |
Edit the NET.CFG file from the
directory where your network drivers are located. Change the PORT to a different
value in the range of 200h to 3C0h in 20h increments. |
| Locking on NETX.EXE or VLM.EXE. |
Edit the NET.CFG file and change
INT to a different value. The most common are 5, 7, 9, 10, 11, and 15. |
| Bank Port Select Failed To Respond |
Edit the NET.CFG file from the
directory where your network drivers are located. Change the PORT to a different
value in the range of 200h to 3C0h in 20h increments. |
NDIS Network Operating Systems
| Symptom or Message |
Possible Solutions |
| MAC7: Interrupt value is out of
range. |
Try each of the following interrupt values:
3, 4, 5, 9, 10, 11, 12, or 15. |
| MAC7: I/O base parameter invalid.
|
The I/O base should be in the range of
200h to 260h or 300h to 360h in 20h increments. Common values are 300h or
320h. |
| MAC7: MaxTransmit parameter is invalid.
|
The value specified must be in the range
1 to 4. Default is 1. |
| MAC22: Driver initialization failed.
|
- Verify that you are using an available LAN Base
I/O, LAN IRQ, and Memory Address in the PROTOCOL.INI file.
- Try specifying a different IRQ on the INTERRUPT=
line.
- Try specifying a different LAN Base Address on
the IOBASE= line.
- Try specifying a different Memory Address on the
MEMWINDOW= line.
- Verify that you have the correct BINDINGS statement
specified in your PROTOCOL.INI file.
|
| MAC25: No module found with DRIVERNAME=MHZEMX$.
|
The PROTOCOL.INI file is not where
the PROTMAN.DOS driver was looking for it. Be sure the PROTOCOL.INI
file is in the directory from which PROTMAN.DOS is loaded. The PROTOCOL.INI
file should also contain the keyword DRIVERNAME="MHZEMX$". |
| OEMSETUP.INF does not contain the
correct information for this adapter. |
Remove all Network Support in Windows.
Go to C:\Windows\System and delete OEM?.INF. Restart
your computer. Completely reinstall the Ethernet•Modem card. |
Microsoft Networking - Windows
for Workgroups
| Symptom or Message |
Possible Solutions |
| Cannot see other machines on the network. |
Go to Main, Control Panel,
then Network. Make sure the Workgroup you have selected matches the
workgroup you are trying to connect to on the network. |
| Other computers on the network cannot
see my computer. |
Go to Network, Network Setup,
then Sharing. Select File Sharing and Printer Sharing (optional). |
| Locks up going into Windows for Workgroups. |
- Check your available conventional memory before
going into Windows by typing MEM and
pressing <Enter> at the DOS prompt. If your Largest Executable
Program size is less than 530K, you will need to adjust your memory
settings. See the DOS user's manual.
- Edit the PROTOCOL.INI file in the Windows
directory. Change the Interrupt value to a different number. The most
common are 5, 7, 9, 10, 11, and 15.
|
| Net start reports Card
Services Cannot Allocate Lan Mem address |
Edit the CONFIG.SYS file. Check
the memory exclusion on the EMM386.EXE line. Edit the PROTOCOL.INI
file from the Windows directory. Change the MemWindow statement to match
the EMM386.EXE line (i.e., if it was x=d000-dfff, then it would be
MemWindow = 0xd000). |
| Net start reports Card
Services Cannot Allocate Lan IRQ |
Edit the PROTOCOL.INI file from
the Windows directory. Change the Interrupt value to a different number.
The most common are 5, 7, 9, 10, 11, and 15. |
| Net start reports Card
Services Cannot Allocate Lan IO PORT Base Address |
Edit the PROTOCOL.INI file from
the Windows directory. Change the IOBase to a different value in the range
of 200h to 3C0h in 20h increments. |
Please read all restrictions
and disclaimers.
Back to Contents Page
|
