msmobiles.com/f

msmobiles.com_robot · Joined: 23 Mar 2004 Posts: 16777215

Is Sprint's network compromised? Are they having nationwide texting issues? More importantly, do their engineers have a clue as to what's going on?

Read more at http://www.msmobiles.com/news.php/7560.html

alcedes · Posted: Sun Aug 10, 2008 9:55 pm Post subject:

It's not specific to Sprint. I can do this with AT&T and my Tilt.

I get the feeling there is a geography factor involved. I've been in Somerset New Jersey, Dayton Ohio, and Atlanta , Georgia within a 24 hour period during which I was not able to see any other devices on the AT&T network in Ohio while I was able to see a few in New Jersey and up to 26 in Atlanta.

On the Atlanta network 15 of the devices were named HTC-8900 (AT&T's code name for the Tilt). There was a device named WINDOWSMOBILE19 and WINDOWSMOBILE28 along with some other devices that were named after people. Trying to connect to one of the devices using resco seems to invariable result in an error. Not surprised though since Windows Mobile devices typically are not acting as file hosts on networks.

Sounds like a TCP port scan should be done to see if there are any ports listening.
_________________
MCAD .Net , MCTS (Web, Windows)

alcedes · Posted: Sat Aug 16, 2008 2:49 am Post subject:

Looks like the names may be gather by sending request to IP ranges over UDP port 137. This is the port used for NetBios identification. Sending an appropriate message over this port resuls in the device responding back with its name. I don't know if one should consider that a risk or not. As mentioned before I've been observing this behaviour on an AT&T device. The only Sprint CDMA phone I have access to does not run Windows Mobile.
_________________
MCAD .Net , MCTS (Web, Windows)