On Fri, 07 Aug 2015 13:58:19 -0500, Char Jackson
wrote:
On Fri, 07 Aug 2015 04:31:34 -0400, Seymore4Head
wrote:
On Thu, 06 Aug 2015 23:28:24 -0500, Char Jackson
wrote:
On Thu, 06 Aug 2015 23:10:50 -0400, Seymore4Head
wrote:
I actually did start using my old router as another wireless point a
few days after I bought the new router by Googling this:
https://www.google.com/search?q=turn...utf-8&oe=utf-8
and I watched a couple of the videos and it worked.
I think I might be having problems with IP conflicts though.
Why do you say that?
I say that because I lost Internet. Tech support for ASUS had me walk
through resetting the router with everything unplugged and resetting
the router. I think the access point IP address is conflicting with
the range of IP addresses that are assigned to the other computers
connected to the 8 port switch.
Well, yes, obviously. I pointed that out in my first reply, quoted below.
What you originally showed was that the router is set to offer a DHCP scope
of 192.168.1.2 to 192.168.1.254, but your access point was configured to use
192.168.1.2, which is obviously inside the DHCP scope. Access points
shouldn't be configured to get their management IP via DHCP, so I
recommended moving the DHCP scope 'up' and out of the way of the
hopefully-statically-assigned access point IP.
One last thing. Windows seems to be pretty good about detecting duplicate
IPs and alerting the user. Did you see that warning?
For some reason I didn't see this post when it was posted. I happened
to see it in searching for my newest post that never showed up.
There is no warning from my machine when I boot the computer. It is
just not connected to the Internet. I can unplug the switch that is
connected to the access point and reboot and my computer will boot.
Since the access point is in my nephew's room and he works at night
and sleeps during the day, I really can't confirm if the access point
is working after that. All the other computers that are connected to
the switch work.
I did change the range to .100 to .199 that doesn't fix the problem.
I got everything up and working again and the last thing I plugged
back in was the wireless access point. Now after starting back from
a single computer plugged into the router, it will connect to the
Internet again.
http://imgur.com/AQGu8q6
You should enter values for Default Gateway and DNS Server. Normally, those
IP's would be the LAN IP for the router.
I have to figure what I should use for the IP ranges.
The DHCP range doesn't need to be that big, and in fact shouldn't be that
big. In your case, you need to at least exclude the IP address of the access
point, 192.168.1.2. I would suggest a much smaller range, for example .50 to
.99 or if you need a bigger range perhaps .100 to .199. Statically assign
the IP for the access point so that DHCP doesn't mess with it. Be sure that
DHCP is disabled on the access point! You never want two DHCP servers on the
same subnet.
I have the ASUS as the main router/wireless and it goes to an 8 port
switch and then it is connected to a 4 port wireless set up as an
access point.
Shouldn't I change the ASUS range to at least 100?
See above. At least move the DHCP range so that the IP for the access point
is outside of that range.
How do I find out what the IP range is for the 8 port switch?
Switches operate at Layer 2 of the OSI model. There are no IP addresses
there. Layer 2 switches are plug and play.
The access point is set up as 192.168.1.2
Fine, but get that IP out of the DHCP range and make sure DHCP is disabled
on the access point.