One of my customers called the other day to say their internet wasn’t working.

I talked them through various diagnostics over the phone and it became clear that although the internet connection was synchronising there was a problem authenticating the customer.

To confirm the fault I went to the customer premises with a spare modem/router just in case it was an equipment fault.

At the customer premises I confirmed the authentication problem which resulted in the customer’s modem/router not being assigned an IP address or DNS servers.

Our technical guys tried to resolve the problem, but in the end they had to pass the problem to BT as the fault appeared to be associated with the BT equipment at the customer’s local exchange.

Whenever we pass a problem to BT we always get the ominous warning that BT will levy an extortionate call-out charge if the fault is found to be with the customer’s equipment.

Within a few hours of the fault being reported BT advised that they had fixed the problem by doing some work at the exchange.

However, the customer still had no internet connection.

I had to make another visit to the customer premises to investigate.

I confirmed that there was still a problem and called our technical support team.

I was advised by technical support to change the username in the modem/router to a BT test username.

I did this on my first site visit, but this time the router did get assigned an IP address and DNS servers and I could browse to a BT test site.

Clearly BT had done something at the exchange as this did not happen on the first visit.

However, the problem was still there when I changed the modem/router username and password back to those of the customer.

Someone in our technical support bypassed the normal BT fault reporting system to speak to a “mate” in BT to find out what was going on.

With his mate’s help we discovered that on fixing the fault a BT engineer had somehow changed the routing of internet authentication to a different Internet Service Provider.

That was why the customer’s username and password were not being recognised and why an IP address and DNS servers were not being assigned.

Fortunately the mate at BT was able to implement a temporary fix so that the customer could get back on-line as soon as possible.

The situation now is that the problem has been completely resolved by going through the proper BT channels.

Given that BT are eager to charge for abortive call-outs if a fault is with customer equipment I am left wondering why I can’t invoice BT for 2 x abortive call outs caused by their equipment fault and their incompetence in resolving the problem.

Has anyone out there tried this and suceeded?

One of our long standing internet customers is the Chaplaincy at Edinburgh University.

They switched to our preferred Internet Service Provider (Quik Internet) when we sorted out a connection problem they were having a few years ago.

Since that initial visit they have been the ideal customers: ie prompt payers and no reported problems!

However, that changed a few days ago when I got a call from the new Bursar who demanded a resolution to their long-standing internet connection problems.

This was a surprise to me as I had not been made aware of any long-standing internet connection problems.

The Bursar advised that the internet connection was dropping regularly and could only be restored by switching the router off then on again.

I was sceptical that it was anything to do with the external internet connection as all our remote tests indicated that there was no problem with the connection.

Nevertheless, I arranged a visit to the Chaplaincy to try and get to the bottom of the problem.

The set-up at the Chaplaincy is that there is a Netgear DG834G modem/router connected to a data switch that provides connections to indivudual outlets throughout the premises over a Cat 5 cabling system.

The premises cover 3 x floors over 2 x adjacent buildings.

I first went to their comms room and checked the router and upgraded its firmware.

I couldn’t find anything wrong, the connection was steady and as fast as could be expected.

I then talked to the Bursar and asked about the devices that are connected to the network.

I discovered that in addition to a couple of PCs directly patched to the Cat 5 outlets there are several Apple Macs connected wirelessly through 3 x Time Capsules and 1 x Airport extension device.

The Time Capsules are connected directly to the Cat 5 outlets and the Airport is connected wirlessly to one of the Time Capsules.

Internet access is also made available to students by providing them with the wireless log-in passcode.

The Time Capsules had been introduced after I configured the original network.

I started to suspect that there might be some sort IP address conflict that was causing the internet access to lock up.

I thought that the Time Capsule IP addresses could be conflicting with those provided by the other Time Capsules and with the IP addresses in subnet created by the Netgear DG834G.

I soon discovered that none of the Time Capsules were set to the required Bridge Mode of operation.

With Bridge Mode the IP addresses to the devices connected to the Time Capsules are managed by a connected router which in this case was the Netgear DG834G.

I made the required changes to the Time Capsules and set up a single wireless network with seamless roaming across the 2 x buldings.

The Netgear DG834G now has total control over managing the IP addresses and there is no possibility of an attached device having the same IP address as another attached device (unless one of them is using a fixed IP address).

This appears to have resolved the problems with no reported internet access problems for several weeks.

This situation highlights the fact that the natural assumption of most customers when they have an internet connection problem is that the problem must be with their internet service and they make their first call to their service provider’s support number.

I find this odd since the the natural assumption when an electrical appliance stops working is that it is the appliance that is faulty and not the electricity supply.

The truth is that most internet access problems are caused by the customer’s equipment or local network connections.

In my view a large part of the problem is the misleading error messages displayed by the applications on the user’s computer when the internet is not available.

These usually advise that internet access is not available and suggest that the customer should contact their network administrator or service provider.

While it may be true that the internet access is not available to the application, most customers do not appreciate that the problem could be caused by the  software in their computer (eg  the firewall), or it could be their network connection (wired or wireless),  or it could be their modem or router or as in the above case it could be other devices connected to the local network.

All of these are a much more likely cause of the problem than the external internet connection.

© 2010 Premitel Suffusion WordPress theme by Sayontan Sinha