I remember thinking that the problem might be something with my cable modem service and whenever it changes IP addresses. Perhaps the router wasn’t automatically reconnecting for some reason? I’m good with PC hardware and software, but networking has never been my strong suit, so if anyone has any clarifications/additional info on this problem please let me (us) know.

Anyways…

So of course this morning my wife yells down to me while I was working from home (at the same desk with the @Home router) and informs me that the phone is not working. Not a big deal for us since we just use our cell phones. So this time I decide I’m going to try the old ‘ipconfig /release and renew’ trick (it’s about the only networking command I know, and seems to have solved everything over the years…). But first, I cycled the power to the router itself (not the cable modem too, like I had done in the past). No luck – still no blue light/service. So then I went into the Windows command prompt and typed:

ipconfig /release

Then, after it does its thing, I typed in:

ipconfig /renew

Bingo. A few seconds later and the blue light is back and service is restored.

In case you were wondering….yes, I am still very happy with the service. Do I like every once in a while having an outage? No. And I never would recommend this service (or any VOIP service) to anyone who doesn’t have a cell phone too. But we have to keep in mind that the Tmobile@Home service is still quite new and I’m confident they’ll get the bugs worked out, eventually. Until then, say it with me:

ipconfig /release

ipconfig /renew

Ahhh……it’s the solution to everything network related it seems! : )

Seriously though – how about a check in from everyone who follows this blog – do you regret your decision to sign up for the service? So far I’ve seen a lot of complaints but it’s been because of things that, quite frankly, I don’t get. Like, ‘my fax machine doesn’t work’ (why would someone in 2008 need a fax machine? Isn’t that what scanners and eFax are for?).