Why is everyone so against the WModem concept for TP2? - Page 7

**shaggylive** · #61 (**permalink**) 05-28-2010, 05:12 AM

Quote:

Originally Posted by wildpig

I do when I try wmodem. See if you can check out on your TP2 to see if you also have that registry entry under the WModem section DWord Value: Connected = 0.

If you can, try Wmodem on your TP2 and see if it will go thr with the connection like it used to with Mogul and TP1. As i said, I believe that this new reg value i am seeing in TP2 might have something to do with me not being able to use Wmodem since everytime I tried to delete or change "Connected = 0", it always comes back again after a reset.

Would appreciated if anyone else can verify this under their TP2. Thanks

aww, now I gotta work? lol. j/k
actually i'm not sure that reg key is a big deal. it's likely just a status flag.

I'll see if I can't look into it for ya soon, but I know if I start messin, i'll kill hours

wildpig · #62 (**permalink**) 05-28-2010, 05:24 AM

Shaggy, much appreciated your help man. I am definitely a very persistent person (as you probably already know

but my persitence can only get things so far because I don't have much in depth technical knowledge. So this thing could be something real simple that I just happen not to have been able to recognize. However, I do believe that it's not a simple matter as it looks like they did go thr great length to really try to clam down on any kind of tethering. Which of course motivated me even more as I really hate any company with any attempt to clam down on users (which is exactly why we are not using an iphone)...

I think I know that sprint and HTC knows the benefits the tether method Wmodem provide compared to ICS which is why looks like they are trying to also clam down on wmodem even though it's very obvious that only a small minority is using wmodem mostly for the benefit of vpn...

Well, I guess I will keep knockin at it....

wildpig · #63 (**permalink**) 05-29-2010, 08:51 AM

At this poirtI've tried just about everything. I know that even in 6.l, seem you can't use wmodem due to something sprint did. Gten indicate that his friend tp2u/ custom RoM 6.5.3 has wmodem working. Anyone know or Suggest a custom 6.5 RoM that let me use Wmodem? thnx

wildpig · #64 (**permalink**) 05-29-2010, 10:13 PM

Quote:

Originally Posted by niteriderxp

... That being said Bluetooth DUN should work without any additional software if the DUN NAI has been changed. It will also give you a non-NATed public IP.

... Now if your company uses IPSEC, the protocol is a bit more complex and does not like traversing NAT.

I have tried this method of BT DUN: http://forum.ppcgeeks.com/showthread...35#post1780335

you do get internet but there is still no nonNAT'ed iP. I chked after connecting and i still got an internal ip of l92.l68.*. And I think I know why. Under the HKLM/software/Widcomm/plugin/DUNServer there is a string value: "ModemInterface = ICS".

So in essence the BT DUN just use ICS so instead thr USB it's now thr BT.

Once again, I don't know if Sprint is specifically targeting nonNAT'ed ip even more intensive in their effort to clam down on tether. It seems every method to successfully tether on TP2 so far has resulted in a NAT'ed ip.

Please, if anyone here has an idea of how we can tether on TP2 w/ a nonNAT'ed ip (be it wmodem or any method) , please say it. All of us w/ IPSEC and certain other VPN really need the nonNAT'ed ip.

**razorloves** · #65 (**permalink**) 05-29-2010, 11:00 PM

i have mr.x newest rom and i installed wmodem 2.25 and whenever i open it, it turns off the data connection. I can go to comm manager and turn it back on, but regardless of what i try, i can never get the Start button to work. it's always greyed out. Any ideas?

wildpig · #66 (**permalink**) 05-29-2010, 11:18 PM

Quote:

Originally Posted by razorloves

i have mr.x newest rom and i installed wmodem 2.25 and whenever i open it, it turns off the data connection. I can go to comm manager and turn it back on, but regardless of what i try, i can never get the Start button to work. it's always greyed out. Any ideas?

when you activate wmodem, the data connection in comm mana. is supposed to be off so that it can be used by wmodem. If it was on before, it was probably becaube you used opera just right before. so once you turn off data conn in comm mana you should be able to hit the start button in wmodem. Note that not until you initiate a dial in on your PC do you supposed to see data connection activity on the phone status bar at top.

problem I have is that the dial-in never completely goes thr pass the username verify screen on the pc and stucked on this screen. It never give a box that says invalid login ever. It just plainly stuck there.. The phone no doubt does try to dial in wheh you ask it to.

**razorloves** · #67 (**permalink**) 05-29-2010, 11:49 PM

Quote:

Originally Posted by wildpig

when you activate wmodem, the data connection in comm mana. is supposed to be off so that it can be used by wmodem. If it was on before, it was probably becaube you used opera just right before. so once you turn off data conn in comm mana you should be able to hit the start button in wmodem. Note that not until you initiate a dial in on your PC do you supposed to see data connection activity on the phone status bar at top.

problem I have is that the dial-in never completely goes thr pass the username verify screen on the pc and stucked on this screen. It never give a box that says invalid login ever. It just plainly stuck there.. The phone no doubt does try to dial in wheh you ask it to.

ok..i've never used this program before. so i'm tryin to learn it. ha.

i follow what you said but i still never get the option to hit start. it's still greyed out. when i open wmodem and connect usb cable, i see Microsoft Windows Mobile Remote Adapter come up in my device manager. Is there something i'm missin here? I only need to install the wmodem 2.25 cab, right? Is there somethin else i need to do? i'm on windows 7 x64, if that matters.

wildpig · #68 (**permalink**) 05-30-2010, 12:11 AM

Quote:

Originally Posted by razorloves

ok..i've never used this program before. so i'm tryin to learn it. ha.

i follow what you said but i still never get the option to hit start. it's still greyed out. when i open wmodem and connect usb cable, i see Microsoft Windows Mobile Remote Adapter come up in my device manager. Is there something i'm missin here? I only need to install the wmodem 2.25 cab, right? Is there somethin else i need to do? i'm on windows 7 x64, if that matters.

I take that you already got the 64 bit driver for HTC Wmodem installed on your system. If not see here.... http://forum.ppcgeeks.com/showthread...er#post1701191

So with wmodem things works differently than ICS. First you activate wmodem (making sure that data connection under comm manager is off). It supposed to let you hit start. Do not connect to the computer until you hit the start button first. Once you hit start, wmodem makes your phone appears to the computer as an actual modem and not a phone when you connect to your computer subsequently. So your computer shouldn't even try to bring up activesync or anything related to activesync up when you connect your phone to the computer. When you say that "Windows Mobile Remote Adapter come up in my device manager" something is definitely not right. I don't know if Verizon has changed anything recently on their phone but the user I mentioned above apparently was able to get it on his Veri TP2 to work.

The way wmodem is definitely very different from ICS tethering. The order that you supposed to activate the wmodem program and connect to the computer is listed on the first page of the same thread that I posted above along with the resgistry changes... It seems a lot of direction, but it's not. And it's definitely worth it to get a non NAT ip

Btw, I did msg vizionforever but got no reply from him so far ;(. I am not sure how much i will be able to apply whatever on verizon phone to sprint but I am definitely interested in knowing more...

**razorloves** · #69 (**permalink**) 05-30-2010, 12:14 AM

Quote:

Originally Posted by wildpig

I take that you already got the 64 bit driver for HTC Wmodem installed on your system. If not see here.... http://forum.ppcgeeks.com/showthread...er#post1701191

So with wmodem things works differently than ICS. First you activate wmodem (making sure that data connection under comm manager is off). It supposed to let you hit start. Do not connect to the computer until you hit the start button first. Once you hit start, wmodem makes your phone appears to the computer as an actual modem and not a phone when you connect to your computer subsequently. So your computer shouldn't even try to bring up activesync or anything related to activesync up when you connect your phone to the computer. When you say that "Windows Mobile Remote Adapter come up in my device manager" something is definitely not right. I don't know if Verizon has changed anything recently on their phone but the user I mentioned above apparently was able to get it on his Veri TP2 to work.

The way wmodem is definitely very different from ICS tethering. The order that you supposed to activate the wmodem program and connect to the computer is listed on the first page of the same thread that I posted above along with the resgistry changes... It seems a lot of direction, but it's not. And it's definitely worth it to get a non NAT ip

Btw, I did msg vizionforever but got no reply from him so far ;(. I am not sure how much i will be able to apply whatever on verizon phone to sprint but I am definitely interested in knowing more...

well then it must not work with this rom. i open wmodem with the data connection off and still Start is greyed out. thanks for all the info

**razorloves** · #70 (**permalink**) 05-30-2010, 12:51 AM

so...i remembered that wmodem is included in the stock 6.5 verizon rom, so i flashed it real quick. Opened EPST and took "dun" out of the nai settings. reboot. opened wmodem, clicked on start, plugged in usb cable, on computer i dialed #777 connection with blank username and password, and boom...i was surfin. no nat ip address. that was too freakin easy.