[Non-Touchscreen Windows Mobile Other] cellphone89:
Suncom GPRS MSN IM

Same problem here man . I'm also with Suncom using an (unlocked htc 8125 wm5)

I've been using various IM clients such as :

Agile Messenger

IM+

WLM

PocketMSN

in order to see if anything works.

All have failed through GPRS.

The only IM client that works on my HTC Wizard cingular's 8125 is Ebuddy...(java client witch IMO surely sucks )

My GPRS settings are utilizing suncom's APN witch is :mobileinternet

I'm also able to connect using wifi with all the clients but that really is just like having a motorcycle with training wheels . Just plain retarded...

I found out with wiresh@rk that I can establish a link when docked with ActiveSync as it uses the current connection in the computer to connect.

A really interesting fact is that i tried to run PocketIRC using GPRS but was also unsuccessfull to connect. This triggered me to start further research and so I did.

I d/l -vxUtil- and learned that the Wizard (phone) was succesfully retrieving names from the DNS server (66.150.38.11 is a suncom dns server ) using GPRS and converting them into IP addresses but then the oddest thing happend with the hops . it showed what I believe its a private default VPN address 10.32.51.1

1 10.32.51.1 RTT = 718 ms TTL=0

2 10.32.51.254 RTT = 1008 ms TTL =0

3 *Request time out

4 *Request time out

5 *Request time out

Trace Route Canceled

Trace Complete

Out of pure curiosity I decided to run the trace through my computer that uses a wifi connection and the output was different :

Tracing route to tcp.mws.mobile.live.com [65.55.161.252]

over a maximum of 30 hops:

1 4 ms 3 ms 3 ms 192.168.1.1

2 29 ms 29 ms * 12.192.56.33

3 134 ms 215 ms 121 ms 12.118.166.189

4 93 ms 90 ms 91 ms gbr1.ormfl.ip.att.net [12.123.32.74]

5 92 ms 95 ms 88 ms tbr1.ormfl.ip.att.net [12.122.1.70]

6 92 ms 92 ms 94 ms cr1.ormfl.ip.att.net [12.122.21.33]

7 88 ms 93 ms 95 ms cr2.attga.ip.att.net [12.122.31.29]

8 94 ms 94 ms 94 ms cr1.attga.ip.att.net [12.122.2.133]

9 104 ms 87 ms 94 ms cr2.wswdc.ip.att.net [12.122.1.174]

10 96 ms 96 ms 97 ms tbr2.wswdc.ip.att.net [12.122.16.118]

11 94 ms 93 ms 99 ms gar1.ascva.ip.att.net [12.122.80.197]

12 96 ms 88 ms 87 ms 12.118.44.62

13 90 ms 144 ms 92 ms ge-0-3-0-57.ash-64cb-1b.ntwk.msn.net [207.46.41.57]

14 91 ms 91 ms 92 ms ge-0-1-0-0.bl2-64c-1b.ntwk.msn.net [207.46.37.41]

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

Witch makes me believe that the route is not actually passing through from internal servers of suncom aka FILTERING. (correct me if I'm wrong gurus)

And finally the whole twist about this whole post is that if its utilized as a modem (8125) with the modem link program ... the output if you trace comes back as :

Tracing route to tcp.mws.mobile.live.com [65.55.161.252]

over a maximum of 30 hops:

1 718 ms 1175 ms 641 ms 10.32.51.1

2 720 ms 916 ms 659 ms 10.32.51.254

3 * * * Request timed out.

4 * * * Request timed out.

But I'm still able connect to MSN messenger and other Windows XP IMS

In conclusion IMO believe that Suncom is restricting access to servers like tcp.mws.mobile.live.com in order to gain revenue with Internal Packeges... I'll continue to report more information any help to solve this issue will be appreciated by many.:cool: