Discussion Locked

Firewall Router in DHCP Wireless Network

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a wireless network setup using Cisco Aironet APs and Bridges. We use an omni-directional antenna broadcast to 10 different bridges which use uni-directional patches pointing to the main omni antenna. This wireless network is distributing DSLand internet access via a DHCP server. The DHCP server has a Cisco Router which is setup to forward only port 80 (HTTP). The WAN Web Gateway (DSL) is 192.168.0.102. The Subnet Mask is 255.255.255.243 which gives an IP range of 192.168.0.x . We also have a web server setup that the network can see through HTTP. All computers get internet access and connect to the web server fine except for one. This client can access the Internet but can't connect to the Web Server. This client has their internal network setup as follows:
They have a desktop PC with a NIC Card and a Laptop with a Wireless Card. Their Cisco Aironet Bridge is connected to a NetGear Firewall Router which is linked to a hub and an Access Point is connected to the hub (for the laptop). This router has a private and public setting. The private side is setup with an IP range of 192.168.250.x . So the PC has an IP address of 192.168.0.31. The PC can see the internet when it is setup to obtain IP address automatically. But itcannot see the Web Server which address is http://paddock. If we hook up the PC directly to the Cisco Aironet bridge using a crossover cable, they can now get both Internet and connection to the Web Server. Therefore, I think it is the router's firewall and it's private and public setup that's causing them to fail connection to the Web Server. But I don't know which settings to change on the Netgear Firewall Router to make it work if that is, in fact, what I have to do to get everything working. HELP!

Note: All other clients do not have a Firewall or router. They plug their Cisco bridge directly into their PC. They all work.

2 replies

by sgt_shultz

i am sure you have already tried this but can problem computer ping the webserver. if you can ping, why don't you just disable the firewall for a test if you think it is the problem...i don't know if this helps but the question i always ask myself with this stuff is, at each point, who (which server/device) do i need to talk to next? can I ping it? i only worry about one server/device at a time. don't have much personal bandwidth (smile). because it works if set to dhcp, examine gateway and subnet mask...what is set for the gateway on the problem pc...i am not sure i get that subnet mask of 255.255.255.243. not sure i get that it gives you 192.168.0.x. why not have it 255.255.255.0...

by michael_y_kim

Thanks for the suggestions but I have already done all that. The problem lies in the client. They want to keep their firewall up and running for security purposes. I guess it is me not knowing how to configure a Netgear Firewall Router. The gateway and subnet mask all get automatically assigned through DHCP. Looking in IPCONFIG, it is all okay there on the problem PC.

This discussion is closed to new replies.