NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Shadeclan
Sep 17, 2013Aspirant
WG602v3 Login Problem
I had my WAP connected to a WinXP machine and, with a little difficulty, was able to log into it and set up security. I recently converted over to Kubuntu - I'm running v13.04. I was able to get the WAP to work OK, that is, people were able to access the Internet through my Kubuntu box, but I can't log in to change any of the security settings. When I type in the IP address, the browser just spins and the attempt times out.:(
Can someone please give me a clue as to what I'm missing and how I might gain access to my WAP - thanks.
Can someone please give me a clue as to what I'm missing and how I might gain access to my WAP - thanks.
9 Replies
- jmizoguchiVirtuosoAssuming you have two nic right?
I would think still should able to access from your Linux box - ShadeclanAspirant
jmizoguchi wrote: Assuming you have two nic right?
I would think still should able to access from your Linux box
You assume rightly - one to the cable modem and one to the WAP.
I should still be able to access the WAP - it's a webpage for cryin' out loud - but everytime I put the IP address in, it just sits there and times out. - jmizoguchiVirtuosoIf you connect to wifi can you still still login or not?
- ShadeclanAspirant
jmizoguchi wrote: If you connect to wifi can you still still login or not?
I've never been able to login to the WAP with a computer connected to it by WiFi - I've only ever been able to login to it through the wired connection. - jmizoguchiVirtuosoBut when AP is behind the 2nd NIC of the PC you can not access it right?
- ShadeclanAspirant
jmizoguchi wrote: But when AP is behind the 2nd NIC of the PC you can not access it right?
No, I can't log into it. The popup box doesn't even come up. - jmizoguchiVirtuosoAssume dhcp on 2nd and AP device ip on same LAN subnet?
- ShadeclanAspirant
jmizoguchi wrote: Assume dhcp on 2nd and AP device ip on same LAN subnet?
The NIC facing the ISP is on one subnet and the NIC facing the WAP is assigned a different subnet - the ISP seems to be doing the assigning.
Neither IP address is anywhere close to 192.168.0.227, the default IP for logging into the WAP, but it wasn't a problem before with the WinXP setup - the IP addresses for the NIC cards were set by the ISP, same as now. - ShadeclanAspirant
jmizoguchi wrote: Assume dhcp on 2nd and AP device ip on same LAN subnet?
Fixed it! I set the NIC facing the WAP on "manual" and gave it an IP address of 192.168.0.226. Doing so allowed me to log into the WAP but prevented access thru the Linux box to the internet. I changed the WAP IP address to the max IP address of the subnet being assigned by my ISP to the facing NIC when it was set to "shared". I then set the NIC back to "shared" and volia!
Thanks for putting me on the proper trail!:D