If a VPN connection over the internet is not an option, you may want to contact your local communication providers (AT&T, Comcast, etc..) and find out what type of metro ethernet connections they may have. A provider can simply provide you with an ethernet cable at each end and they handle the traffic through their private cloud.

Ok...

So first, generally if a router has more than one NIC, each NIC is on its own subnet. A router wouldnt have more than one NIC that belongs to multiple subnets. Do not confuse a traditional router with that of a consumer based internet router that has many ports on the back of the box. I think this is where your confusion is. I applogize. On an internet router that has 4 ports in the back, this internet router is actually a router with a built in switch. This type of router has only ONE subnet. You can plug additional switches in that back of this internet router. Think of the internet router as two devies, a router and a 4 port switch in one box. that 4 port switch is already wired to the router's port.

Now in this example, you have two switches plugged into the back of this internet router. OK... so far so good. 10 computers plugged into each switch. Now the router wants to send a packet to 192.168.1.1. The router has no knowledge where the computer is plugged into. The router ONLY needs to know computer1's MAC address. If it hasnt communicated with it recently, it needs to get Computer1's MAC by peforming an ARP request (dont worry about that detail for now). When the Router has Computer1's MAC, it send the packet to the switch. Keep in mind on the internet router, we are still inside the same box. Now the 4 ...

The router may be connected to more than one switch, but it each switch will be on a different router port and VLAN. so if the router needs to send a packet to 192.168.1.1, it knows that that subnet is on the router's first interface, as an example. So here is what happens in the scenario where the router needs to send a packet to computer A:

1) router has a packet that it needs to deliver to 192.168.1.1
2) router determines that to get to this host it needs to send the packet on interface 1 (based on the router's routing table)
3) router checks its arp table to see if it has a MAC address for host 192.168.1.1
4) if router has MAC, it sends the packet on that interface. If it doesnt, it performs an ARP request until it gets the answer.
5) packet is own its way on that interface. This interface is connected to the switch port. The switch picks up the packet
6) Switch is a layer two device, doesnt care about the IP
7) switch looks at the packet to inspect the destination MAC.
8) Swich looks at all MAC tables to see if it can knows which port the MAC has been seen.
9) if the Switch finds the MAC in its tables, it send the packet on the correct port
10) if the switch does find the MAC, then it sends the packet on ALL of its port
11) If #9 ...

hello silvercats..

1) Yes, a router has a MAC address and IP on each network interface. The MAC address is the layer 2 (physical) address, while the IP address is the layer 3 (logical) address.

2) the router doesnt really know that the switch is there. When a computer needs to send a packet to a remote network, it sends it to the gateway (router). there may be a switch between the computer and the gateway. The switch has the MAC addresses learned in its tables so it knows which ports to send the traffic through.

3) Routers do operating at network and data link layers. TCP/IP depends on the data link layer for local delivery of packets. what I mean by that is for one host to send a packet to another host on the same segment, the host uses the MAC address for delivery.

I can go into more detail if you have more questions after reading this response...

ChrisHunter's on the right path, just a few things to add to his answer. The three computers on the LAN do not get configured with the public static IP. They will be configured with private IP addresses . The only correction is the say the private side of the router is 192.168.0.1. Then computer #1 will be .2, computer#2 can be .3 and so on. The computers on your LAN can all be set dynamically except your web server, make that IP a private static. It is not important which IP your dynamic clients are assigned within the range.

For question #2, just make it a private static on the same internal subnet, .2 is fine.

For question#3, what you do is port forwarding on your router. First it would be best to have a DNS address, assign that hostname to the public IP address on your router. Then on your router create a port forwarding rule for that public IP on port 80 and map that to te private IP you assigned to your we server on port 80 as well. Make sure the server is running web services and that it's local firewall, if enabled, allows 80 inbound.

That is pretty much it. You can do this on the router without port forwarding by exposing the private server to the Internet completely by the public IP, by I do not suggest that as the server will be fully exposed.

The OSI model is conceptual. In the example you provided the Win 95 system would require a driver to support Wifi.

Each layer depends on te lower layer to get to the wire. For example if you were to develop an application, would would code into your app how to place the 0's and 1's on the network media. You application make calls into the lower layer (other programs) so on and so on. The reverse happens on the target machine on the way up the OSI until it reaches the application layer. For example, wifi NIC vendors do not integrate code into their firmware for a specific target app.

Create two divs, outer and inner div. The inner div goes inside of the outer div...

<div class="outerDiv">
  <div class="innerDiv">
    your main content
  </div>
</div>

CSS
.outerDiv {width:75%;margin:auto;}
.innerDiv {style as you would normally for your content}

Have you checked with your webserver provider that they allow outbound SMTP connections on port 465? since you are getting a transport error, that would be my first suggestion to validate.

Lusiphur commented: What they said... +0

Have you considered running Windows 8 as a VM. It's an easy simple way of evaluating operating systems without the fuss of screwing around with your desktop OS. Windows 8 CP runs great on VirtualBox.

Configure virtualbox: http://www.itgeared.com/articles/1099-running-windows-8-developer-preview/
Install Win 8 as a VM: http://www.itgeared.com/articles/1270-install-windows-8-consumer-preview/

I would hope that this is an error on their part and that they are not doing this by design. I would contact the company you bought this from and report the issue. I would assume that the entire roll from the same batch has this problem. There's going to be a lot of unhappy network'ers out there.

jbennet commented: You seem cool +14

You have various options. Each OS is going to have strengths and weaknesses in the categories you listed. The fact is that most of the operating systems on the market, if installed and configured correctly, along with proper routine maintenance, following best practices, will result in a low spec, easy to use, secure, and well performing operating system.

Unfortunately for Windows, they have made it too easy to acquire the product and install through wizards with alot of roles and features enabled by default. This type of scenario increases the chance of system instability, exposure to malware, etc..

Some of the other non-Windows operating systems may be stereo-typed as being better with regard to security, but the reality is that due to the low integration into the market, those that develop malware traditional do not target the non-windows systems.

If you are working on a project, I would suggest that you choose an operating system that you are not familiar with so that you can take advantage of this as a learning opportunity.

jbennet commented: Good answer +15

[QUOTE]I do believe that if I set up a vpn connection to the database network(WORK NETWORK), it will work just fine and it will be secure, and no public wifi user should be able to access ANY network resources that is on the WORK NETWORK. PLEASE correct me if I am wrong.?![/QUOTE]

You are correct.

To have a dedicated router that can support VPN tunnel would suggest that you have more than one person in this building that needs a secure connection back to the remote office. Generally, these "branch office" tunnels are created so that you can have a small office of employees to have a secure connection back. However, just to summarize what I had suggested before...if you are the only employee at this location, then a VPN router is not feasible. All you need to do is load the VPN client on your computer and connect back to your work's network through their VPN gateway. This will create a secure tunnel over this pubic network. That is safe. If you do require to create a branch office tunnel, then both networks at this location should be separated by VLANs.

Some routers provide run a web server to allow the administrator to use a web browser to interact with. This is where you may think that the router was programmed using Java. Now, it may be that the router's HTTP server is serving java pages. That is not uncommon. You would need to check with your router's documentation for more information about the HTTP server that it is running. However, as L7Sqr indicated, the core IOS that the router is running to "route" packets is not going to be written in Java.