Attached Files:

Hey AttTio. Is your diagram correct?. I see the connection from the switch going to one pc that's wired and another that is connected wirelessly. What happens if you connect both pc's straight to the router?. You could have a bad switch or the cable between the router and switch is bad if you get no connection in Ethernet mode as shown

First time I've connected them with DHCP separately check the given IP, and make on the Wifi Router IP reservation - After connecting via LAN and Wifi there is an ALERT in Windows - "IP ADDRESS CONFLICT"

First time I've connected them with DHCP separately check the given IP, and make on the Wifi Router IP reservation - After connecting via LAN and Wifi there is an ALERT in Windows - "IP ADDRESS CONFLICT"

That's fine - - and we can broaden your knowledge and make this work for you. I asked

If my system wanted a share on another at 192.168.1.1, where would the packet(s) be routed?

Click to expand...

and the routing logic is:
1) if there's a specific route for the target address, use it
2) if not, send it to the DEFAULT route (that's the line shown as

Code:

0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.5 20

) The 192.168.0.1 is the router to which 192.168.0.5(my system) is attached. That will go to the modem and thence to my IPS - - clearly ping 192.168.1.1 will fail every time and I have no access to any devices attached to 192.168.1.1

So, we need to change the IP addresses to get them ALL on the same subnet
OR add persistent routes to solve the issue.

I've done this stuff for some time now and let me give you some guidelines

1) NEVER give a laptop a fixed/static address. Instead, set the router to
use the DHCP Reservation on its hardware MAC address. WHY? Because when you
take the laptop on a trip or just down to the local coffee shop, it will never
connect properly - - you coerse it to work on one and only one router - - yours.

2) If at all possible (meaning you can control ALL devices), use just one subnet
{eg 192.168.1.1} and let the router with this address control ALL dhcp assignments.
This means, if you have multiple physical routers daisy changed A->B->C,
then only ONE can make DHCP assignments ==>A and B,C should have DHCP disabled.

3) if you *must* tollerate connections from different subnets
{ 192.168.1.1, 192.168.2.1, 192.168.3.1 }, then you *MUST* learn to create
Persistent Routes.

{btw: a switch does not have an IP address and makes not DHCP assignments}

Thanks JOBEARD
I've got You
1, all the laptops has DHCP enabled, and Reserved IP om the Router
3, One subnet is enough (192.168.1.0)

If I set on
1a,
SERVER WIFI connected to Router IP: 192.168.1.110, subnet 255.255.255.0, Gateway: 192.168.1.1 same for the DNS
1b,
SERVER LAN connected through Switch to Router IP: 192.168.1.100, subnet: 255.255.255.0 (should I set Gateway or just leave empty?)

I've done this stuff for some time now and let me give you some guidelines

1) NEVER give a laptop a fixed/static address. Instead, set the router to
use the DHCP Reservation on its hardware MAC address. WHY? Because when you
take the laptop on a trip or just down to the local coffee shop, it will never
connect properly - - you coerse it to work on one and only one router - - yours.

2) If at all possible (meaning you can control ALL devices), use just one subnet
{eg 192.168.1.1} and let the router with this address control ALL dhcp assignments.
This means, if you have multiple physical routers daisy changed A->B->C,
then only ONE can make DHCP assignments ==>A and B,C should have DHCP disabled.

3) if you *must* tollerate connections from different subnets
{ 192.168.1.1, 192.168.2.1, 192.168.3.1 }, then you *MUST* learn to create
Persistent Routes.

{btw: a switch does not have an IP address and makes not DHCP assignments}

So
the base idea was:
1, Connect all computer via Wifi to the Router (internet)
2, Connect SERVER and WORKSTATION(s) via LAN together
(I'm running FreeNAS on the server as a VM, it needs to have LAN connection to work
and needs Internet access too)

IP: 192.168.1.110, subnet 255.255.255.0, Gateway: 192.168.1.1 same for the DNS

Click to expand...

and I surmise they work well.

Switch to Router IP: 192.168.1.100, subnet: 255.255.255.0 (should I set Gateway or just leave empty?)

Click to expand...

hmm, the gateway address is missing??? DNS too?
NOT GOOD and you should not be required to manually intervene.
Try this on one LAN attached box - - directly connect it to the router itself.

Really strange - - never seen a router act differently due to wifi vs lan connection, so I would point the finger at the LAN driver(s) needing updated firmware.

Without a gateway, packets go nowhere; without a dns address, you can ping an ip address, but will never resolve a domain name (eg google.com) to its address for a browser to connect (btw: google.com has several IPs and one is 74.125.239.6