Cant connect to wireless access point via browser.
Page 1 of 2 1 2 LastLast
Results 1 to 15 of 27

Thread: Cant connect to wireless access point via browser.

  1. #1
    Registered User
    Join Date
    Oct 2003
    Location
    Western Australia
    Posts
    737

    Cant connect to wireless access point via browser.

    I have a netgear wg602 wireless access point which is connected to a 4 port adsl router. However I am unable to access the wg602 setup page via a browser. Is this something that I should be setting up in the routers properties page? If so what exactly am I looking for?

  2. #2
    Geezer confus-ed's Avatar
    Join Date
    Jul 1999
    Location
    In front of my PC....
    Posts
    13,087
    ... yup the connected router needs to know what the ap is using as its internal ip & allow it, & it be also inside its scope {allowed Ip range} (so whatever ip you are trying to access has to be that set in the ap by default, you can't generally change it)

  3. #3
    Registered User
    Join Date
    Oct 2003
    Location
    Western Australia
    Posts
    737
    Can you run that by me again, Im confus-ed.?

    How do I tell the router what IP the ap is using?

    Under the dhcp server in the modem properties the defined start address is 192.168.1.100 and the end is 192.168.1.149. Is this where I would change the range to match the ap address?

  4. #4
    Registered User DsLTech's Avatar
    Join Date
    Sep 2002
    Posts
    32
    Quote Originally Posted by riddellcomp
    I have a netgear wg602 wireless access point which is connected to a 4 port adsl router. However I am unable to access the wg602 setup page via a browser. Is this something that I should be setting up in the routers properties page? If so what exactly am I looking for?
    Have you tried browsing to the name of the access point? It should be printed on the bottom of the AP. If the AP is not pulling an IP from your router the AP's default IP is 192.168.0.227, you can try browsing to it directly. You should not have to change your dhcp server range to match the AP, the AP should pull an IP automatically to match what is already configured in the dhcp server of the router.
    Try doing an IPCONFIG /ALL to see if your pulling an IP address and to check the address of the default gateway.
    Last edited by DsLTech; April 27th, 2004 at 06:50 AM.

  5. #5
    Geezer confus-ed's Avatar
    Join Date
    Jul 1999
    Location
    In front of my PC....
    Posts
    13,087
    .. yeah my answers do that sometimes, I forget who understands what

    So.. what I'm saying is that your ap will have a set ip, (the address you can't get to) - that needs to be inside the scope (IP range) of your allowed internal adresses - where it can get mucked up is when you have dhcp enabled as automatic on your router (never mind if its enabled on the ap too !) .. so you can't extend the range of 'allocatable by dhcp' ip's, as your ap has one & it won't use another (generally), so if you put it in that scope it won't get allowed anyway - there are ways around this if static IP is no good (but this ones confusing enough already, so one step at a time) ..

    So if you only have a 'few' client machines (I suspect this is at home ? so not loads ?) then try with static IP so you know what the hell is going on .. confine your efforts to just one beast on the ap for now ..

  6. #6
    Registered User
    Join Date
    Oct 2003
    Location
    Western Australia
    Posts
    737
    Quote Originally Posted by DsLTech
    Have you tried browsing to the name of the access point? It should be printed on the bottom of the AP. If the AP is not pulling an IP from your router the AP's default IP is 192.168.0.227, you can try browsing to it directly.

    yes I have tried both. Netgear 5bccXXXX (not sure of the rest as its in a friends office and Im at home.) and also http://192.168.0.227

    But no luck with either.

  7. #7
    Registered User
    Join Date
    Oct 2003
    Location
    Western Australia
    Posts
    737
    Quote Originally Posted by confus-ed
    .. yeah my answers do that sometimes, I forget who understands what

    So.. what I'm saying is that your ap will have a set ip, (the address you can't get to) - that needs to be inside the scope (IP range) of your allowed internal adresses - where it can get mucked up is when you have dhcp enabled as automatic on your router (never mind if its enabled on the ap too !) .. so you can't extend the range of 'allocatable by dhcp' ip's, as your ap has one & it won't use another (generally), so if you put it in that scope it won't get allowed anyway - there are ways around this if static IP is no good (but this ones confusing enough already, so one step at a time) ..

    So if you only have a 'few' client machines (I suspect this is at home ? so not loads ?) then try with static IP so you know what the hell is going on .. confine your efforts to just one beast on the ap for now ..
    So what would I change in all of this??

    IP Address Subnet Mask DHCP Server Disabled Enabled DHCP address pool selection System Allocated User Defined User Defined Start Address User Defined End Address DHCP Gateway Selection Automatic User Defined User Defined Gateway Address

  8. #8
    Registered User
    Join Date
    Oct 2003
    Location
    Western Australia
    Posts
    737
    That didnt look like that when I pasted it in. Here it is again.

    LAN CONFIG

    Ip address 192.168.1.1


    DHCP Server: enabled

    DHCP address pool selection: system allocated

    User defined start: 192.168.1.100

    end: 192.168.1.149

    DHCP gateway: Automatic

  9. #9
    Registered User
    Join Date
    Oct 2003
    Location
    Western Australia
    Posts
    737
    Oh and just to add this setup will be just one pc in the office and his daughters laptop connected up via wireless.

  10. #10
    Geezer confus-ed's Avatar
    Join Date
    Jul 1999
    Location
    In front of my PC....
    Posts
    13,087
    Ooooo ! stop posting while I'm mid answer !

    Whats the IP of the AP ?

    Is that within the scope of the router ? (look in your router manual for what it'll most likely describe as 'private IP' range)

    What I was suggesting is/was that you turn off DHCP completely & assign each client manually, but I dunno how many machines link off the router so I dunno how practical that might be, if this router links into a big fat network then it won't be at all ..

    Alternatively check the AP is in scope of the router & your DHCP pool, but make sure the AP's fixed IP isn't part of the pool .. (I still get the feeling this isn't making overly much sense to you .. ? ).

  11. #11
    Registered User
    Join Date
    Oct 2003
    Location
    Western Australia
    Posts
    737
    Quote Originally Posted by confus-ed
    Ooooo ! stop posting while I'm mid answer !

    Whats the IP of the AP ?

    192.168.0.227

    Is that within the scope of the router ? (look in your router manual for what it'll most likely describe as 'private IP' range)

    I will check my mates router in the morning.

    What I was suggesting is/was that you turn off DHCP completely & assign each client manually, but I dunno how many machines link off the router so I dunno how practical that might be, if this router links into a big fat network then it won't be at all ..

    There is only one machine off this router at the moment and a laptop via wireless if we ever get this going.

    Alternatively check the AP is in scope of the router & your DHCP pool, but make sure the AP's fixed IP isn't part of the pool .. (I still get the feeling this isn't making overly much sense to you .. ?
    Okay maybe that last bity confus-ed me a tad
    DSLtech,

    I will also do a ipconfig /all and see what it tells me. Thanks.

  12. #12
    Geezer confus-ed's Avatar
    Join Date
    Jul 1999
    Location
    In front of my PC....
    Posts
    13,087
    okay lets see if a practical example can clear the last bit up for you, when you understand stuff it gets so much easier

    So just making a load of numbers of lets say ..

    Your ap has its actual ip 192.168.0.227

    Lets then say your router has a private address range of 192.168.0.1 to 192.168.0.255 (that's what most have) .. so automatic dhcp won't /can't work for your AP if the 'pool' range is all of it, (as its got a fixed ip - if you let it use the whole range it'll try to dynamically allocate maybe the Ap's 'set' ip which is gonna break it), so x.x.x.1 - x.x.x.255, you'd either need to set your AP's Ip outside that range which is no damn good as your router can't see it then, or make the 'pool' not include our 'fixed ip' or as I said set them manually (use static ips)..

    I dunno whether that's any clearer than the last time (this is like many things in life once you 'get it' you wonder why the hell it was apparently so hard, but until you do ...)

  13. #13
    Registered User
    Join Date
    Oct 2003
    Location
    Western Australia
    Posts
    737
    Quote Originally Posted by confus-ed
    okay lets see if a practical example can clear the last bit up for you, when you understand stuff it gets so much easier

    So just making a load of numbers of lets say ..

    Your ap has its actual ip 192.168.0.227

    Lets then say your router has a private address range of 192.168.0.1 to 192.168.0.255 (that's what most have) .. so automatic dhcp won't /can't work for your AP if the 'pool' range is all of it, (as its got a fixed ip - if you let it use the whole range it'll try to dynamically allocate maybe the Ap's 'set' ip which is gonna break it), so x.x.x.1 - x.x.x.255, you'd either need to set your AP's Ip outside that range which is no damn good as your router can't see it then, or make the 'pool' not include our 'fixed ip' or as I said set them manually (use static ips)..

    I dunno whether that's any clearer than the last time (this is like many things in life once you 'get it' you wonder why the hell it was apparently so hard, but until you do ...)
    Yes I think ive got it now.
    The router automatically assigns IP addresses to the client machines that join the network?

    But.....As the ap has its own ip which it must always use it tells the router, "I dont want your lame IP address I have my own."
    So the router then syas "Fine well don't think your using your ip address around here. Take your bat and your ball and your IP address and go home." So the AP does exactly that.

    Okay so you say to assign static ip addresses which should be easy as I only need to assign one for the server pc and one for the AP as that is the only thing connected to the network (Then the lappie connects to that)
    Would I do that under the dhcp settings page.

    Im assuming that I change this setting: DHCP address pool selection to "User defined." But then where do I enter the Ip addresses? And also what about DHCP Gateway selection? Do I change that to user defined also.

    Thanks again.

  14. #14
    Geezer confus-ed's Avatar
    Join Date
    Jul 1999
    Location
    In front of my PC....
    Posts
    13,087
    You set static ips on the clients themselves not in the router - so in xp you find your connection in Network connections, right click, properties, then you get a box called Local area connection properties, & then you click on TCP/IP & click its property button - finally you get a box IP properties & its blindingly obvious what you do from there (type the flipping Ip you want in the box ! ) to return it to 'automatic from dhcp server' you just click the obtain automatically check box.. (if its 98 the instructions are pretty much the same)

    DHCP gateway selection should be already 'automatic' & leave it that way ..

  15. #15
    Registered User
    Join Date
    Oct 2003
    Location
    Western Australia
    Posts
    737
    Okay Im with you now.


    Actually the pc store that I brought the AP from got me to check the tcp/ip properties and said that they were correct at "Obtain automatically." He said it was a winsock error that was causing problems.

    So if the IP of the AP is 192.168.0.227 then I would set the IP of the client machines to 192.168.0.228 and 192.168.0.229 and so on and so forth.
    And subnet mask to 255.255.255.0 as is the AP.
    YES????

Similar Threads

  1. Fastest wireless access point I've ever seen
    By Damned Angel in forum Tech Lounge & Tales
    Replies: 5
    Last Post: January 20th, 2014, 08:53 AM
  2. Replies: 5
    Last Post: January 10th, 2004, 11:54 PM
  3. Wireless Ethernet Bridge vs. Wireless Acess Point
    By Low_Level_Owl in forum Tech-To-Tech
    Replies: 2
    Last Post: February 14th, 2003, 11:50 AM
  4. Wireless Access Point / Cable Router Combo Suggestions
    By KCarter335 in forum Networking
    Replies: 12
    Last Post: January 28th, 2002, 11:17 AM
  5. [RESOLVED] W2K SP2??
    By Bjorn in forum Windows NT/2000
    Replies: 3
    Last Post: February 17th, 2001, 12:58 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •