Your problem is complicated in that you are using two unkonwns -
hardware and the complex Operating System access to that modem.
Simplify by breaking a problem down into parts - then solving those
parts. Otherwise the problem becomes exponentially more complex.

One simple program to do this is Hyperterminal (or any other
terminal simulation software). If using Hyperterminal, don't enter a
name for a new connection (hit cancel). Now we will dial the ISP
directly AND see what that fancy Operating System saw and did not show
you.

This connection will default to eight data bits, one stop bit, and
no parity.
Under File>Properties , find the Connect Using option and select
the modem. If modem is not listed, try the procedure below to various
serial ports (COMx:).

Now Hyperterminal's window is talking directly to the modem. Enter
AT&F , then hit enter. The modem (if listening) will respond with
OK . If every character entered is not echoed in Window, also try
entering the ATZ command. Now every time you enter AT (and
enter), then modem will put that AT on Window, and then respond with
OK on next line.

To increase the modem speaker volume, enter ATL3 (if I remember
the correct command).

Now that you are talking to the modem's computer, then modem is
ready to dial out. Enter ATDTxxxxxxx where xxxxx is the phone
number. Try dialing to another phone in the house. Also try it with
xxxxxxx as the ISP phone number. Do it to any ISP including those you
are not registered with. If modem makes a connection, the ISP will
answer and display Logon: or something equivalent.

This proves all hardware and wires are properly connected, or
identifies hardware as suspect. If necessary, do same on other
computer to see what a good machine does.

.. Move on to diagnose the Operating System settings. Without doing
this Hyperterminal test, then the problem is exponentially more
complex because even hardware integrity is unknown.

Report back since other things that appear to work may be indication
of other problems. Yes, this Hyperterminal test provides that much
additional information.

On Feb 7, 1:37 pm, Jethro <Wil...@somewhere.org> wrote:
> Actually, I had it backwards. The Conexant RS56-PCI is what I had in
> the machine that the modem diagnostic in Control Panel said it was
> working, but I could get it todialNetzero. I double-checked what I
> connected the phone lines (phone/line) to, and even though they were
> correct, I switched them anyway. Same result. Dialtoneone voice
> phone, but will notdialNetzero. The other modem I was going to try
> is a Motorola 62002-51 (possibly SM56?). I can't get the one driver I
> found on DriverGuide to work. So I am at a stalemate - at least until
> I can get my hands on another modem.