|
Post by silverdragon on Jul 17, 2014 8:18:20 GMT
This is a thought experiment, as I have no experience of this particular problem.
My Router, default account Admin, default password was Changeme, as set by the manufacturer.... I changed it. I wrote it down. I wrote it down in the handbook that came with it, and stuck that under the router, so I knew where it was.
Now the router refuses to accept the new logins. It also doesnt accept default logins.
The only option is pressing the reset button... (I know where that is...)
HOWEVER...
My question is, if I reset the name of our LAN and password to exactly the same as it was before reset, will my families Wireless devices just pick up that lan?...
I am presuming the answer will be yes.
The bit I have no idea about... I get the feeling the problem is caused by a rogue router.... I have been having minor problems with service drop outs, a power off and on again reboots the router, normal service is resumed.
So if this carries on, I may have to change the router....
I have it on good authority that if a Wireless lan is set up with more than one router, if the LAN name (SSID) is the same and the pass-phrase is the same, all mobile devices will just "Roam" from one LAN to the next.
So questioning that, if I do replace the router, if I just set up the details to the same LAN name (SSID) with same pass-phrase, my wireless devices do not need to be reprogrammed.
Is that about right?...
|
|
|
Post by paulsee on Jul 17, 2014 12:39:46 GMT
Hi Silver,
Your situation sounds similar to what I experienced last year. Network setup is modem to a Main router. 4 other old routers with their own specific SSID name and password were converted to access points by disabling their network server option and each connected to one of the LAN connectors of the Main Network router.
The Main Router died, bought a new one with a different brand. Set up the new Main Router to be like the old one and everyone was able to access it as if it was the old main router. All access points working as well.
Hope this helps
|
|
|
Post by the light works on Jul 17, 2014 14:25:35 GMT
mine did the opposite - it forgot who it was and went back to the default ID - requiring changing the logins of all computers (eventually I may get around to plugging in my computer and trying to reprogram it, but it currently works despite my computer whining that it doesn't like routers with default names)
|
|
|
Post by silverdragon on Jul 19, 2014 7:15:30 GMT
Thanks, I have a new router "In the post", it will get here eventually.... The ISP suspect a minor fault and will just replace it. If I set it up to the same details as the old one, it will just switch on and replace exactly the old router, I have talked it through with ISP tech's.
|
|
|
Post by Lokifan on Jul 20, 2014 14:57:52 GMT
Hoo boy, now you're making me remember my TCP/IP stuff. Beware! Possible blathering follows... The only problem I can see is if one of your devices skimped on it's protocols--specifically on how it manages its ARP table. ARP is the thing that connects the IP address to the physical MAC address. A MAC address is supposed to be unique to every device ever manufactured (although some cheaper manufacturers cheat) and never changes. IP addresses are usually assigned dynamically, and change depending on the network configuration. Ideally, if your router configuration is identical to the one you're replacing, your network may "bobble" a little as it reconfigures itself, but there should be no problem. Unfortunately, some products don't deal with their ARP table very well, and you get cases where one box insists on trying to talk to a MAC address that isn't there anymore. In this case, it's a bug--but one so common I've seen it very, very often. Best thing to do is to power down the offending device for at least a minute, then restart it. That should wipe out its ARP cache and force it to renegotiate with the new router. One thing I've seen with multiple routers in close proximity is that their radio transmitter/receivers literally were broadcasting on top of each other (even when set to autonegotiate their channels). Changing one to a different frequency fixed the issue. Personally, I've swapped my router out with a new one twice. Each time, I kept the same configuration amd only had one problem with one older device on the net. Curiously, Windows 7 decided to number it's network connection differently based on SSID. So, suddenly I was no longer connected to "My Network Name" but "My Network Name 2". Didn't affect operation, but it did tell me the network recognized the MAC was different, at least.
|
|
|
Post by silverdragon on Jul 21, 2014 9:43:08 GMT
Ah... Actually..... Someone Thunked.
In all respects, this goes beyond the call of duty, and respect is due. Someone was given the problem, and came up with Common Sense. The instructions say... and these I have never read.... because I have never needed to before.... If you are replacing a router with this one, if you set up identical details as the one you are replacing it with, and that router is now turned off, this new router will automatically reconnect with all devices using the old details. Someone somewhere decided that reconfiguring a whole plethora of devices to connect to a replacement router was a right royal pain in the (backside) Spoofing a network ID is only spoofing if done with intent to deceive... If its done with full WEP protocol and network ID is not generic, and you have set a sensible pass-phrase, its no longer spoofing, its replacing?.... So if you turn off one router, replace it with another, and set that up as identical to the old one, why CANT it just work?....
Now I didnt think it would be that simple, but apparently, that commnon sense was decided upon quite a while back.
Having a number of routers in close proximity on the same frequency is always a bad idea?... I wonder why?...[/sarcasm...] And yes, changing the channel on each router is always a fix on that.
|
|
|
Post by Lokifan on Jul 21, 2014 17:41:57 GMT
What can I say? My first access point was massively overpriced and you had to use Cisco IOS CLI to configure it. Since then, I've been very suspicious of all "plug-n-play" nonsense, and have the scars to prove it. Plus, I literally know (as in we go out to lunch now and then) some of the folks who design the firmware for many of the access point/routers for the lower end home/small business market. Some even do competitive analysis, i.e.: they buy every router in their market they can find and beat them to death to find holes in the competitor's products. Every now and then, over some Dim Sum, we'll hear the story of how company X screwed up again, and needs to update/recall/kill and bury in a cornfield at midnight one of their designs. I'm glad it worked out for you. In the near past, it didn't always. Now I feel like one of the Four Yorkshiremen: "We had it tough..."
|
|
|
Post by silverdragon on Jul 22, 2014 6:21:41 GMT
This isnt exactly plug and play.... U still have to connect to the router Wired, and "Set" the LAN name and pass-phrase, minding to set a changed password on the way out, but if I do that and duplicate the old router details, it does the rest by letting all previous connected machines just "Find" the usual network......
This is the bonus, I was expecting to have to manually reconfigure all wireless machines to a new network.
|
|