Sprint EVDO Blocked Ports

anomaly · EVDO Newbie Joined: 29 Apr 2006 Posts: 3 Location: USA

Hey all...

I've noticed I can't run an identd server from my EVDO connection. After scanning my EVDO IP I found that (at least) the following ports are being filtered by Sprint:

Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2006-04-29 01:10 EDT
Interesting ports on x.x.spcsdns.net (x.x.x.x):
(The 1639 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
80/tcp filtered http
113/tcp filtered auth
135/tcp filtered msrpc
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
445/tcp filtered microsoft-ds
559/tcp filtered teedtap
901/tcp filtered samba-swat
1022/tcp filtered unknown
1023/tcp filtered netvenuechat
1025/tcp filtered NFS-or-IIS
1433/tcp filtered ms-sql-s
3128/tcp filtered squid-http
3306/tcp filtered mysql
4000/tcp filtered remoteanything
4899/tcp filtered radmin
5000/tcp filtered UPnP
17300/tcp filtered kuang2
27374/tcp filtered subseven

I contacted Sprint's "advanced" support for PPC-6700 users. The tech told me that this is the way the network is engineered and there's nothing that can be done about it. I just wanted to share this information and see if anyone had similar findings. It looks like I won't be using identd any time soon on my Blutooth tethered PPC-6700 Sad

_________________
PPC-6700 tethered via Bluetooth

Scott · Posted: Mon Oct 16, 2006 6:33 pm Post subject:

Additional block ports: 88, 8080 (two of the four selectable choices for the KR1 router's remote management configuration).

I have had a couple instances where a customer stated they could not get access over 1080. That port works for me though.

Scott · Posted: Tue Nov 14, 2006 1:57 pm Post subject: Another Sprint-blocked port

Port 1024 appears to be blocked as well: http://www.evdoforums.com/thread3776.html

Fizbin · EVDO Newbie Joined: 14 Aug 2007 Posts: 1

I guess we can now add port 8025 to the list of blocked ports as well.

Unfortunately, my mail server uses port 8025 for specially authenticated SMTP connections (anything sent over it gets added automatically to my whitelists - which is convenient), so this is kinda important to have.

I tested it, easily enough, by sending mail without the Sprint card - everything works; the exact same operation WITH the Sprint card providing network access, fails - so, it's a pretty obvious indication that it's Sprint doing the blocking.

The question is, how to have Sprint remove this block? I'd hate having to try to jump through hoops to get around it.