I have deleted some, but not much of JM's previous post, he writes
JM wrote on Mar 9
th, 2010 at 10:23pm:
... alternate addressing ... is a work-around you shouldn't need. Furthermore, I've seen many (self-inflicted) problems caused by errant alternate addresses - if it would only give you a private address you'd know straight away the dhcp server link was at fault, but you didn't get this. The error message from earlier suggested an invalid IP request - hence my thought on a subnet error.
I am guessing that as you imply later, that Vista has lost the dhcp server, implements an alternate address on the 192.168.0 subnet and then is rejected by the hub. The address requested is private but uses a different 3rd octet, 0 not 1. Your theory, I think, that I have carried an address with me from work needs to be explored, but if that was the case, then how did it connect in the first place. I can confirm that my works LAN, that I connect to wired, most of the time, does use the 192.168.0 subnet address range. So I could have carried it with me from work.
Quote:So, forgetting your blog - the query is being aided here - where are you now with this problem?
Agreed the blog is meant to point here, a small help in its google score this is where I put my final words and ask for help.
I have replaced the BT Home Hub with a Linksys WAG in the location where I caught the event viewer error message. So I hope we won't see any problems again. However the address at which I originally documented the systems failures has not been changed and I will try and hunt down another error message. I am not there as often as I was before Xmas and I don't plug my works machine into the home LAN much either, so I need to get user co-operation to do any diagnostics on the other laptops. Its not as if I can put them on credit hold
The answer here is to use my works machine at home, the connectivity has always been appalling so it shouldn't take long.
Quote:Yes, I too have a passion to hate Vista's unhelpful networking but when it is happy it does work on fixed ethernet and wireless.
If you country code is set right I can't see it using anything other than the proper (to the Hub's) channels - but why not make sure as in an earlier post of mine (pick one, say ch2 - this is done on the Hub btw). Do you use tunnelling vpn at work? If so, try an added delay between one connection and anither - give it 5 mins idle after disconnecting one lan before stby/hib and using on another (try another 5 mins idle from on/resume/wakeup before attempting a wifi connect) and let us know (here) if that help at all.
In my original location, I have changed the channel on your advice, and shall probably do so in the more recent location i.e the location at which I got the event viewer message. I have used inssider to check that I am the sole user of the channel in the area.
I do not use VPN.
But I do change from wired to wifi between work and home locations.
NB This is recent Dell and has "Dell Control Point" installed and running. While looking for
Dell's Sepcification Sheet which is a .pdf, I found this thread called
Dell ControlPoint Connection Manager causes WiFi to drop connection on Dell's community forums which certainly describes the symptoms and one of the BT Helpdesk people has suggested it's a problem. I don't think either of the Studios (my family's laptops) nor the XP laptop has this software, but I can check one of them tonight.
Quote:If you do want a work-around, try 192.168.1.50 as a fixed ip - that will work on your hhub.
That's a thought. (Surely its not so simple). If it is the answer, then as you say, a problem of knowing too much not too little.
Home
Pages: 
