Unable to communicate to Network Segment on same subnet

Currently the network is setup as follows.
IP: 192.168.17.x

I have configured another router on same physical network to be static with:


From 192.168.17.x, I cannot ping
Cannot ping from 192.168.20.x to

Nor am I able to get out to the internet, I'm at a total loss right now, does anyone have some insight into this?

I have disabled firewall rules on each end to test, still nothing.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Neil RussellTechnical Development LeadCommented:
You have Gateway:

What is Does it have routes set for the 192.168.20.x address?
I'd agree with Neilsr, I'd guess the issue is that doesn't know how to reach the other network(
David SpigelmanPresident / CEOCommented:
The problem is your subnet masks. Because of your masks, your inside and outside addresses are on the same network.

A mask of means that the network goes from: -

Now the question is: Why are you using a mask? If there's no real reason for you to be doing so, you should do one of the following:

Change the subnet masks to all around, which will give you networks of and You should be able to route between those.
Change the IP scheme inside the internal router to with a mask of

Doing one of those ought to enable you to get out from behind the inside router. As for routing from the 17 network to the other network (i.e. inbound), you're probably going to need to do some static routing somewhere to tell your 17 clients to point to the 17.45 address if they want to reach devices on the other side of the internal router. You could probably do that on the external router, which would make it easier to handle.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ensure Business Longevity with As-A-Service

Using the as-a-service approach for your business model allows you to grow your revenue stream with new practice areas, without forcing you to part ways with existing clients just because they don’t fit the mold of your new service offerings.

Neil RussellTechnical Development LeadCommented:
You can only have ONE default gateway on your network. That gateway MUST know of all routes it needs to access other networks.
David SpigelmanPresident / CEOCommented:
The default gateway is for the inside clients (i.e. on the inside of the internal router.) But it's still not going to work because both sides are on the same subnet. In fact, I'm surprised that the router allowed it.
You stated what is wrong within your problem description:

     "Unable to communicate to Network Segment on same subnet"

Based on your subnet mask, addresses your IP subnet includes addresses -  As you seem to know, this means that 172.16.17.x and 172..16.20.x are within the same IP subnet.

As you seem to imply you also know they are on different "network segments", also known as different LAN.

To expand on d0ughb0y explanation a bit, which may make it clearer.  Hosts within the same IP subnet must be on the same LAN segment in order to talk to each other.

So you need to do something so that your hosts are on different IP subnets.
David SpigelmanPresident / CEOCommented:
Except that it's 192.168, not 172.16 - but I know why you said that. :)
Oh, crap.  I'm doing a bunch of work on my network in our 172.16 subnets.

Thanks for catching that.
Khandakar Ashfaqur RahmanExpert/ConsultantCommented:
If you communicate within same subnet then you don't need to use router but simply you can use switch.Your Network IP Range: -
When you are using router then it seems you want to create another LAN.For that case, you must not use any IP between - for your routers internal interface. You may use different IP for your routers LAN interface like:
MSkrezecAuthor Commented:
Thanks guys, it's a bit more clear to me now -- I understood that a static route might have needed to be but in place, however I was under the impression that since I had placed a router with Gateway, it would handle and forward all request outbound/block incoming.  I've got it up and running now using subnet and .32 as d0ughb0y had suggested.

We've currently got 2 networks on the same subnet, other is at 13 and ours is at 17, couldn't I technically use .32 on
David SpigelmanPresident / CEOCommented:
Yes you could use the mask on the 32.0 subnet, which would give you addresses from But do you need subnets that large?
MSkrezecAuthor Commented:
Well, we currently have 2 full racks virtualized for production environment on first segment, all of IT on 2nd segment, and plan to have a dedicated virtual test environment on 3rd segment.  However, subnetting is not my strongest point, guess I slept too much in Highschool, however still got my CCNA.

My engineer was off yesterday, didn't want to have to bother him while i'm playing around and didn't want to take production down, so to experts-exchange I go!

Thanks for the help guys.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.