Wireless Router, access point problem

[sswingle]

Ok, so I am trying to get wireless working on a pre-existing network. The current system already has a router using DHCP on 192.168.1.1 It starts handing out addresses at 192.128.1.2
I am trying to add a wireless router to the system to use as an access point. I turned off the routers DHCP server and gave it a manual IP 192.168.1.150 When I plug a wired system into the router, it pulls an IP address and works on the internet just fine. I can also access the routers configuration page with that system. The wireless system however see's the wireless connection, but can never get an IP address. If I manually give the wireless system an IP address of 192.168.1.151, it too can connect to the router's configuration page, but it cannot communicate with 192.168.1.1, or the internet.

Does anyone know how I can get this setup working? Would it be easier if we got a plain wireless access point instead of turning a router into an access point?

Before trying this, I had also tried connecting the existing network to the router's WAN port, and giving the router an ip of 192.168.2.1 with DHCP turned on. This allowed both clients to communicate with the router, and the router was getting a valid 192.168.1.x ip on the WAN side, but the clients still could not connect to the internet.

What am I missing here?

 

[ktwebb]

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.

 

[JackMDS]

May be this can Help: Using a Wireless Cable/DSL Router as a Switch with an Access Point

:sun:

 

[nweaver]

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.

 

[sswingle]

Originally posted by: ktwebb
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

 

[sswingle]

Originally posted by: JackMDS
May be this can Help: Using a Wireless Cable/DSL Router as a Switch with an Access Point

: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.

 

[Variable D]

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.

 

[sswingle]

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.

 

[Variable D]

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

 

[ktwebb]

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?

 

[sswingle]

Originally posted by: Variable D

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: ktwebb

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...