01-29-2017 11:56 AM - edited 01-29-2017 11:59 AM
Solved! Go to Solution.
01-29-2017 12:08 PM
Use ethernet rather than wireless.. Wifi is junk science never intended for long term connectivity, just for portable devices in coffee shops... It's extension into a home / business enviornment, especially apartments, has been a disaster.
both operationally and security wise.
You need to turn off wps,
turn off any guest wifi.
St DHCP lease for a day not an hour.
Make sure the NTS is on and set to the proper time zone.
drives and printers must be static IP's
Set dhcp start to 192.168.1.100 , the gateway to 192.168.1.1 and start static IP devices at 192.168.1.99 on down, don't use 192.168.x.2- .10 they are an invalid user class for some.
Make sure you're onm a straight modem and not an all in one defaulting to NAT mode with a second router behind it.
01-29-2017 12:59 PM - edited 01-29-2017 01:03 PM
01-29-2017 01:33 PM
Sorry, that's all wrong.
It's why you're having issues with one device, and will with more.
The router is wrong. it can't work with a 192.168.1.2 addy.
if you're double NAT ing, it must be on 192.168.2.1 and your devices on that router 192.168.2.11 to .254 Again dhc[p and statics MUST NOT OVERLAP, and statics should be below the DHCP range.
You have devices in the .2 to .10 range
What's the WIFI extender doing? Extending wifi range to create a remote access point or is it actually a connection point for wired devices outside?
Is it cross band repeating or trying to repeat on the same channel?
01-29-2017 01:37 PM
Sometimes network cards go bad. a quick fix or cheep way to check is go to newegg.com or its like and get a USB wireless adaptor. They are very inexpensive. Put it in load software if needed and see if that works. Also could get a new nic card. Oh btw did you check the cable between the computer and the switch, change ports on the switch? any of these things can go bad, cables get squished etc.
Well thats my 2cents good luck
01-29-2017 01:43 PM
I think he's trying to do a NAT with the same addy on the wan and the lan side and in the x.x.x.2 to x.x.x.10 range withboth static and dynamic IP's in termixed...
Possibly 2 wireless ID's on the same channel and or with the same SSID's
01-29-2017 02:40 PM
My first thought is that you should not have powered off the shop network switch during your restarting sequence. I'm thinking your shop computer has an address conflict between the network DHCP source and the range extender device connected to it. The range extender is PROBABLY trying to act as a second DHCP source and is handing out a 192.168.2 xxx address to the shop PC.
Trying to build your own LAN addressing scheme is not trivial, especially when the LAN includes a range extender. Unless you are an IP networking guru, you should only have ONE router and ONE source of DHCP on your home LAN.
This is fairly easy to fix. Set what you called the 'primary router' to get its settings from the network (modem) and use DHCP in the router for all devices on the LAN. It is probably already doing that now.
Set all computing devices to get their IP addresses from the network DHCP source, which will be the 'primary router'. No more static address programming for you! If your router allows, set the DHCP to start at 192.168.1.11 or above (50 is fairly common in business).
01-29-2017 04:18 PM
He's got both static and DHCP so there needs to be room for the statics... The best practices are set up with the dhcp above the statics and yes, never use .0 to .10 for any user class devices. Apple devices are having issues with them as a known bug.
He may have only extended a single device via the IP addy assigned to the extender and that's why a device can't connect
The only available IP is already used up.
01-29-2017 04:26 PM - edited 01-29-2017 05:08 PM
Yup, and it was probably a cell phone or tablet. I 've never found a home that needed more than 30 static IPs reserved. My former employer always started large site DHCP at 50. They had room for 200 users, multiple printers, dual UPS, file servers, and network device monitoring. Oh, yeah, NEVER use 0 or 255, they are reserved for broadcast!
02-01-2017 07:24 AM