I'm studying for my Microsoft 70-291 test. As I go through some sample exams, and questions, one question has me confused.
Question is basically this.
There are two subnets, Subnet1 and Subnet2
Server1 is on Subnet1. You can only allow Subnet1 clients access Server1, nothing from Subnet2.
Subnet1 --> 172.16.1.1/16
Subnet2 --> 172.17.1.1/16
Router Subnet 1 side 172.16.1.5/16
Router Subnet 2 side 172.17.1.5/16
You are only allowed to change TCP properties on Server1 (adapter assigned 172.16.1.1/16).
Answer that is given is go into TCP/IP properties, click advanced, and add TCP/IP 172.17.1.1 and Gateway 172.17.1.5.
Wouldn't this allow subnet2 to access server1? I'm confused.
-
server would not determine what routes are allowed. the firewall and or router would.
-
I think I figured it out. In the advanced tab you're assigning subnet2 to use gateway on their side of the router, which would not allow passage to the other side because they're on separate subnets.
-
Why would you let a windows server route in the first place is beyond me. but sure that would work.
-
First of all, this is a MICROSOFT certification exam, so you'd expect a windows server to act as router. But it doesn't matter, you're adjusting the gateway settings which point to the IP addres of the router, regardless of what it is.
-
someone needs to study up on how IP subnetting works.....
The router/server capabilities do not matter one bit unless the IP subnetting is set up correctly. One mismatched bit in the mask and you'll shutdown whole segments and possibly an entire network.
To the OP, there are loads of training resources that will teach you about subnetting. It it critical that you understand how this works for the msft and cisco certification exams. Look at places like cbtnuggets and solarwinds.net to get started, there are loads of others. The math is a bit of a slog, but once you understand it (there *will* be an ah-ha moment) you'll have it down pat.
TCP/IP Subnets and Gateway Question
Discussion in 'Networking and Wireless' started by HTWingNut, Jun 12, 2010.