Build a LAN with a WNDR3400v2

---

FredReed wrote:



What I am confused about is, the "ping" test and "router login", aren't those two functions requiring the use of the internet?

Neither requires the use of the internet.

What you have set up right now is a private network that is isolated from the internet (which is a "network of networks" btw).  But you can still log into the router from your browser, and you should still be able to use ping to check connectivity on your private network.  Everything on the that network will be given an address (called an IP address) from the router.  That allows the router to forward the data to the right destination.  Netgear routers generally use 192.168.1.x addresses ("X" being a number between 1 and 254).  The router itself has a private IP address, and that should be 192.168.1.1.

Home networks are all private (as are most company networks), but usually they are not isolated from the internet. The router manages the private/public connections - similar to the way a human telephone operator would manage phone calls coming into a company (back in the phone extension days).  As far as the router is concerned, your outside internet line is simply broken.  It still will manage local connections (just like a company phone system would allow in-company phone calls even if the public phone lines are down).

So you can think of your devices on your private network as having a local extension that can't be directly dialed from outside, and which can't reach the outside unless the phone lines are up.  That's not 100% technically accurate, but using that framework will be helpful in understanding the basic concept.

Moving on to your S4 - it is also connected to your mobile data network.  So it will actually have two IP addresses - a public address from the mobile provider, and a private one from your router.   That is similar to a phone with two phone numbers.  Both work independently, and (in this case) there's no connection between the two "phone" lines. 

If you open the web browser on either PC, and enter http://192.168.1.1 into the address bar, it should reach the router's web ui.  It will likely want you to go though the setup wizard (but that likely will get stuck because it will detect no internet).  If there's a way to exit the setup wizard (setting up manually) you should take it.  You'll then see all the router management screens, including seeing the list of the devices attached to your private network.

CMD.EXE is built into windows.  You can simply type CMD in the windows search bar (both for win7 and win10) and it will find it.  When you click on it, it will open a black window on the screen.  It is a command line interface, so you'll need to click on the window, and then type commands (like ping).  Windows will execute those commands and you'll see a response also in the CMD window. For instance, 

The C:\>  is the CMD prompt.  That means that CMD is looking at the root of the "C" drive.  Yours should say something like C:/users/username>  The _ after the prompt is the an indicator that CMD is waiting for you to type something (on the prompt line).

I typed ping 10.0.0.1 at the prompt and then pressed enter. CMD ran the ping command which generated the response you see in the window.   Note my router is set up to use 10.0.0.x addresses (another range of private network addresses). 10.0.0.1 happens to be my own router.