pinging a machine on my home LAN

[Kwaj]

I have a LAN whereby all the machines on the network are given generic
192.168.1.X addresses. How would one remotely access a machine on the LAN,
if I know the WAN address of my router?

Assuming my router has a WAN Y.Y.Y.Y and a machine connected to the home LAN
has an address 192.168.1.X - I can ping my router by typing:

ping Y.Y.Y.Y

How would I ping the 192.168.1.X machine?

 

[Skeleton Man]

I have a LAN whereby all the machines on the network are given generic

192.168.1.X addresses. How would one remotely access a machine on the LAN,
if I know the WAN address of my router?

Assuming my router has a WAN Y.Y.Y.Y and a machine connected to the home LAN
has an address 192.168.1.X - I can ping my router by typing:

ping Y.Y.Y.Y

How would I ping the 192.168.1.X machine?

With great difficulty... to access private networks (regarless whether you use
192.168.x.x or 10.x.x.x or anything) from anywhere external (ie. the internet),
you need to setup tunnelling.

A tunnel is a private secure connection between the point you're connecting
from, and your home LAN (usually the tunnel is established between the router
where you connect from, and your router at home, allowing machines on either
network to communicate with each other).

Setup correctly the router at either place knows to send traffic for a
particular subnet (e.g. 192.168.1) via the tunnel.

Honestly tho, for a begginner it really is not worth the hassle.. (if anyone
has a simpler idea please share...)


Regards,
Chris

 

[RBM]

I don't know if would work the same, but I just got an IP camera, which I
could see on any pc on my network by typing the camera's ip address. All
these pc's are behind the router though, to see the camera from the WAN, I
had to set up port forwarding (open two ports on the router) and direct all
traffic through those ports to the IP address of the camera

 

[kony]

I don't know if would work the same, but I just got an IP camera, which I
could see on any pc on my network by typing the camera's ip address. All
these pc's are behind the router though, to see the camera from the WAN, I
had to set up port forwarding (open two ports on the router) and direct all
traffic through those ports to the IP address of the camera

Yes that's correct. The router needs to port-forward the
appropriate ports to the IP for the target box, those ports
varying per the access method (app). Then the user accesses
beyond the LAN, on wan->internet by specifying the router's
IP # and the port number.

 

[Skeleton Man]

I don't know if would work the same, but I just got an IP camera, which I

could see on any pc on my network by typing the camera's ip address. All
these pc's are behind the router though, to see the camera from the WAN, I
had to set up port forwarding (open two ports on the router) and direct all
traffic through those ports to the IP address of the camera

For simple things like that it's an option, but where you require access to
several different things on different machines, or the same port on multiple
machines, it's not much of an option (unless you want to pick a new port number
for every service on every machine, and remember which port # is which)

Regards,
Chris

 

[kony]

For simple things like that it's an option, but where you require access to
several different things on different machines, or the same port on multiple
machines, it's not much of an option (unless you want to pick a new port number
for every service on every machine, and remember which port # is which)

Regards,
Chris

Then what do you suggest?
One alternative would be using more routable IP #s. That
gets expensive. Remembering shouldn't be a problem, if you
can remember one (which is sorta necesary for *any* option)
you can load up a webpage (or whatever) with your list.

 

[Skeleton Man]

Then what do you suggest?

One alternative would be using more routable IP #s. That
gets expensive. Remembering shouldn't be a problem, if you
can remember one (which is sorta necesary for *any* option)
you can load up a webpage (or whatever) with your list.

Depends on what the OP wants to do exactly.. they weren't very specific.. all
they mentioned was pinging and remote access (that could be web pages, VNC, or
anything).

Using real IP's would cost a small fortune.. but there is a workaround if they
use DSL.. you can have multiple accounts using the same line.. (e.g. PC1 with
username foobar@isp can use the same modem simultaneously with PC2 and
johndoe@isp)..
That would require the ISP to allow multiple accounts, but it's cheap way to get
multiple real world IP's..

If it's just something simple there's no reason why port forwarding can't be
used.. (again depends what they wanna do)

Regards,
Chris

 

[kony]

Depends on what the OP wants to do exactly.. they weren't very specific.. all
they mentioned was pinging and remote access (that could be web pages, VNC, or
anything).

Using real IP's would cost a small fortune.. but there is a workaround if they
use DSL.. you can have multiple accounts using the same line.. (e.g. PC1 with
username foobar@isp can use the same modem simultaneously with PC2 and
johndoe@isp)..
That would require the ISP to allow multiple accounts, but it's cheap way to get
multiple real world IP's..

Multiple email accounts or user accounts?
What good are multiple accounts? I mean, that does not
change the routing through the internet et al to the router
and into the lan. The multiple accounts are an
authentication on the ISP's equipment, not inside the lan.

If it's just something simple there's no reason why port forwarding can't be
used.. (again depends what they wanna do)

Ultimately one is connecting to the router, no way around
that. The typical router accepts port number, what else?
That's the only commonality I recall. Based on port number
it will port-forward to the machine set up in it's routing
table, as config'd by it's admin.

 

[Kwaj]

I was basically trying to set-up an FTP server on my home machine. the
server sits behind an ADSL router and was not getting a dedicated IP-address

Here was the work around:
1) subscribed for a URL from www.no-ip.com
2) set up the ftp server on port 221 to make sure it doesn't interfere with
any other ftp traffic from any of our other machines
3) port forwarded all traffic on port 221 to the IP-address of the server
4) installed a dynamic-update-client, to make sure that theURL constantly
maps to our current IP-address...regardless of what is assigned by the WAN.

 

[General Schvantzkoph]

I have a LAN whereby all the machines on the network are given generic
192.168.1.X addresses. How would one remotely access a machine on the LAN,
if I know the WAN address of my router?

Assuming my router has a WAN Y.Y.Y.Y and a machine connected to the home LAN
has an address 192.168.1.X - I can ping my router by typing:

ping Y.Y.Y.Y

How would I ping the 192.168.1.X machine?

You can set up your router to port forward the ICMP port to one of your
machines although this is a really bad idea. In fact you should disable
ICMP on your router altogether. There is no reason to allow your network
to be pinged from the outside, all you are doing is making your network
visible to the evil doers out there. If you do want to access your
machines from the outside you can use secure shell (SSH). You port
forward the SSH port(22) to one of your machines which will allow you to
login to that box. From there you can ssh into any other machines on your
network. SSH is standard with just about all Linux distributions. You can
get it on Windows by installing Cygwin.

 

[Skeleton Man]

I was basically trying to set-up an FTP server on my home machine. the

server sits behind an ADSL router and was not getting a dedicated IP-address

In that case port forwarding will work fine.

Regards,
Chris

 

[Skeleton Man]

Multiple email accounts or user accounts?

What good are multiple accounts? I mean, that does not
change the routing through the internet et al to the router
and into the lan. The multiple accounts are an
authentication on the ISP's equipment, not inside the lan.

DSL usernames here are in the form user@isp-name (like an email, minus the top
level suffix)

1. Move the DSL modem from the router's NIC to your hub/switch (so it's
accessable by all machines).
2. Setup your primary user and PPPO* client on the router. Connect.
3. Setup your secondary user and PPPO* client on a second machine. Connect.
(DSL allows multiple simultaneous connections via the same modem)

The router gets a real IP and of course has an internal 10./192.168. address.
The second machine also gets a real IP and still has its internal address too.

Hey presto ! You now have 2 real world IP addresses !! (for whatever it costs
to have a second user account)

On the second machine you have a choice between using the WAN address as the
default gateway, or going via your router.
I use this method frequently when I need a real IP and port forwarding won't
do.. (or if I don't want traffic on my router bogging down access)

Regards,
Chris

 

[kony]

DSL usernames here are in the form user@isp-name (like an email, minus the top
level suffix)

1. Move the DSL modem from the router's NIC to your hub/switch (so it's
accessable by all machines).
2. Setup your primary user and PPPO* client on the router. Connect.
3. Setup your secondary user and PPPO* client on a second machine. Connect.
(DSL allows multiple simultaneous connections via the same modem)

The router gets a real IP and of course has an internal 10./192.168. address.
The second machine also gets a real IP and still has its internal address too.

Hey presto ! You now have 2 real world IP addresses !! (for whatever it costs
to have a second user account)

Err, OK, but that's the same thing as just having multiple
IP #s, just worded differently, which is more expensive.

On the second machine you have a choice between using the WAN address as the
default gateway, or going via your router.
I use this method frequently when I need a real IP and port forwarding won't
do.. (or if I don't want traffic on my router bogging down access)

If you have only a single DSL line, the router should never
be bogged down more than the DSL line itself.