[jenfavre]

Hi,

I managed to successfully tether my 8320 on 2 computers, but on the last computer I get up to "Verifying username and password" when it comes back with "error 721: The remote computer did not respond."

I've used the exact same settings as on my other 2 machines, so I'm not sure how to troubleshoot. I'm using the init string +cgdcont=1,"IP","wap.voicestream.com" and I've disabled the hardware features under Standard Modem configuration. Number is set to *99# and username/password is blank.

When I query the modem, the results are:

ATQ0V1E0 - OK
AT+GMM - BlackBerry IP Modem
AT+FCLASS=? - COMMAND NOT SUPPORTED
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - COMMAND NOT SUPPORTED
AT+GCI=? - COMMAND NOT SUPPORTED
ATI1 - Research in Motion BlackBerry IP Modem
ATI2 - Research in Motion BlackBerry IP Modem
ATI3 - Research in Motion BlackBerry IP Modem
ATI4 - Research in Motion BlackBerry IP Modem
ATI5 - Research in Motion BlackBerry IP Modem
ATI6 - Research in Motion BlackBerry IP Modem
ATI7 - Research in Motion BlackBerry IP Modem

Any help with this would be appreciated!

[cky1billion]

I know that when I had tethered my 8700 via bluetooth, I would run into this sometimes. I haven't done it on my 8320, but intend to soon. What I had to do was pull the dongle, or shut the phone off and make it connect again and then it would dial out. If it didn't immediately connect the first time, it meant it was going to continue to give that error until I disconnected it.

Good Luck, I hope that helps.

Ian

[rtst31975]

Originally Posted by jenfavre

Hi,

I managed to successfully tether my 8320 on 2 computers, but on the last computer I get up to "Verifying username and password" when it comes back with "error 721: The remote computer did not respond."

I've used the exact same settings as on my other 2 machines, so I'm not sure how to troubleshoot. I'm using the init string +cgdcont=1,"IP","wap.voicestream.com" and I've disabled the hardware features under Standard Modem configuration. Number is set to *99# and username/password is blank.

When I query the modem, the results are:

ATQ0V1E0 - OK
AT+GMM - BlackBerry IP Modem
AT+FCLASS=? - COMMAND NOT SUPPORTED
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - COMMAND NOT SUPPORTED
AT+GCI=? - COMMAND NOT SUPPORTED
ATI1 - Research in Motion BlackBerry IP Modem
ATI2 - Research in Motion BlackBerry IP Modem
ATI3 - Research in Motion BlackBerry IP Modem
ATI4 - Research in Motion BlackBerry IP Modem
ATI5 - Research in Motion BlackBerry IP Modem
ATI6 - Research in Motion BlackBerry IP Modem
ATI7 - Research in Motion BlackBerry IP Modem

Any help with this would be appreciated!

I had the exact same problem and I had the exact same model query response as you. I got mine working and I discovered I had missed a few things:
-I had to go into my BB and goto options, advanced options, tcp and I had to put in wap.voicestream.com

The tricky one was this:
I labeled my dialing connection "Tmobile". I had to goto the Tmobil cion and goto it's properties. From there I went to the networking tab, highlighted the "internet protocol" option in the center and then hit the "properties" button, then click the advanced button, unlick the "use ip header compression". Then, presto!! It worked!
Good luck!

[grooveuniverse]

This may sound basic but, rather than just powering off, remove the battery, and have it recycle. This could do the trick.

The other thing you have to do if that doesent work is to call Tmobile. explain to rep that you did all basic troubleshooting so he can transfer you directly to the BB specialist. I say this because I had mine to work, then the next day it wouldnt work. After removing modem and Desktop Manager and reinstallignall over again etc., I was stumped. The guy simply reset or cleared out their server/switch side and I was back up and running. No changes to my configuration whatsoever.

[dmcgrady]

For what its worth mine was doing the same thing (721), and I noticed I had the mail icon with a red mark on it. I pulled the battery and did a hard reboot.
Red mark on email gone, Problem solved.

Maybe it wasn't logging on because it had a failed message action going on and on. This happened after I tried to send a few pics all together.

just my .02