BCM V.92 Modem Init String - check this

[oldsupportguy]

All you new Dell owners (and people who are forced to support the BCM
V.92 modem)

If you can't dialup to a V.90 site, install this init string.

+MS=V90

The BCM modems fall back to v.34 and ussualy don't fall back well...

I've seen this fix:

1: Not connecting, but handshaking
2: Connecting, but not passing traffic
3: Connecting but giving a 691 DUN Error (Invalid username/password)
4: Lost Carrier disconnections
5: Less than 33.6k connection speeds

Its not going to fix everything, but this modem is less than ideal for
general use... and Dell isn't supporting them very well, the support
I've listened in on while transfering our customers there, verify
driver versions and blame the ISP. When asked about an init string
they won't offer any - even though +MS=V90 works and is tested to work
just fine.

In XP go here to enter the code:

Control Panel / (Printers and Other Hardware) Phone and Modem Options
/ Advanced

And please... PLEASE... update your modem driver. Even if you just got
your PC out of the box, chances are there's an update for this modem.

How to update your modem driver: call dell support - they know how.

[bob]

My 8250 connects to an ISP that does not support V.92 at 45.2 with no
additional modem string. On the other hand my 8100 with high end Zoom needs
that string to connect, so go figure.
Bob in CA
"oldsupportguy" <damnju...@tds.net> wrote in message
news:65f0ea28.02112...@posting.google.com...

[oldsupportguy]

Sure, that's probably true. But like anything with computers, nothing
is ever the same even when everything seems the same. There is always
ISP hardware, phoneline quality, and so many other variables that
nothing can be taken as a catch-all 100% perfect fix.

I'm a support analyst for a major reginal ISP, and after the 6th call
in a row for BCM/GTW modems I had to post my previous message. And we
use top-of-the-line hardware from a major vendor who supports us very
well. Then when the V.92 modems from Broadcom hit the market, it was
nothing but problems. The simple init string fix has worked on every
call.

Who's to say its our equipment not handeling the fallback to v.90, or
does the Broadcom modem fall back at all? It seems like it goes from
v.92 to some bastardized form of v.90 or v.34... but when it does
connect it spends so much time shifting speeds nothing ever gets out.

Ah well, just another $3 modem in a $1000 machine with beta drivers.
:-)

"bob" <mr...@sti.net> wrote in message news:<3de2...@news.sierratel.com>...