Will this networking topology work?

[vziera]

Okay here is the update in response to your inputs friends:

Kindly correct me if there's anything wrong, and yes this is kinda for a small business office. Really appreciate your comments friends, it means a lot!

 

[Ahhzz]

Looks sharp.

 

[xvi]

Kindly correct me if there's anything wrong, and yes this is kinda for a small business office. Really appreciate your comments friends, it means a lot!

Looks nice! Only thing I can think to add is to see if that wireless printer/scanner can be wired in somehow. If signal strength is good off of it, it should be okay, but it adds a hefty chunk (relatively) of unreliability since it's competing with just about everything else that uses 2.4 GHz. I've seen a surprising number of wireless issues caused by things like baby monitors and wireless cameras. If you're not rubbing elbows with your neighbors (potential interference), it may not be much of an issue.

I had a client who'd call up because her home wireless network would disappear whenever her neighbors were home. Went from working great to can't even see it. Her computer was only a few feet from her router. Her neighbors were about 120-150 feet away (depending on which one she was talking about). I don't know what her neighbors were doing, but spitting out THAT much 2.4 makes me concerned for their health. No idea what it was.

 

[vziera]

What of the labels and parameters? are they correct? I mean the IP, DNS, etc

 

[Ahhzz]

What of the labels and parameters? are they correct? I mean the IP, DNS, etc

Overall, looks good. I would probably hard-code the IP for the Access Point in the top center, for ease of troubleshooting later. The same with the printers, as they usually have web pages that make management easy, and these days, the auto-follow function that keeps track of the printers when they change IP, is proce to not giving you an actual IP to use, but something gobbledy-gook. Otherwise, I think you're fine.

 

[vziera]

Awesome thank you mate!, you guys saved my life and those who are new to this kinda thing!!!

 

[FireFox]

Anything connected to the router should pull a private IP if DHCP is enabled

And if a Pc is connected to a router but the DHCP is not enabled what happens?

 

[xvi]

And if a Pc is connected to a router but the DHCP is not enabled what happens?

APIPA! (Automatic Private IP Address). That's that 169.254.XXX.XXX(/16) number that devices sometimes get when a connection isn't working correctly. It's designed that in the event that there isn't a DHCP server available (an Ad-Hoc wireless network, for example), all devices will give themselves an IP on a common subnet and said devices can still communicate with each other.

 

[vziera]

Gonna make the final revision, thanks bro!

 

[brandonwh64]

And if a Pc is connected to a router but the DHCP is not enabled what happens?

No Ip is given to the client.

http://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol

 

[FireFox]

No Ip is given to the client.

http://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol

It means that if I have a router and I turn of DHCP and the Pc is connected to the router I won't get Internet?

 

[xvi]

It means that if I have a router and I turn of DHCP and the Pc is connected to the router I won't get Internet?

Correct. Your router won't give itself an APIPA address and the APIPA address that your devices assign themselves wouldn't care even if it did. They wouldn't know that your router is a router and it wouldn't know to put any data through it.

If you turned off DHCP on your router, someone could still statically assign themselves a normal address and still access the internet through the router, assuming they had/guessed the right IPs for everything.

 

[FireFox]

Correct. Your router won't give itself an APIPA address and the APIPA address that your devices assign themselves wouldn't care even if it did. They wouldn't know that your router is a router and it wouldn't know to put any data through it.

If you turned off DHCP on your router, someone could still statically assign themselves a normal address and still access the internet through the router, assuming they had/guessed the right IPs for everything.

I have a weird case.
To my router i connect a Netgear firewall and to the Netgear i connect my pc, the router act as router modem then i go to my router settings and i turn off DHCP and set the router modem to act just as Modem then i apply and save the settings and the Pc doesn't loss connection, how could that be possible?

Note: when I do those changes the Pc is turn on and connect to the Internet.

 

[brandonwh64]

It means that if I have a router and I turn of DHCP and the Pc is connected to the router I won't get Internet?

You could manually assign the IP and DNS to each PC if you want but the router itself will not give it an IP address.

 

[remixedcat]

There's also somehting called static DHCP and that's what i use for the main systems.

 

[FireFox]

Still no answer to my weird case

 

[remixedcat]

turning off the DHCP server makes it into a switch for wired and an access point for wireless.

then when you connect it to the 1st router that 1st router is the DHCP server and such.

 

[FireFox]

turning off the DHCP server makes it into a switch for wired and an access point for wireless.

then when you connect it to the 1st router that 1st router is the DHCP server and such.

Ok that's a logical answer.
But why if I first turn off DHCP and set the Modem Router to act just as Modem and then I connect the Netgear firewall to the Modem Router that it's acting just as Modem and then i connect the the pc to the Netgear Firewall I don't get Internet?


Note: I Noticed that first I have to leave the Modem Router with DHCP turn on and leave it acting as Router Modem after that i can connect the Netgear firewall and then I connect the pc and I get Internet, turning DHCP off and setting the Modem Router to act just as Modem before I get Internet connection don't give me Internet and that doesn't make too much sense.

 

[remixedcat]

Ok:

Modem/router (MODEM ONLY)>Router/Firewall>PCs.

Is that what you are trying to do?

Why not just get a seperate modem, connect to the firewall, then use the switch and access points?

If you have the modem in modem mode only you need to set the DHCP on the firewall.

If the modem/router is on BOTH you need to turn off DHCP on the 2nd device.

 

[FireFox]

Ok:

Modem/router (MODEM ONLY)>Router/Firewall>PCs.

Is that what you are trying to do?

Why not just get a seperate modem, connect to the firewall, then use the switch and access points?

If you have the modem in modem mode only you need to set the DHCP on the firewall.

If the modem/router is on BOTH you need to turn off DHCP on the 2nd device.

Sorry for the late reply.
Btw, that's not what I am trying to do, that's what i have
That's right Modem Router only Modem>Netgear Firewall>Pcs,

DHCP is turn off on the Modem/Router that act just as Modem and the Netgear firewall is acting as Nat.

 

[remixedcat]

That should work if it's really a firewall

 

[remixedcat]

not unless the modemrouter is borked

 

[FireFox]

That should work if it's really a firewall

Yes it is, btw what means borked?
Sorry about my ignorance

 

[Mindweaver]

Like @remixedcat said you'll want to turn off DHCP on the 2nd router. Having two routers on the same network will cause nothing but problems. Now you could have 2 and do something like a load balance and set the 1st DHCP server to 192.168.10.2-192.168.10.127 and the 2nd DHCP server 192.168.10.128-192.168.10.255, this would create redundancy as well in the event one DHCP server fails. I would set the DNS server on your server. Do you plain to use /24 subnet?

 

[xvi]

"Borked" is slang for "broken", basically.

Like @remixedcat said you'll want to turn off DHCP on the 2nd router. Having two routers on the same network will cause nothing but problems. Now you could have 2 and do something like a load balance and set the 1st DHCP server to 192.168.10.2-192.168.10.127 and the 2nd DHCP server 192.168.10.128-192.168.10.255, this would create redundancy as well in the event one DHCP server fails. I would set the DNS server on your server. Do you plain to use /24 subnet?

I don't think a typical router would allow that level of control over DHCP settings, although I think it would if it were flashed with DD-WRT (or similar options). Would be a nifty solution if possible though.