I 've had no problems in the past with multiple FW upgrades. However, I've just upgraded to 5.0719.0.2 from 4.0632.0.38 and cannot get a wi-fi connection to my Netgear router. Every time I try to open a web page I get: 'Web: No Gateway Reply'.
I've tried everything I can think of: a hard reset, re-running the FW update, deleting and then manually entering the network settings and entering the settings via the wlan wizard. All end with the same error message.
I'm out of ideas. Anyone?
Take a look at this post for further info instead of me rewriting it read all for good info. http://www.allaboutsymbian.com/forum//forum/thread/62463/
Thanks jet. I'm sure my settings are all correct though as I did a memory card restore after the upgrade. Also, even switching all the security off at my router doesn't help.
As v3 and v4 worked fine, I can only think v5 doesn't get on with my router. Anyone else had problems with a Netgear?
I'm no expert at setting up wireless networks, but I do have a Netgear router which works fine with my updated(latest) FW N80.
Just a idea...see if it works when you plug in the cable from your modem into a LAN port of the router instead of the "internet" port.
Finally sorted it. While I didn't have MAC filtering turned on, I did have a fixed IP address allocated to the N80. Re-entering the IP and MAC addresses fixed the problem.
Thanks for the suggestions.
hi guys i have the same problem with my upgraded n80 everytime i connect i get no gateway reply or wlan network not found..im connecting here at work secretly so i cannot change the router settings...anything i should change in my phone? because my officemate's laptop connects without doing anything just entering the wep key...thanks
You often get this issue 'No Gate Way found !'
Solutions to get rid of this.
- Reset your connection settings
- Delete the existing Access Point and Create all new (With Auto Settings).
- Wifi settings should be have Automatic Configuration Enabled
- Also Restart your NETGEAR Router / Wifi Access Point.
This should solve your problem.
-Even if this doesnt work ?
Try these advanced settings.
- Identify your NETGEARs config parameters.
- Your Network providers guide should be suffice
- Make Sure your NETGEAR is configured in Open Network mode
- No WEP/Security keys to be enabled.
- Identify the IP address of your NETGEAR router - Usually it would be of this sort - 192.168.XX.1
- In your N80 configure the NetGear Access Point -> Adavanced Settings -> IPv4 -> IPADDRESS = 192.168.XX.16 or something (Your Wifi Router Address and N80's IPV4 IP address should match except for the last 2 digits, can be set from the range of 2 to 255)
- Key in the Subnet Mask
- Set the Default gate way (Router Address - 192.168.XX.1 )
- Also set the DNS Address in your phone something like - 202.245.33.126 or some sort (If you are not sure set this as auto or this can be same as your default gateway).
If you are sucessfull in keying in the correct parameters., Your N80 would get connected for sure.
Another easiest way to get these settings is to connect a PC/Laptop to your NetGear router (through Wired LAN or WiFi)
Hit ipconfig/all from Windows XP Command Prompt.
you would get an info of this sort -
Physical Address. . . . . . . . . : 00-00-39-36-7C-E8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, August 10, 2007 9:28:53 PM
Lease Expires . . . . . . . . . . : Saturday, August 11, 2007 9:28:53 PM
Use the info you get from your PC/Laptop to configure your N80 and you should be all set !
Happy Researching 😉
:icon14:
Just updated to v5. Mine is working much like the former.
But I have the same boring problem of "NO WLan network found" sporadically and quite often appearing in the desktop scanner. Some connection drops but less frequently than WLan scanner failure.
Wi-Fi tx power still features 1 mW. Sad enough for me.
Anybody else?