Communication problem between 192.168.0.1 and 192.168.1.1

[smartcap]

Here's the situation:

Our office has 2 floors and a DSL connection is shared among all the employees located on both floors.

FLOOR 1:
-----------

-DSL line is connected to a Netgear Wireless Router (192.168.1.1) located on the first floor
-All computers (4 total) on this floor are assigned an IP range of 192.168.1.10 - 192.168.1.14
(subnet 255.255.255.0)
-All computers on this floor have a DLINK wireless NIC card


FLOOR 2
----------
-IP range for computers on this floor are 192.168.0.20 - 192.168.0.26 (subnet 255.255.255.0)
-16 port Linksys Hub
-6 computers total; all 6 computers are connected via CAT5 to this hub
-1 computer is acting as a bridge between the first floor and second; and has two network cards installed (1 wireless NIC card and one standard Linksys NIC card)


PROBLEM
------------

How can I get the comuters on the 2nd floor to see the shared resources on the 1st floor.


BTW they can all surf the net just fine...

 

[JackMDS]

The Bridging computer should have WinXP

Link to: Configuring Windows XP as a Network Bridge.

And then you do regular Sharing.

:sun:

P.S. Bridging with Entry Level Wireless Client card between two Networks. Nah! It will be "Quirky".

Put few $$$ and do the bridging right with two Access Point.

 

[smartcap]

Hey jack,

The computer ion the 2nd floor that's acting as teh bridge is running WIndows 2000 Pro... I sthere anyway for me to accomplish this without purchasing additional hardware?

 

[JackMDS]

You do not need hardware just replace the OS with WinXP.

It does not make sense to design an Office Network with 10 computers around the concept of saving few hundreds $$$.

The first time that you would have trouble you will lose these few $$$ anyway.

:sun:

Edit: Or you can do it without a Bridge. Plug a Wireless Driverless Client card (like the Linksys WET11) into the Hub on the second floor and configure the whole thing as one Network.

Link: Wireless Network - Configuration Modes.

 

[ScottMac]

You can bridge them networks till the cows come home, the workstations will still not see each other; they are on different networks (192.168.0.0 and 192.168.1.0 are not the same address blocks).

Change the addresses so that both segments are in the same block, or put a router of some sort between 'em.

A bridge joins two segments at layer two, IP addresses are a layer three thing. If the layer three address blocks aren't the same, each segment's hosts will ignore the packets from the other segment (like "multinetting" an interface).

Either disable the bridge then add and enable "Routing and Remote Access," or keep the bridge and change one of the segments to match the other's address block.

FWIW

Scott

 

[JW310]

Would supernetting work in this case? Say, instead of using a subnet mask of 255.255.255.0, using a subnet mask of 255.255.254.0?

JW

 

[JackMDS]

Originally posted by: ScottMac
You can bridge them networks till the cows come home, the workstations will still not see each other; they are on different networks (192.168.0.0 and 192.168.1.0 are not the same address blocks).
Scott

The XP Software Bridge is Not a Cow; it is a horse so it can do it.:shocked:

:sun:

 

[skyking]

I'll be setting up a pair of linksys wrt54g routers with the satori firmware to do what you want. I hope to have it running by Sunday afternoon, I will report back here. The routers are 59.99 after rebates at office depot and at Best Buy this week.

Here is a link detailing the procedure:

http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=443

 

[watts3000]

I agree with everyone here buy a router that will allow you to move between 2 subnets. I would get something like what skyking suggested or a regular linksys befsr41 wired router. There know need in trying to save a few bucks when this solution can be set up rather inexpensively.

 

[SNC]

I'm not sure why you do not just change the IP addresses of one set of PCs. Cost is nothing. Makes life simple. If they are setup that way for security reasons than configuring a router or XP Bridging defets that. My vote is to just change the IP's

 

[VirtualLarry]

If you are trying to do Windows' File/Printer Sharing, across/between two seperate TCP/IP subnets, then bridging isn't going to do squat for you, other than slowing down the LAN for all of the nodes involved. Either plunk down a multi-homed, routing server (also as a WINS server/browse master) in between the two subnets, or if all of the nodes need to share files amongst each other (no central file server), then get them on the same IP subnet together.

 

[JW310]

Originally posted by: JW310
Would supernetting work in this case? Say, instead of using a subnet mask of 255.255.255.0, using a subnet mask of 255.255.254.0?

JW

Curious to get an answer as to whether or not the quoted would work. I learned a little about supernetting in a networking class I took last semester, but I'm not sure how/if it would work in this case.

JW

 

[ScottMac]

No. Supernetting would not work.

In that case, you'd do better to use a Class A or B address then to "glue" two Class C into a contiguous block.

In either cae, you'd have to change a bunch of addresses, why not just put them all in the same Class C address block? It's only a couple devices, doing it the way he wants to do it will cost him some efficiency.

FWIW

Scott

 

[Garion]

Actually, if you setup bridging on the PC with two NIC's you could use a supernet -255.255.254.0 to get the two IP ranges onto a single subnet. It's not very good networking and it's difficult to support, but it WOULD function.

I'm with the "just run a crossover cable between the router and the hub and set everyone to DHCP" crowd - By far the best solution. For < ~50 PC's, you really don't need multiple subnets.

Remember, the simple solution is usually the best one. If you maintain two subnets, you'll need some kind of router to go between them, which means another device to manage, more moving parts, something else to break, slower performance and something else for you to document and have to explain to someone else.

One note - This assumes that you're doing wireless right and have WEP/WPA security enabled. If you don't, do so, or risk someone hacking your network from outside.

- G

 

[HKSturboKID]

Since both network meet in the Win2k box, why not sell the box for $100 and get a 16 port switch and have the same ip range all round. Save troubleshooting time in the long run and just put them in different workgroups, apply sharing and ntfs security.

 

[NightCrawler]

Do this:

1. Move the Wireless Router upstairs and attach the Hub directly to it with CAT 5 and then all the computers connect to the Hub.

2. The downstairs computers can use the wireless signal.

3. Change all the IP's to be on 192.168.0.0 and 255.255.255.0

There you have it a solid connection and no reason to use that Windows 2000 box as a bridge.

 

[Basse]

I would recommend not moving the wireless router because the signal would probably be poorer through the floor.

Just pull a cable from the Netgear to the Linksys.

Or is there any other reason why you have them on separate networks?

 

[NightCrawler]

Could just snake a cat 5 cable to the upstairs 16 port hub.

 

[Dowfen]

Get a switch with a built in layer 3 router or use Routing and Remote Access.


Eric