geek help...quick, por favor

[syf350]

i have a machine whose address is 192.168.200.1.

i need to tell a customer that any remote clients they want o be able to connect to this machine must be in that same "family", i.e. 192.168.200.2, etc


what is the language i am looking for, since i have a good feeling "family" is not correct?

i'll fax anyone a beer who helps.

[Datawiz]

Originally Posted by syf350

i have a machine whose address is 192.168.200.1.

i need to tell a customer that any remote clients they want o be able to connect to this machine must be in that same "family", i.e. 192.168.200.2, etc


what is the language i am looking for, since i have a good feeling "family" is not correct?

i'll fax anyone a beer who helps.

192.168.... is considered a PRIVATE IP ADDRESS. It will not be accessible to the outside world, unless you create a service that gets forwarded to that private IP. Someone across the city can't set their address to 192.168.200.3 and be able to access your stuff.

[Milton Fox]

"downstream#" You should wait until someone else responds, because I dont know the real answer! I think that last bit of information is helpful though!

[syf350]

Originally Posted by datawiz

192.168.... is considered a PRIVATE IP ADDRESS. It will not be accessible to the outside world, unless you create a service that gets forwarded to that private IP. Someone across the city can't set their address to 192.168.200.3 and be able to access your stuff.

got it...but whats it called? scheme? group? ?

[Datawiz]

Originally Posted by syf350

got it...but whats it called? scheme? group? ?

subnet

[syf350]

thanks!

carry on....

[NeedSpeed]

You can only mask off the appropriate octet.

[lander]

Originally Posted by datawiz

subnet

[lspencer534]

Originally Posted by syf350

thanks!

carry on....

What about the beer?

[syf350]

fax number?

[Datawiz]

Originally Posted by syf350

fax number?

WTF is a fax?

[lander]

Originally Posted by datawiz

WTF is a fax?

Duh!

[snide]

Originally Posted by datawiz

WTF is a fax?

It's what answers my home phone.

[mikeg826]

range

[Cybercowboy]

192.168.*.* is a private subnet.

To make this accessible to the outside world, they need to open a port. For instance, if you want them to be able to hit a web server on that private subnet or something acting as an HTTP server, you would open up port 80 and forward all traffic through their outside IP address to that port. For security reasons this can be quite risky, so if possible get all the MAC addresses of the remote computers and add a filter to the router that only allows connections from those MAC's. HTTPS service would be port 443. Typically it's one or both of these ports that need to be opened up, but again it opens that port to the world unless you do some sort of security.

For examples on how to do this, find the router manufacturer and model if possible (for instance, NetGear Model XXXXXX) and google that make/model with "port forward setup" and you'll probably get excellent instructions.

[HellCat]

Originally Posted by Cybercowboy

192.168.*.* is a private subnet.

To make this accessible to the outside world, they need to open a port. For instance, if you want them to be able to hit a web server on that private subnet or something acting as an HTTP server, you would open up port 80 and forward all traffic through their outside IP address to that port. For security reasons this can be quite risky, so if possible get all the MAC addresses of the remote computers and add a filter to the router that only allows connections from those MAC's. HTTPS service would be port 443. Typically it's one or both of these ports that need to be opened up, but again it opens that port to the world unless you do some sort of security.

For examples on how to do this, find the router manufacturer and model if possible (for instance, NetGear Model XXXXXX) and google that make/model with "port forward setup" and you'll probably get excellent instructions.

Damn! You beat me to it.

[Grey Ghost]

Originally Posted by Cybercowboy

192.168.*.* is a private subnet.

To make this accessible to the outside world, they need to open a port. For instance, if you want them to be able to hit a web server on that private subnet or something acting as an HTTP server, you would open up port 80 and forward all traffic through their outside IP address to that port. For security reasons this can be quite risky, so if possible get all the MAC addresses of the remote computers and add a filter to the router that only allows connections from those MAC's. HTTPS service would be port 443. Typically it's one or both of these ports that need to be opened up, but again it opens that port to the world unless you do some sort of security.

For examples on how to do this, find the router manufacturer and model if possible (for instance, NetGear Model XXXXXX) and google that make/model with "port forward setup" and you'll probably get excellent instructions.

VPN?

[Cybercowboy]

Originally Posted by Grey Ghost

VPN?

Oh god no. VPN's are way overkill for something like this (usually) but certainly one could use a VPN. Based on knowing what the OP does for a living (alarm system stuff) I'm thinking it is for remote access to either a video stream or alarm data. This could probably be done easily by forwarding one or more ports to the WAN.

Lets's say their router is 192.168.100.1 on the LAN side, and on the LAN side there is a web server at address 192.168.100.6. and from the router the outside (WAN) IP is 2.3.4.5. Port forward port 80 from 192.168.100.6 to 2.3.4.5. From anywhere on the web I can ping 2.3.4.5. For instance, you can ping 173.194.115.2 from a cmd prompt by typing "ping 173.194.115.2" or also by typing "ping google.com" (they are the same.) So assuming you can ping 2.3.4.5, they can port forward port 80 and then from any computer with an internet connection, open a browser and type for the URL "http://2.3.4.5" and if there is a web server listening on the computer at 192.168.100.6 on their LAN it will open up whatever web page that server has.

VPN's are credential-based connections where the remote client has to enter a username/password for authentication. Very nice and all, but with port forwarding you are essentially allowing any and all connections that that computer over a specific port (or ports) and the only security possible is to limit those remote connections only from specific IP addresses or MAC's.

Also usually VPN's are made to a domain, not a simple peer-to-peer network like most of us have at home.

[lander]

Originally Posted by Cybercowboy

Oh god no. VPN's are way overkill for something like this (usually) but certainly one could use a VPN. Based on knowing what the OP does for a living (alarm system stuff) I'm thinking it is for remote access to either a video stream or alarm data. This could probably be done easily by forwarding one or more ports to the WAN.

Lets's say their router is 192.168.100.1 on the LAN side, and on the LAN side there is a web server at address 192.168.100.6. and from the router the outside (WAN) IP is 2.3.4.5. Port forward port 80 from 192.168.100.6 to 2.3.4.5. From anywhere on the web I can ping 2.3.4.5. For instance, you can ping 173.194.115.2 from a cmd prompt by typing "ping 173.194.115.2" or also by typing "ping google.com" (they are the same.) So assuming you can ping 2.3.4.5, they can port forward port 80 and then from any computer with an internet connection, open a browser and type for the URL "http://2.3.4.5" and if there is a web server listening on the computer at 192.168.100.6 on their LAN it will open up whatever web page that server has.

VPN's are credential-based connections where the remote client has to enter a username/password for authentication. Very nice and all, but with port forwarding you are essentially allowing any and all connections that that computer over a specific port (or ports) and the only security possible is to limit those remote connections only from specific IP addresses or MAC's.

Also usually VPN's are made to a domain, not a simple peer-to-peer network like most of us have at home.

aka NAT.