Web pages not accessible

[#1]

Hello everybody!! I' m setting up a FortiWifi 50B as an access point with firmware version 3.00-b0568(MR5 Patch 3) inside a college network. The FG50B is plugged into another wireless router via its WAN1 interface (also known as its default interface to the external network) with a configuration of 192.168.30.x/24 network. I' ve also configured the internal interface with a 192.168.1.x/24 network. Only one computer is plugged into the internal interface. In order to route all the traffic from the internal interfaces into the WAN1 interface I' ve created a static route setted up as it follows: 0.0.0.0/0 and I added the right default gateway address. My current system information is: Operation mode: NAT HA status: Standalone I' ve also configured my firewall policies, the current configuration for all the traffic is: Source: all Destination: all Schedule: always Service: any Profile: unfiltered Action accept and I' ve tried both, enabling and disabling the NAT option inside the firewall policies. This is how the network looks like: PC1-----|FG50B|-------|TRENDnet router|------|College Network|------|Internet| PC2_______________________| For the moment my issues are related to the web access, since I can ping the computers inside the local network (PC1 & PC2) and the intermediary devices (50B, trendnet) When trying to access a webpage for example google.com or any other website, it doesn' t work... Since I' m new to this kind of hardware, my knowledge of the settings for the 50B is limited so I' ll be grateful if someone could give me some help on this issue. (sorry if I' m missing some vital information that could be useful.. I dont know quite well what to post )

[rwpatterson]

Using your diagram, the FWF50B should get an IP via DHCP from the Trendnet on the WAN interface. In the settings you should click the check box to allow the default gateway to be set from DHCP. Also you should allow DNS forwarding from internal and WLAN if your using the FWF50B to serve DNS queries. Try a PING from the workstation to a known good Internet IP address (4.2.2.1). If this does work, it' s strictly a DNS issue. If this fails, then you have another routing issue you need to sort out. Post back with more info, and we' ll see if we can' t make this fly....

[#3]

Thanks for the answer rwpatterson, The FWF50B indeed got its IP with the DHCP setting and I made sure the DNS forwarding options for WLAN & internal were checked. I tried to Ping www.google.com and the DNS seemed to be working since it resolves the google' s domain name and gives the following IP address (209.85.229.147) the down side is that the packets sent to the server are timed out or unable to reach their network destination. I' ve also tried to execute a Traceroute command and realized that it dies after it goes two hops away from the trendnet (probably a DMZ...Proxy...??) I' ve checked the browser configuration that PC2 uses to connect to the internet via the trendnet (using Mozilla Firefox) and it has a predetermined HTTP Proxy with an IP address of 192.168.1.1 and port number of 800. My actual configuration with PC1 to access the FG web interface is set as a direct internet connection (with the same browser) otherwise if I use the proxy settings it wont work. Once again here is my diagram: PC1-----|FG50B|-------|TRENDnet router|------|College Network|------|Internet| PC2_______________________| This information may seem basic but I' ve only finished my beginner training on networks and I apologize if the answer could be right there but a lot of stuff isn' t clear to me... yet!

[rwpatterson]

The only thing I can think of is maybe the network between the trendnet and the FGT is the same as on the WLAN side of the FGT. 192.168.x.x. If this is the case, change it (WLAN side), and you should be good.

[#5]

Thanks for the advice rwpatterson, but the problem was the web proxy from the college network. I asked one of the teachers and he told me that the other people trying to configure different kinds of devices had problems with that proxy. He gave me a more direct (and also less filtered) proxy address and it worked. I only had to change the proxy address (& port) inside the browser configuration on PC1 and here I am writing this reply

[rwpatterson]

Very nice. Thanks for the follow up.