I’ve added a new article called Troubleshooting Internet Connection Problems to the Tutorials & Guides section. You’ll find it helpful for diagnosing and fixing problems when you:

• Can’t access a web site.
• Can’t get online at all.
• Can’t connect to a wireless network.

This excerpt describes a method for curing many modem- or router-based problems.

Trouble accessing the Internet

If you can’t access the Internet at all, start by checking your hardware:

1. Is your modem on? Check that all the usual lights are lit or blinking as appropriate. It helps, of course, if you know which lights are usually lit solid and which flash, so if possible position your modem (and your router) so you can see the status lights.

If the lights are not lit correctly – or if you’re not sure whether they are – reboot your modem: disconnect the power cord, wait about a minute, then reconnect the power cord and wait for the lights to come on. Then try your Internet connection again. If the lights are not lit, ensure the power cord is properly seated, then check the Ethernet or USB cable between your modem and your computer. Don’t just give the cables a look over; instead, disconnect each end of the cable and plug it back in securely. If you’re using an Ethernet cable, it should make a click when it seats properly. If you’re using a USB cable and have it connected through a hub, take the hub out of the loop: disconnect the USB cable from between the modem and the hub and connect it directly from the modem to a USB port on your computer. Also, if you’re using a USB port on the front of your computer, try disconnecting that cable and plugging it into a USB port on the back of your computer; sometimes, the ports at the front do not have sufficient power to do the job.

Tip: Prepare for trouble

Most ISP’s list their technical support phone number on their web site (although you may have to dig around to find it). Write it down now, before you have a problem with your Internet connection, and stick it somewhere handy. Also, make sure you have a copy of your router’s documentation on hand – you should find a downloadable version at the manufacturer’s site.

If the modem lights still fail to come on, give your ISP a call. There’s a good chance there’s something wrong their end.

2. Is your router on? If you use a router in conjunction with your modem, make sure the appropriate lights are lit and check its cables, too. Even if the correct lights are on, try resetting the router by disconnecting its power, waiting a minute, then reconnecting the power.

If the router’s lights fail to come on but your modem appears to be working, your router may have failed. Routers have a tendency to go bad silently and without notice. One way to check whether the router is kaput is to disconnect your computer from the router and reconnect directly through the modem. If you can successfully connect to the Internet without the router intervening, there’s a chance the router no longer works. It’s also possible that the router’s internal firewall or security settings are causing a problem, but in that case, its lights should still display as usual.

Sometimes, rebooting the modem and the router separately is not enough, but a full reboot may do the trick:

1. Switch off your computer and unplug the modem and the router.
2. Wait a minute.
3. Plug in the modem and wait for its lights to come on.
4. Plug in the router and wait for its lights to come on.
5. Switch on your computer.

I was presenting at a teleconference earlier this week for OneWorld. It’s a great organisation, and all my fellow teleconferencers were from non-profits, so I felt like there was a sympathetic audience on the other end of the line for my presentation of highlights from NTEN’s Non-Profit Technology Conference.

But really, I had no clue whether they were sympathetic or not.

As I was presenting, everyone else’s line was muted, so my words went completely, disturbingly uninterrupted. Not even a hushed cough or a shifting of buttocks on a chair to be heard. And, of course, there was no visual feedback. Were these quiet folk nodding? Sneering? Snoring? Cheering me on? Or wishing I’d finish? Were they, indeed, quiet at all? There was no way to tell.

Teleconferencing is a silent, squirming ordeal for presenters.  It’s not quite so bad when everyone’s an active participant, or there’s an accompanying web-based component, or some other way to provide interaction. But for a straightforward talk, it’s downright nasty.

The best part of making any presentation is feeling the mood of the audience and responding to that mood. You can start off flat and still win them over if you use the visual cues, eye contact, subtle shifting of attention to help you remould your talk to fit the room. Fat chance of that when you’re speaking in the teleconferencing cone of silence.

Web 3.0: Goodbye teleconferences? 

After my bit was over in the teleconference, the host invited questions. I’d been talking about web 2.0 sites and services and someone asked: “What do you think Web 3.0 will bring us?”

There are lots of different ideas about this. Tim Berners-Lee thinks web 3.0 will bring us the semantic web, an Internet in which computers understand the information stored on them and act as truly intelligent agents. Self-aware sites, if you will. Others talk about an intersection of small applications all working together, regardless of whether they’re on your computer, a phone or another device. Something far more sophisticated and seamless than the digital handshaking that goes on now with web 2.0 apps and services. Others think the driving technology behind web 3.0 will be improved hardware and greater bandwidth, and applications which benefit from these hardware advances.

Perhaps it was in response to the eerie quiet in which I had just presented, but I picked on the latter; the hardware-driven advances. I said web 3.0 would be the death of the teleconference. After all, there’s no reason why, with the faster connections and more powerful graphics processing coming down the pipeline, videoconferencing shouldn’t replace teleconferencing almost entirely - at least in countries with big, fat Internet pipes and generous data plans, like the US. If I can conference on Skype with my far-flung family now, then surely web 3.0 will deliver ubitquitous video interactions.

Of course, web 3.0 should herald much more than merely the death of teleconferencing. Seth Godin has an interesting take on web 4.0 and it sounds good to me. But only if I no longer have to teleconference. Without that advance, web 3 or web 4 will both be failures.

I’ve been a fan of TinyURL for some time, and I blogged about it recently. TinyURL converts long, unmemorable web addresses into tiny web addresses. For example, TinyURL converts the address:

http://www.rosevines.org/blog/2008/1/25/troubleshooting-a-google-slow-down-makes-me-think-about-dump.html

into:

http://tinyurl.com/ytgp26

That’s much easier to type correctly into your browser and works well in email, where long addresses are often broken. The TinyURL is also permanent: once you create it, it can be used by anyone, anywhere, at any time; if you try to create a TinyURL for a previously-Tiny-ed site, you’ll be given the same shortcut URL.

The only trouble is, these short URLs are just as unmemorable as their long equivalents. If you want to return to the site, you’ll need to have stored or written down the TinyURL.

Moourl performs the same miniaturisation trick as TinyURL, but goes one better. It generates a small, randomly generated series of characters, such as:

http://moourl.com/bgw81

and it then gives you the option of assigning your own 20-character Moo address as well. So that initial long address could end up as:

http://moourl.com/blogslowdown

Now that’s short and easy to recall.

Quite a day today: Mixed it with 650 other women online at the Women Who Tech (WWT) telesummit and my new Apple MacBook Pro arrived.

The telesummit was excellent. Sessions were held using ReadyTalk, with slideshows online and a free phone-in number. There were some glitches with the web side, mostly due to misunderstandings and broken links. I found the ReadyTalk support people very helpful in response, and the WWT women were equally helpful and flexible. There’s room for improvement in helping newcomers understand how a combined phone-in/webinar works, but hundreds of women managed to participate very happily.

I noticed some overlap in sessions from last week’s NTEN Non-Profit Technology Conference. That overlap wasn’t necessarily a disadvantage: I found it useful to have some concepts and material repeated with the slightly different slant required by a webinar. The 75-minute sessions zipped past at an amazing rate and were stuffed with good information and useful resources. I attended sessions on Get Your Local Campaigns On; Build an Online Campaign; Women and Social Capital; Firing up your Online List; Everything you Wanted to Know about Tech But Were Afraid to Ask; and Web 2.0 sessions. I used Twitter to tweet all the sessions I attended, while following those I couldn’t attend via others’ tweets. Very effective but definitely a multitasking stretch, what with several other background tasks requiring my attention.

A few highlights: Beth Kanter’s Cute Dog Theory of Web 2.0; listening to the panel field all sorts of questions in the Everything You Wanted to Know session; hearing some of the personal tales behind the highly successful ventures of some very high profile women.

Women Who Tech will be publishing the sessions online for those who couldn’t attend, so keep an eye on their site. And keep an ear out for the next time around: it’s a high-value, high-intensity day.

Crossing over 

In fact, so high-intensity was it that I didn’t get a chance to open the box containing my brand new Mac. It’s sitting here, beckoning. I plan to leave it under wraps until tomorrow, when I can do it justice. As this will be the first Mac I’ve spent time with for well over 15 years, I plan to blog the experience.

The abundance of very happy Mac users at the NTEN conference and the ability to run Windows on the new Macs has lured me into this new realm. While I’m not planning to plunge into the ranks of the blinded-by-the-Mac fanatics, I think Microsoft is becoming more of a lumbering behemoth with each passing year and it’s time to look at alternatives. I intend to load up the release version of Ubuntu 8.04 when it’s launched in 24 days, so it should be an interesting time.

I’ve been resisting Twitter because I thought the signal-to-noise ratio might be so bad it’d be unbearable. But with the NTEN (Non-profit Technical Network) conference about to take off in New Orleans next week and many NTENers planning to use Twitter as a backchannel for the conference, I decided I better get on board. Of course, now I’ve been completely seduced.

The seduction started almost immediately. I decided to follow one of the NTEN conference participants and immediately discovered a bunch of little gems in her tweets. Links to interesting sites; a new and interesting beta program just opening up; some news about another conference I couldn’t attend. Within minutes of starting to use it, Twitter had already paid off. It’d be incredibly easy to be swamped by Twitter, but a little discernment in who you follow makes all the difference.

I’ve been wondering how I’ll use Twitter at the conference. I’ll be lugging my laptop with me and I’ll have my cell phone, and Twitter is accessible using either of them. But I’ll need to ration my laptop use to preserve my battery (a conference with 1000 techheads in attendance - just imagine the competition for power outlets!) and I prefer not to receive tweets via SMS. So it dawned on me that I have another alternative: my Kindle. It’s comfortably portable, not very power hungry even with the wireless switched on, has a web browser built in and a keyboard for sending Twitter updates.

I’m not a great fan of the Kindle’s web browser, but that’s probably because I am yet to be convinced of the appeal of viewing any web site on a tiny screen. Still, one of the great virtues of Twitter is the tweets are short - 140 characters and that’s it. And there’s a Twitter mobile site, m.twitter.com, which winnows away all the excess fluff from the normal Twitter site and leaves you with a clean list of tweets and links. That seems like an ideal sort of site for Kindle-based viewing.

So I loaded up Kindle’s browser (you get to it by clicking Menu in the Home screen and then selecting Experimental -> Basic Web) and typed in m.twitter.com. After logging in - probably the hardest part of the whole deal - there was a lovely, clean list of my tweets and the tweets of people I’m following. I added my home page to the Kindle bookmarks, a bookmark for the “People You Follow” page, and jumped over to the NTEN conference group (08ntc) and bookmarked that, too. Then I sent a tweet using the keyboard - quick and sweet.

Accessing links on the Kindle entails scrolling to the text containing the links and clicking - you’re then offered a list of all the links in that piece of text and you can scroll and click the one you need. It’s a little clunky, but quick enough to use, especially with Twitter’s condensed style. In fact, Twitter is probably one of the best fits for Kindle’s dumbed-down browser.

So I’ll head off to the NTEN conference next week with the Kindle in hand. I’ll report back on the experience. By the way, you can find me here on Twitter.