Well the transition to broadband hasn't been quite as smooth as I'd hoped.
The basic set-up was fine, using the BTYahoo 'frog' (Speedtouch 330 modem). But of course, I've got to have a router and a wireless set-up. So having checked out various reviews, read through umpteen forums, I opted for a Linksys Wireless-G WAG54G router. Got a network card into my PC, and a USB wireless adapter for the other machine. Easy….
Actually it was once I realized I had to plug in the USB adapter before loading the adapter software/driver. And once I realized that activiating the XP firewall on the wireless connection was stopping it reaching the wireless router. Obvious really.
Did a quick check on the ADSLGuide forums and got the thumbs up :up: to rely on the router firewall. Great… all hunky dory, except that the wireless connection kept dropping out. 'Don't panic', I said to my other (and rapidly 'better') half, 'I know what I'm doing. Maybe the connection has gone down at the exchange. Happens all the time, I hear.' True enough, they do drop out occasionally, but I was grasping at straws. I reckon the first drop-out happened when I decided to 'investigate' the router settings, did a save and no doubt broke the connection as a result. Anyway, the connection popped back up, but did seem a tad unstable.
A couple of hours later, it happens to me :yikes: And I'm connected by a cable. Can't possibly blame the wireless technology now. So I plugged the 'frog' back in. It belched a couple of times, but did connect. Hmmmm. Not good. I really didn't believe that the exchange had 'dropped out' and then timed its return so perfectly. Could be a problem. Plugged the router back in and the irksome red light on the 'internet' indicator was still there. Can't swear that it was there earlier, but I guess it means 'DUD CONNECTION'.
Next step was to disable ZoneAlarm, and lo and behold the connection jumped back into action. All sorted. Must be something to do with ZA, and since the router is firewalled, I'll do without. All fine, I think. Aaargh, no it ain't. As I'm writing, the wireless machine just dropped off again. Dark mutterings… I better get this sorted.
Beginning to think it may be how I've allocated local IPs. Need to investigate further but I have a sneaky suspicion that I selected the wrong 'start' number somewhere and that this might be causing the problem…
More later.
Hopefully back later on with some good news.