Why does this work 1

[tylerdurdan66]

I just switch my network to 192.168.2.x with subnet 255.255.0.0

I didn't switch my wireless access point they aer 192.168.1.x with subnet 255.255.255.0

I added non domain computers with a DHCP server and firewall running on 192.168.0.x with subnet mask 255.255.255.0

 

[tylerdurdan66]

I forgot to say that evervthin works great, the wireless access point can connect to either network with no problems. Just wondering why this works.

 

[Serbtastic]

There must be a device on your network routing between 192.168.0.x, 192.168.1.x and 192.168.2.x.

Run a tracert from a wireless host to one of the 192.168.2.x addresses and post it here for analysis.

 

[tylerdurdan66]

The three set of ips are all using the same switches and wiring.

 

[Serbtastic]

That's irrelevant. Have you configured static routes on your clients? Run 'netstat -r' and post results for analysis.

 

[MarkhP]

The subnet masks overlap.
255.255.0.0 subnet means that devices can have an address between 192.168.0.0 and 192.168.255.255

255.255.255.0 is a subset of the range available using 255.255.0.0 and would mean that devices using 192.168.2.x can see the 192.168.1.x and 192.168.0.x devices

 

[tylerdurdan66]

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0c 41 62 cb ed ...... Wireless-G PCI Adapter - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.6 192.168.2.100 25
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.0.0 192.168.2.100 192.168.2.100 25
192.168.2.100 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.2.255 255.255.255.255 192.168.2.100 192.168.2.100 25
224.0.0.0 240.0.0.0 192.168.2.100 192.168.2.100 25
255.255.255.255 255.255.255.255 192.168.2.100 192.168.2.100 1
Default Gateway: 192.168.2.6
===========================================================================
Persistent Routes:
None

Route Table

 

[PeterHurst]

Mark is right

Your subnet masks are wrong - they should be 255.255.255.0

 

[tylerdurdan66]

here's the reason I started using the 255.255.0.0 subnet.

I want to be able to access all ips from my machine

I want to disable 192.168.0.x (subnet 255.255.255.0) from having any possible access to 192.168.2.x (subnet 255.255.0.0)

Also I want the expandability on the 192.168.2.x to use 192.168.3.x if ever needed.

Is there a better way to achieve these objectives?

 

[cyberspace]

If it works then i can't see a problem, I think maybe the previous posters mis-read what you were saying.

There is no reason why what you have done shouldnt work from what I can see, the subnet masks are assigned to achieve what it is that you want to achieve.

Systems Administrator
BSc Network Computing, CCNA. Both in training!

 

[KiscoKid]

The best setup would be to deploy VLAN's for each of your users/subnets and user inter-vlan routing between them and controlling which vlan can talk to which vlan.

However, if I recall correctly, didn't you have a Neatgear router, some layer 2 switches and that was about it? (I was the one who originally recommended using a 255.255.0.0 subnet as I dont think you had the appropriate equipment to do it better.)

Check to see if your Netgear (or whoever manufactures the router) can support something called 802.1q trunking. If so, you may be in business and I can advise on this if required.

If it doesn't, based on what you said in your last reply, you can keep things as they are and just add a filter/access control list etc on the router to

(a) Deny 192.168.0.x/16 talking to 192.168.2.x/16
(b) Permit your machine to talk to any host (in fact put this line 1st in case you belong to 192.168.0.x/16)