I'm trying to move my T-Mobile To Go number--which was originally ported from Southwestern Bell about four years ago--to a VoIP service provider. Unfortunately, T-Mobile either doesn't know or doesn't care how to set a PIN on an account. When I submitted the port request, I gave the new provider my T-Mobile account PIN, which I thought was, let's say, 1110. Three weeks go by, and that PIN is rejected as invalid. No problem, I must have remembered it wrong. Apparently, a subscriber can call 611 from his handset and use the IVR to change the PIN. I try this. "Due to technical difficulties, I am unable to change your PIN. Please hold for a customer service representative." At this point, the CSR says that if I don't know my existing PIN, I have to go to a store.
I roll up to a T-Mobile store and ask to change said PIN. After providing ID, I tell the person a new PIN--so as not to confuse anything, I don't use what I think the old PIN was--of 4443. I watch him enter it into the computer, I e-mail this new PIN to my VoIP provider, and all is well, so I think. Just now, I receive an e-mail from my carrier: "T-mo has rejected the port today, saying 4443 is an invalid PIN." ARGH. Just for giggles, I call the IVR from not-my-prepaid-line and have it prompt me to enter my PIN. I enter 4443. "I'm sorry, that's not the same as our records." I call, again, from my prepaid line and try to change my PIN using the IVR. "Due to technical difficulties, I am unable to change your PIN. Please hold for a customer service representative." ARGH x2.
Fortunately, and in a shocking turn of events, Verizon was much smoother. My parents' phone number moved from their Verizon landline in exactly 23 days, 14 of which were taken up by the disconnect order needing to complete.
So I've figured out why pet adoption agencies have such a hard time placing pets: This form
is more complicated than a mortgage and has more conditions than a cell phone contract. It's like the volunteers want to keep all the animals they find and use the excuse of "no one was qualified to adopt!" in order to justify having 30 at a time in their houses. At least the adoption fee isn't outrageous. I've seen some that want more than $300 for a tabby cat.
In short, support your local shelter. All the pet adoption agency animals have great homes whose owners are thrilled to keep them forever.
So we moved this Monday, and I realize you're all dying to know great the new house is and all that stuff, but, frankly, who cares when I can discuss geek things?
FiOS is, as everyone likely knows, amazing. We moved a) because this townhouse has FiOS and b) the townhouse is bad ass inside. I ordered the Verizon Flex bundle which is 20/5 Internet* and the "Extreme HD" (all "cable" channels like Discovery and USA in HD, no premiums like HBO) channel lineup for $79.99/mo. Oh, and three CableCARD units at $3.99 each for the replacement flotilla of TiVo HD units. No crappy Verizon STBs here, thanks.
Short review: 20/5 Internet really is 20/5. It's OMG-fast, and low latency. About 9ms (wired) to my colo box. The TV picture is incredible and the channel lineup includes everything we want except NASA TV. ( Mad geeking cut for the rest.Collapse )
I'm still here... :)
This semester at school is almost over, giving me a couple weeks until I dive into the last Maymester, Summer and Fall semesters of my life (hopefully). Next year at this time I will be graduating with my B.Sci. in Computer Science.
We put in an offer to lease an amazing townhouse about four miles away from our current apartment and are waiting to hear back on Monday. The place has three levels, three bedrooms, four(!) bathrooms, a wide open second level ("great room"), granite countertops in the huge kitchen, plush carpet, travertine flooring and FiOS
. I have great rental and employment references, plus the unit has sat vacant for five months so I'm betting the "credit that looks like a funny car at a monster truck rally" won't be much of an issue (esp. with the deposit we're offering).
Speaking of Internet, our Internet connection
is down and has been for about 24 hours. Fortunately, tethering through AT&T 3G devices isn't difficult and hopefully our regular link comes back up by Monday. If not, we're not going to be here much longer so I'll just get an AT&T data card and share it out to our network. The other offerings here aren't worth either the contract they'd require or the hassle of getting set up.
Thu, Apr. 16th, 2009, 09:20 pm
"Only now, with the advent of Potato Day, has tyranny come to our shores." Oh, and Jon Stewart says "y'all."
Thu, Apr. 9th, 2009, 10:43 pm
Tap..tap..Is this thing on? Apparently not. :)
I have dd-wrt installed on my router. That router does NAT from 192.168.7.0/24 to a WAN IP of 192.168.100.33. Yes, I know NAT is evil, and I know double NAT is worse. However, XOHM's Ethernet home modem won't *@)$ing disable NAT and just bridge the WAN IP to the Ethernet port. Whatever. I have made my peace. I just set 192.168.100.33 to be the "DMZ" IP of the XOHM modem and this usually works well.
However, my 360 complains that NAT on my network is "strict" and I should enable UPnP. No problem; dd-wrt has this. I enable it. NAT is still "strict." Restart dd-wrt and 360; no change. UPnP discovery is working. Find ports I need to forward (3074/tcp, 3074/udp and 88/udp) to 360. Give 360 a static DHCP lease and forward said ports. Tada, 360 now says NAT is "open." Disable UPnP like paranoid-techie would want me to do. Oops, NAT is back to "strict." Reenable UPnP, life is good.
So, I learned:
* The 360 wants ports 3074/tcp, 3074/udp and 88/udp forwarded to it in Some Way.
* It also want UPnP on.
Sun, Mar. 29th, 2009, 03:37 am
Oh, and trying out wet cat food for my feline to see if it helps with his tummy. He almost took my arm off when I opened the can.
Sun, Mar. 29th, 2009, 03:16 am
"Monsters v. Aliens" is hysterical. Not the greatest, but it was worth the $ to see it at The Inwood