Wireless problem

[Wilmslow]

My guess is another local wifi operating on the same channel.

Download a channel detecting software - can't recall the name, but there are good free ones.

However, why not just try a couple of different channels and see if that cures?

[NickFitz]

One point: most of these wireless routers are set up to use the 192.168.1.x range, IIRC.

The problem then is that all your neighbours' routers are trying to be DHCP servers on the same subnet, which confuses the heck out of the network kit.

Try configuring your router to use another value between 2 and 254 in the next-to-last place - for example, 192.168.153.x, where the "153"can be anything you like between 2 and 254. The router config will almost certainly be on http://192.168.1.1/ or http://192.168.0.1 - TBH it's so long since I had one with the factory defaults that I can't remember what they are

Important point: do this from a machine with a wired Ethernet connection to the router, otherwise you'll have disconnected yourself from the wireless connection when the router switches to the new subnet - I did this once and had to get up off the couch and step over to the desk where the wired machine was, literally two paces away, to finish up. You don't need that kind of pain in your life

Additional important point: If you're using Windows (as you probably are, in which case please accept my commiserations) then you should be able to get away with using a wireless connection to do this if, after changing the router to use a different subnet, you open a command line (Start menu -> Run... -> type "cmd" and hit "OK") then type (IIRC) "ipconfig /renew" then hit return/enter/wotever it's called these days.

[Cowboy Bob]

http://tech.slashdot.org/article.pl?.../06/07/1727240

[VectraMan]

One point: most of these wireless routers are set up to use the 192.168.1.x range, IIRC.

The problem then is that all your neighbours' routers are trying to be DHCP servers on the same subnet, which confuses the heck out of the network kit.

Sorry Nick, but is that remotely true? The low level network gubbins should be keeping the networks entirely seperate, so no DHCP request could get to your neighbours' router even if they wanted to. And two unconnected networks don't conflict with each other.

[blacjac]

Sorry Nick, but is that remotely true? The low level network gubbins should be keeping the networks entirely seperate, so no DHCP request could get to your neighbours' router even if they wanted to. And two unconnected networks don't conflict with each other.

That would depend on if the router is secured and encrypted (WEP /WPA).

Most routers out of the box aren't.

[VectraMan]

That would depend on if the router is secured and encrypted (WEP /WPA).

Most routers out of the box aren't.

I think it's fair to assume that most people setup encryption.

Are you saying that if you have two wireless ADSL routers without encryption near each other they'll join together and form one network? Because I don't think that's true (unless you make it true). And if it's not true, then DHCP setup can't matter.

[blacjac]

Most IT professionals will set up encryption.


Most end users do not (talking from personal experience).


As for weather or not it will form one network, I doubt it.

I can imagine another router broadcasting on the same channel, with the same IP address offering DHCP could well cause problems for a windows laptop.

However that is just speculation.....