cellio: (mandelbrot)
Ever since the power surge (and resulting replacement of Linksys box and one other hub), we have been noticing sporadic weirdness on our network. We use DHCP to hand out IP addresses (doesn't everybody?). The Linksys box is configured (by default, if I recall correctly) to start handing out addresses at 192.168.1.100. The Linksys itself is 192.168.1.1. As best I recall, these are the same settings we used successfully on its predecessor for close to three years.

So now, every now and then, it will hand out the address 192.168.1.2. And that unlucky machine will be able to see the LAN but not the internet. Rebooting usually does not fix it, but creative sequences of reboots of all machines and power-cycling of the modem and Linksys usually do the trick.

We cannot find any common factor when this happens. Sometimes it just does.

Tonight, when I found myself the unwilling owner of 192.168.1.2, I decided to try an experiment: I gave myself a fixed IP address without changing anything at the Linksys end. I guessed that I should use 192.168.1.1 for the gateway and name service, rather than the "real" ones; after all, the Linksys box is supposed to resolve the interface issues between the local machines and the network, right?

This worked perfectly. In fact, in a rare Windows moment, I didn't even have to reboot!

I assume that as the other machines encounter the wayward 192.168.1.2 we'll make this adjustment on them, too, until nobody's using DHCP any more. Then we'll forget about this until some unlucky house guest wants to plug his laptop into the network. :-)

I feel like this is an ugly hack. I have not solved the real problem. But at this point I think I'm going to stop looking for it.

Because there is a strict quota on hardware happiness, I found that the 4-port hub we had lying around is really only a 2-port hub. (One is "uplink", which seems to be magic and does not work with anything I tried to plug into it, and one is just dead.) So I can't get rid of the cables strung across the floor just yet.

DSL

Jun. 2nd, 2002 01:58 pm
cellio: (avatar)
Ah, what a joy. I have cast out the demons of stupidity (that would be Verizon) in favor of Telerama. The installation was nearly painless, the pain involved was a problem at our end (not theirs), and the tech-support people (who answer 24 hours a day, by the way) were cheerful, helpful, and not clueless bozos like the guys over at Verizon. (I almost wrote "Luddites", but they obviously don't reject technology wholesale. It provides them an income, after all.)

Read more... )

network

Apr. 4th, 2002 11:04 pm
cellio: (avatar)
You've just got to love support conversations that include phrases like "how long did you say this has been working for you?" and "who told you that?".

Whee. )
cellio: (avatar)
Well, maybe tonight I'll be able to figure out what's wrong with the damned network connection. Off I go... (It's got to be between the modem and the outside world, and thus Verizon's problem. But the modem itself is the only part I can't either swap or drop out of the loop, so it could be an actual hardware failure. I'll admit, though, that I am trusting in Westel not to light the "ready" light if there's no signal coming in.)
cellio: (avatar)
Last night our home network connection was dead, but I didn't have a lot of time to investigate it. (I tried all the simple stuff.) This morning it was still dead. I just tried pinging us from work and it appears it's still dead. Grumble. This means I have to start taking things apart... (Yes, I have a firewall and thus won't answer pings. But I should get a rejection notice, not silence, if the connection is there.)

The modem activity light flickers occasionally, but I don't know if that really means anything. The chain is: modem to linksys box to router box(es) to desktop machines. None of the machines that are presently network-aware can see the internet, though I can see the file server. (Dani can't, but his machine is flaky that way so that's inconclusive.) Presumably this means the problem is at or beyond the modem, but I know from past experience that Verizon won't talk to me if I admit to the real wiring. They want the modem to be plugged into a single machine and they'll want me to mess around with my TCP/IP settings even though the problem is not there. Bah. I've got to improve my mental model of all things Windows so I can fake my half of that conversation. :-)

Well, homeward to see if there are any quick fixes before heading out to D&D.

DSL

Dec. 3rd, 2001 11:46 am
cellio: (Default)
We have a Stupid DSL Setup in our house, but I'm not sure what to do about it. (This thought is brought to mind by friends who were @home customers.)

Once upon a time, I worked for a company that had a policy of paying for a second phone line to support a modem (back in the days before DSL was available). They would pay for installation once.

When Dani and I moved into our house, DSL was available so we decided we wanted that. The company was in the process of figuring out its policies for paying for DSL. They told me to use the modem policy -- get a new phone line, bill the DSL to that, and put the phone line in the company's name.

But, I said, DSL doesn't compete with voice on the line; you don't *need* a second phone line. We can just add DSL to our existing line and you can pay (or reimburse) the DSL part of the bill.

No deal, they said. They would only pay for DSL if it came on a separate bill to them in the company's name. No reimbursement, no layering on an existing phone line.

Well, we said, this is profoundly stupid, but if they want to waste their money... we realized that at some point we would no longer be employed by that company and then we'd have a stupid situation on our hand, but what could we do?

So we got the phone line, and put DSL on it, and the company was happy, and the phone company was undoubtedly laughing all the way to the bank.

A couple weeks after our installation was complete, the company changed the policy to "we'll just give you $40/month if you have DSL and you deal with it". I was peeved, but moving the service would have cost a couple hundred dollars out of our pockets, so we left it alone.

When I got laid off, Dani and I talked about fixing this. But there are two things that have prevented us from doing anything thus far:

1. The current service works. For Verizon, this is no small feat. Moving the existing service would risk disruption for several weeks.

2. The current service is a permanent connection. New accounts are now PPPoE, which is we're told is a royal pain in the ass. And we'd have to reconfigure our network, and every time we look cross-eyed at the network something goes wrong. Why invite it? So if we set up a *second* account (and later kill the existing one, once it works), we'll be stuck with PPPoE because it will be a new account.

We don't actually know that moving the service would preserve our PPPoE-free existence; they might still screw that up. I'm pretty confident that I could not get a reliable answer from their customer-service people before committing, either.

So we are paying $18/month for an unnecessary phone line to preserve a correctly-functioning connection to the Internet. Is that lame, or what?

Expand Cut Tags

No cut tags