Archived from groups: alt.cellular.verizon (
More info?)
I'm just guessing, but the first thing I would look at is the communication
settings (like data bits, stop bits, parity, data/text translation), it
almost sounds like you are translating the qnc/qnc into something else
before sending.
As for Mobile Office, no it is not required, it is just very easy, and I
usually suggest it to people that just want it to work, and don't want to
play with it. Last I looked, it was $39.95. How much money can you save
going to something else to save a few pennies (okay, $10 or so, 1000
pennies, that's a lot rather than a few), and how much aggravation does it
entail.
==========================================
Update: Just had a thought (okay, maybe a brain fart)
However, if you see "packet data", you are using the high speed 1x
connection (rather than the low speed one).
If that is working, then that is not your low speed connection, but rather
the high speed one (10 times faster than the slow one).
just for fun, try your logon as: 1X Logon Userid (phone number)@vzw3g.com
Password vzw and set your max baud rate to 230 (then 115 etc)
You may actually be able to connect at higher speeds than dial-up!
The reason I suggest the above, is that if it works for 1X, you don't want
to kill something working, call it (the DUN) something like "High Speed 1X",
and create a new one for low speed.
"Robert" <newsfeeds@cmoschip.cotse.net> wrote in message
news:40ac1b57$1_2@127.0.0.1
> You don't have to actually purchase their mobile office kit, though,
> right? I've got a synch cable and it talks to the phone just fine -
> you see "Packet Data" displayed while it's dialing. I made my own
> dun connection in XP following their directions from their site.
>
>
> "Peter Pan" <Marcs1102NOSPAM@Hotmail.com> wrote in message
> news:2h2fv0F87oqbU1@uni-berlin.de...
>> "Charles Robinson" <charlesr@visi.com> wrote in message
>> news:40abfb92$0$8691$a18e6209@newsreader.visi.com
>>> Peter Pan <Marcs1102NOSPAM@hotmail.com> wrote:
>>>> Sounds like you might be in an extended network area (I'm guessing
>>>> from the ati/net password you tried, never heard of qnc/qnc not
>>>> working in a verizon area).
>>>
>>> It (qnc/qnc) won't work if you're trying to connect to the 3G
>>> network. There are different initialization strings for either
>>> service. Don't know which is which, though. I just know there is
>>> a diff....
>>>
>>> -Charles
>>
>> That's incorrect. If you are in a high speed/1x/NA/Express/verizon
>> native/3G/whatever you call it area, QWK2NET will STILL work. Only
>> certain phones/software even need init strings, and Mobile office
>> (that's what I use) has two connections (one QWK2NET and the other
>> Express). As I said before, I have NEVER seen QWK2NET not working in
>> a verizon area (read the post, it breaks it into 3 areas, native
>> verizon area, extended, and roaming, the part of the post you
>> trimmed said that, but just the words verizon area refer to the
>> first of the three ((NATIVE verizon area)).
>>
>> At any rate, I think my view/typing may have added to the
>> misconception. When I type verizon area I mean the verizon NATIVE
>> area, some people view all the areas (native/extended/roaming) as
>> the verizon area. It works absolutely 100% of the time in NATIVE
>> verizon area, but is hit or miss in extended network and roaming
>> areas.
>>
>> The part you clipped, was a response to someone that was asking why
>> #777 didn't work for him, and the qnc/qnc statement was meant to
>> refer to native verizon areas, not necessarily extended or roaming.
>>
>> Just to add more confusion, consider this, you can be in a NATIVE
>> verizon area, but in a valley (or in my case I was inside a metal
>> cargo van), have a tri-mode phone, and only able to use analog for
>> voice. In that case, it (Analog) won't work for data, even if you
>> are in an area that should work.
Facebook
Twitter
Instagram