wireless and lan segments not talking

[comptech]

scenario

windows pc 1 connected by wireless on ip 192.xx.xx

windows pc 2 connected by ethernet on ip 198.xx.xx

linux file server connected by ethernet ip 198.xx.xx

all are in the same domain so privileges aren't an issue

pc1 can browse the network and see the file server but cant access the file server
pc2 can browse the network and see and access the file server


i have no control over the configuration of the wireless access point that issues the 192.xx.xx ip

any suggestions am open to

being racking my brain

[khat17]

Depending on your setup you may have to set the requisite options to bridge the networks. The IP ranges differ and some devices/boxes may isolate each range/bank. Find the option for bridging and you should be fine.

[jamrock]

windows pc 1 connected by wireless on ip 192.xx.xx

windows pc 2 connected by ethernet on ip 198.xx.xx

linux file server connected by ethernet ip 198.xx.xx

192.xx.xx.xx is on one network segment and 198.xx.xx.xx is on another network segment. By themselves, network cards cannot communicate with cards that are on other segments.

Can you change the machines on the 198.xx.xx segment to 192.xx.xx.xx addresses?

If not, you will need to put a router between both segments. A router has at least 2 network cards. In your example, one network card would have a 192.xx.xx.xx address and the other would have a 198.xx.xx.xx address. Network packets would travel though one network card into the router and out through the other network card.

If you have an old computer, you can use Pfsense or Smoothwall to act as a router. Both products were designed to provide routing/firewall services between the internet and a LAN. However, you can disable the firewall and use them between network segments.

http://www.pfsense.org/
http://www.smoothwall.org/

[ruption]

We know that the wireless router is issuing the 192.xxx.xxx.xxx range, but what is issuing the 198.xxx.xxx.xxx range?

[kilaj1]

If i recall correctly you can also use the route add command, not sure if it will work in your case but i did this across VLANs and it worked

[khat17]

Thinking about it again - aside from the bridging - you could just disable DHCP on one of the devices - like the WIFI router - and let all DHCP be controlled by a single source. This way the router just acts as a media converter from copper to wireless.