Wireless router, access point problem [routers configuration] [wireless router]
Q: Ok, so I try to work wirelessly on an existing LAN. The current system is already a router with DHCP on 192.168.1.1 It starts handing out addresses on 192.128.1.2
I tried to add a wireless router to use the system as an access point. I put the routers DHCP server and gave him a manual IP 192.168.1.150 When I plug a wired system in the router, then pulls an IP address on the Internet and works fine. I can also access the routers configuration page for that system. The wireless system is to see the wireless connection but can never be an IP address. If I manually select the wireless system provides an IP address of 192.168.1.151, it can connect to the routers configuration page, but it can not communicate with 192.168.1.1, or internet.
Does Does anyone know how I can setup to get working? Would it be easier if we have a simple wireless access point instead of turning a router into an access point?
Before trying this, I also tried connecting the existing network to WAN port on the router, and giving the router an IP of 192.168.2.1 with DHCP enabled. This enabled both clients to communicate with the router and the router was getting a valid ip 192.168.1.x on the WAN side, but customers still could not connect to the internet.
What am I missing here?
Re:Originally posted by: guy
And if the only problem is the lack of a DHCP request not going through, why can I not ping 192.168.1.1, but I CAN ping 192.168.1.150 when I manually set the IP to 192.168.1.151
Well if you set it manually you are not using DHCP. So based on what you have said the above is how it would act….
I am trying it both ways. DHCP is not going through. Explain to me that if when I set a manual IP, I can ping 192.168.1.150 but not 192.168.1.1 when they are both on the network. DHCP or not should not make a difference there.
Originally posted by: guy
I dont think that is the problem since a computer wired into the wireless router can access the internet, so the wireless router is definately talking to the wired switch/router
If a wired computer works plugged into that second device then a conversation about turning on/off NAT on that box is irrelevant. So without reading the entire thread again: Is your wireless client machine associated to the AP? Using XP's zero config utility or card utility? If your associated are you sending packets but not receiving perhaps?
Yes, the wireless client associates with the AP, but then times out trying to get an IP. I get the limited or no connectivity message after a little while. This is using the windows xp utility. I did not think to check packets since by manually setting the IP I could communicate with the router…
Re:I dont think that is the problem since a computer wired into the wireless router can access the internet, so the wireless router is definately talking to the wired switch/router
If a wired computer works plugged into that second device then a conversation about turning on/off NAT on that box is irrelevant. So without reading the entire thread again: Is your wireless client machine associated to the AP? Using XP's zero config utility or card utility? If your associated are you sending packets but not receiving perhaps?
Re:but wouldn't that setting break the wired connection also?
No, you do not need to do NAT to have conenctivity on a network.
And if the only problem is the lack of a DHCP request not going through, why can I not ping 192.168.1.1, but I CAN ping 192.168.1.150 when I manually set the IP to 192.168.1.151
Well if you set it manually you are not using DHCP. So based on what you have said the above is how it would act….
I also ask again, would it be easier if they just bought a standard wireless access point in terms of getting it setup. I'm thinking it may be, since that is what it is made to do, vs tricking a router into not being a router.
Either will work fine. It just your configuration with a AP is more plug and play. With a router you have to configure it properly.
V
Re:Where would one go to turn off NAT on a linksys router? That is a good point though, my D-Link has a setting, use this device as a router or a switch, and I did not see a setting like that on this Linksys.
However, and I could be wrong on this, but wouldn't that setting break the wired connection also? And if the only problem is the lack of a DHCP request not going through, why can I not ping 192.168.1.1, but I CAN ping 192.168.1.150 when I manually set the IP to 192.168.1.151 It is like the router isn't forwarding ANYTHING on the wireless link, but is on the wired links.
I also ask again, would it be easier if they just bought a standard wireless access point in terms of getting it setup. I'm thinking it may be, since that is what it is made to do, vs tricking a router into not being a router.
Re:I would make sure NAT is not turned on the second router and make sure the second routers WAN address is the ethernet port of the first router. I am unsure why it works wired and doesn't work wireless unless the router is smart enough to recognized the wired port but not the port the wireless conneciton is using. It also could be that that the DHCP broadcast requests are not being passed on over the wireless connection. This would mean two problems.
Re:Originally posted by: guy
May be this can Help: Using a Wireless Cable/DSL Router as a Switch with an Access Point (http://www.ezlan.net/router_AP.html)
:sun:
That's exactly what I did, and everything works except the wireless client can never renew it's IP automatically like it's supposed to. When I manually set its IP, it can talk to the router, but not the rest of the network. I know the wireless router itself is talking to the rest of the network because a client wired to the wireless router works.
Re:Originally posted by: guy
How are you uplinking the Router/AP to the first router? If the second device does not have auto MDI/MDX then you'll need to use a crossover cable from a switch port on the first router's switch, to switch port on the second. LAN ports on both. Tape the WAN port if you have to, you won't be using it on the second device. Apparantly you don't have connectivity between the two routers. Not having the correct cable or port would be my first guess.
I dont think that is the problem since a computer wired into the wireless router can access the internet, so the wireless router is definately talking to the wired switch/router
Re:put some bubble gum in the internet port of the wireless router, and use a normal port to connect it to the rest of the network.
Re:May be this can Help: Using a Wireless Cable/DSL Router as a Switch with an Access Point (http://www.ezlan.net/router_AP.html)
:sun:
Re:How are you uplinking the Router/AP to the first router? If the second device does not have auto MDI/MDX then you'll need to use a crossover cable from a switch port on the first router's switch, to switch port on the second. LAN ports on both. Tape the WAN port if you have to, you won't be using it on the second device. Apparantly you don't have connectivity between the two routers. Not having the correct cable or port would be my first guess.
Related posts
Tags: routers configuration, wireless router