There is alot of information on other sites about tuning and tweaks to help speed up your Evdo/1xrtt connections. While 1xrtt may recieve little to no help from them, sometimes the EVDO side gains significantly.
I dont take credit for any of the information posted below, I just put it together here for people to view.
One of the utilities you can download to adjust your settings is Dr TCP
from here on BBR. I just wouldnt recommend changing anything that you dont know about.
One of the first adjustments you can make is this,
TCP Receive Window Size = 65536
##DATA tuning, aka HA (Home AGENT)
To see/change the HA Address, you must acquire the MSL code from Sprint. If you've activated the card yourself when first purchased, the code they gave you to activate is the MSL code. Or you could call the tier 2 data group 866.818.1944 (sometimes long wait) and tell them you need to activate your card and need the Activation Code. They should give it to you with no issues. They'll ask for your ESN number written on card or the phone number of card which can be found in Device Diag in Connection Manager. They also might ask for your account password. If a rep does not head down that path, hang up and call another.
Once you have the 6-digit MSL/Activation code...
- Run Sprint Connection Manager
- Must be disconnected from EVDO (disable NDIS if using it)
- Move mouse over 'Go' button and leave pointer on top of it
- Type in caps... ##DATA
- Enter MSL code
- A screen like this should appear for Novatel cards...
For Sierra Cards-
Experiment with primary/secondary addresses below but be sure to write down the original address on the card in case you need to go back to it. Update: Or you can do an 'Update Profile' in connection manager and it will set back to defaults. The primary address is first used when connecting. If that fails, it will use the secondary.
On Vision and PowerVision phones, dial ##DATA#. You'll need the MSL code to change the HA address, which is harder to acquire for phones. For some phones, this universal code might work... 040793
Here are the addresses of Home Agents around the country. The tools used to determine the location are only about 80% accurate, so these locations may not be exact. Set the HA to one near you (but try others). If traveling, set to the region of your travels. Thanks to cyb3rshad0w for cross-checking this list...
18.104.22.168 San Jose, CA Area 1
22.214.171.124 San Jose, CA Area 1
(could be Stockton)
126.96.36.199 Anaheim, CA Area 1 (or San Jose)
188.8.131.52 San Jose, CA Area 7 (or Anaheim)
184.108.40.206 Kansas City, MO Area 2
220.127.116.11 Kansas City, MO Area 2
(could be Omaha)
18.104.22.168 Kansas City, MO Area 2
22.214.171.124 Kansas City, MO Area 2
126.96.36.199 Pennsauken, NJ Area 3
188.8.131.52 Pennsauken, NJ Area 3
184.108.40.206 New York, NY Area 3
220.127.116.11 New York, NY Area 3
18.104.22.168 Chicago, IL Area 4
22.214.171.124 Chicago, IL Area 4
126.96.36.199 Roachdale, IN Area 4
188.8.131.52 Roachdale, IN Area 4
184.108.40.206 Fort Worth, TX Area 5
220.127.116.11 Kansas City, MO Area 5 (possible DNS config issue, likely Ft. Worth)
18.104.22.168 Atlanta, GA Area 5
22.214.171.124 Atlanta, GA Area 5
(speedtest.net says in Houston)
126.96.36.199 Relay, MD Area 7
188.8.131.52 Relay, MD Area 7
(speedtest.net says in Florida)
184.108.40.206 Atlanta, GA Area 7
220.127.116.11 Atlanta, GA Area 7
This is it. There are no other home agents known.
Here is a quick way to determine your assigned 'area' w/out needing MSL code. This will at least narrow it down to two possible HAs...
DNS: area4.spcsdns.net (must be set to Indiana or Illinois)
Another way is to do a traceroute (tracert command in Windows) to some website and compare the path of IP address locations with this tool (only 80% accurate)..
To compare your speeds with different HAs...
(sprint's test site)
To check latency from command line, 'ping www.google.com' or website near you. Lower is better.
Rev0 typically does 180ms-400ms, 130ms is about the lowest.
RevA typically does 100ms-200ms, can be as low as 50-80ms if near tower with few/no obstructions.
Latency can be much higher with poor signal, thick or many walls, when below ground or if HA is set far away.
- When traveling, the HA you are assigned to may cause traffic to bounce twice across country. If you live in NYC and are assigned to a NY HA, but then travel to LA and visit a website in LA, your traffic (worst case scenario) will likely bounce from the LA tower to the NY HA to the LA website back to the NY HA to the LA tower and to your laptop. That's a lot of unnecessary hopping across country. If you have performance problems when traveling, try setting the HA to the region of your travels. Statistically speaking, if traveling often around US and visiting websites everywhere, setting the HA to one in the Midwest may be the best compromise.
- Mac/Linux and router users. You must change the HA with Connection Manager in Windows. The settings are stored in the card so when used with non-Windows, the HA setting will still work.
Warning: Use info at your own risk. Don't change other settings unless you know what you're doing.
Update: Sprint seems to have improved HA bandwidth performance issues by turning off the compression servers. The HA you point to may be a factor if you travel across country but in general, the HA is less of an issue than in the past. Latency/ping times could still be impacted, especially for RevA users. Update2: Many still see bandwidth improvements by experimenting with different HAs.
BTW: This is a CDMA thing, not a Sprint only design, so Home Agents are likely done this way for Verizon and Alltel as well. I've tried to find a way to change Verizon HAs but with no luck.--
Hn7000s Small Office plan/.74m dish & 1Watt Trans on Satmex 5 Signal: 86/Win XP Pro SP2/P4 3gig, 2Gigs Ram, Radeon X1300 500meg video