Looked at the posted material so far but did not find an answer.

I followed the instructions on uploading the firmwaare for this model router. It uploaded fine. However the next steps indicated RUN CMD IPCONFIG RELEASE ETC ETC. Did this but never saw the correct response as indicated in the PDF install document.

I am on Windows 7 64    router is vers 4.0     sn  cdfaoe7j8886

I am unable to get to localnode:8080 nor back into the router to try again.

Any hints?  Thanks

I kept re-booting both the lap top and router, now we are in fine.

But, and color me stupid, I named the device  n6kzb-100  and created a password, but I can not get into setup now. I guess the User Name is not  n6kzb-100 or I missed it and am stuck.

I have tried resetting the router, but to no avail.

Thanks.......

OK that is working and thanks for the explanation.. But now I can't even get back to the "localnode" with the browser. My adapter sez "no network access".. Mike

I think I see the issue.  In my notes I think I changed it from "mesh" to "AP".

That is why I can't get back in. In looking through the forums, the posted solutions do not work.

I only have this one node with Mesh software.

Mike

I have only the one router by error on my part it is AP.

I tried 8081 no go, I can't get to it.  I have a "yellow' warning sign on the network ICON.

Al was fine until I changed to AP and re-booted, sigh.............

It sez I have no network access.

It acts like it wants an IP address etc for me to connect to it?

Mike

Well I did LAN to LAN with my home router. Comes up with IP of 172.27.0.2 as you say. But no go, I can not ping it or get to it. This is what I get for moving it from MESH to AP without reading first. Thanks, at least it is alive, one way, hi hi. Mike

Later I tried adding the IP of 172.27.0.2 into the ip4 settings of the "local area connection"

I used it as the IP address

net 255.255.255.0

used it as the gate address

no dns

At least now I see the original routers name and it comes up as an identified home network.

But it still sez no network access and can't be pinged.

What a stubborn little beast..........

____________________More Progress

Just did a reset on the router, (the MESH linksys to my lap top, in AP mode), direct RJ45 connection to LAN port. I can now ping 172.27.0.2 and it tells me I am network connected. !!

But I can't get to the setup screen to log in. But progress and thanks to all so far. I took a bit from everyone's suggestions and got it this far, not bad. At least I am seeing the beast now.

(This is real odd ball to say the least).

--------------------------- Time to end this madness..........

Thanks to all, great learning curve. Stupid dog knock wall wart out of its precarious location, my fault, so power to router was gone for a couple of minutes. And despite all my best efforts I can no longer duplicate, nor see the router.

So the time has come to delegate it to the parts bin and move onto another linksys. It is obvious that I have not "bled" enough to be MESH ready as of yet. Will tackle another router later.

Adios and again thanks to all..................END

Nope.... Wont work.

You need to set your PC to something OTHER than .0.1 or .0.2, as they will be in use and you cannot have 2 IP's the same on any network.

The standard first DHCP a node will normally dish out is 172.27.0.5, so manually set (static) your PC to that, with 255.255.255.0 as the subnet, and 172.27.0.2 as the gateway.

Then do an IP Config in cmd prompt to verify that is the settings.

THEN, http://172.27.0.2:8080 and you should be able to get to it.

When set to AP mode, it will take on a .0.2 IP.

If that gets you back into the mesh node settings, change it from AP back to just 'mesh node', save and reboot the node.

Once that happens, you will have to change your PC network settings either back to DHCP, OR, change the gateway to .0.1 (the node), and the browser URL back to http://localnode:8080 or http://172.27.0.1:8080 (same thing as 'localnode' ).

Hope this helps,

Jim

K5KTF

/edit