Printable View
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?
... 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)
Can you run that by me again, Im confus-ed.https://forums.windrivers.com/images.../2007/09/1.gif?
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?
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.Quote:
Originally Posted by riddellcomp
Try doing an IPCONFIG /ALL to see if your pulling an IP address and to check the address of the default gateway.
:) .. 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 ..
Quote:
Originally Posted by DsLTech
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.
So what would I change in all of this??Quote:
Originally Posted by confus-ed
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
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
Oh and just to add this setup will be just one pc in the office and his daughters laptop connected up via wireless.
Ooooo ! stop posting while I'm mid answer ! :devil:
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 .. ? ).
DSLtech,Quote:
Originally Posted by confus-ed
I will also do a ipconfig /all and see what it tells me. Thanks.
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 :rolleyes: (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.Quote:
Originally Posted by confus-ed
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.https://forums.windrivers.com/images.../2007/09/1.gif
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.
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 ! :D) 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 ..
Okay Im with you now.https://forums.windrivers.com/images.../2007/09/1.gif
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????
Okay things arent getting any better. If I try to change the IP address of the NIC to anything but "Obtain ip auto..." I cannot access the internet.
Heres the settings..
Windows IP Configuration
Host Name . . . . . . . . . . . . : office
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-40-05-0E-02-5F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.12
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. . . . . . . . . . : Wednesday, 28 April 2004 5:30:14 PM
Lease Expires . . . . . . . . . . : Saturday, 1 May 2004 5:30:14 PM
Okay I connected the AP up directly to the NIC and changed the IP to 192.168.0.210, as per the install instructions just to test it. However I was unable to connect to the ap in a browser. I could not ping the Ap either.
When the ap is connected via the router and I change the IP of the NIC from "obtain auto..." I cannot access the internet at all. I have to chnage it back to "Obtain auto..." in order to get internet access.
I had to restore this computer froma ghost copy (thats another story) and when it first booted up the NIC drivers werent installed properly. I cant remember the exact order of things but at one stage I was able to get to the AP config page. However after a reboot I couldnt anymore. Can I assume the problem lies within the NIC ?
Right so that was always gonna happen ! He says so very helpfully after it has - & I should have explained more :rolleyes:
What I want to get to first is all your machines talking to each other, then we can worry about cloning mac addresses & the like to fool your ISP's connection into thinking its connected to just the machine that originally connected to it ..
When you originally make an account with an ISP it looks for a thing called a MAC address (Media Access Control) which is a unique number associated with your NIC (network interface Card - it shows in your post as 'physical address' 00-40-05-0E-02-5F), so what needs to happen here is that the router which is the first point in our inward connection chain, needs to have the MAC address cloned, if it works all ok with 'automatic' then that's been done before ..
What looks to be happening here is that we still haven't got all the settings in the ap right, because that needs to be talking to the router which we still don't seem to have..
Subnet value wants to be the same on all machines regardless (we haven't got lots & lots of machines here so we can cease to worry about that - as long as they are all the same).
Now I just read the bit about 'winsock' ... so lets eliminate that one completely shall we, because it might be causing it (I hate this remote control business, because I can't 'see' everything in real time & guage whats happening ! Grrr ..)
So what operating system do we want a 'winsock fix' for ? (you might maybe google this yourself & save a reply ? ;))
BTW the IPs whether they be fixed or dynamic NEED to be inside the scope of what the router can see & that includes the AP (So all the machines/router/ap want to be using the same range x.x.x.1 to x.x.x.255, your AP is using 192.168.0.227 so your adress range for your router needs to include that so it wants to be able to see 192.168.0.x & not be the same as any other machine already connected to our router)
There's two lots of things going on here which is why its so flaming confusing ! There's connecting to the internet via our cloned mac address in your router & there's getting all the machines on your network to see each other..(effectively two lots of network !)
Try all of that & lets see if we make some progress !
Oooo ! Where did that appear from !?!?Quote:
Originally Posted by riddellcomp
I'm not very sure I understand this - you connected the ap directly to a pc & managed to change its IP to 192.168.0.210 ? Via the browser pages you can't get to any other way ? - Then when you connect that to the router you can't see it anymore ?
So like I said above is that number in your routers range of IP's - so what's the address of the router ?
For the sake of clarity perhaps you might knock up a diagram showing what's connected where with what IP's identifying /naming the machines for reference ? 'Cos I'm getting 'extra' confus-ed :D ! - which ain't good..
Yes and google tells me winsock is for win98/se only.https://forums.windrivers.com/images.../2007/09/1.gifQuote:
Originally Posted by confus-ed
So bearing in mind our recent bit of pm'ing ;) (we'll do that bit by mail to avoid he said, she said, you said, I said - which is most confus-ing !) .. I'm just answering this bit quickly for reference mostly for 'others' - try looking for 'winsock fix' - its to do with the fact that you can't really uninstall / reinstall TCP/IP in windows XP - the 'standard' M$ answer being a re-install of windoze ..Quote:
Originally Posted by riddellcomp
When/if we get it all going I'll come back & attempt to answer any outstanding stuff :) & see if we can get a straight answer ! Instead of all these assides...
Well I finally got this working thanks to the generosity and help from Confus-ed.https://forums.windrivers.com/images.../2006/04/1.gif
However I will let him explain the technicalitys for those that might face similar problems as he knows more about what hes talking about.
So thanks for the thanks which is always much appreciated :)
So what the hell made this thread so hard then ?
Riddellcomp only had once pc, one laptop, one router & one wireless AP - first I'll say (as he knows already ;)) he got the 'wrong' stuff & made it hard for himself - what he really wanted for this was just a combined AP/router - so wireless plus some lan ports - then he'd have only had to worry about one lot of 'scope' ...
Here he had a router on 192.168.0.1 for its IP & his AP was on 192.168.1.277 -well 'crappy' routers (the ones you can buy for home use without raising a mortgage at the bank) generally have a limited 'scope' (I will explain that word eventually, honest !) & thus can only generally address one hex couplet in our IP..
WTF ? I hear you cry - what's sex, I mean Hex :D, got to do with the price of wet fish on a Monday, huh, then 'ed ?
Well IP's are made up of 4 pairs of hex couplets that are most confusingly written in dinary, that's decimal to you 'old' folks like me, but Hex is base 16 (so 10 in dinary/decimal is written as A, 11 is b .. f is 15) so if you see an IP ending '.255' that's really ending ff .. yeah, yeah, yeah, ff & get to the point ! .. the point is all these home routers have limited scope & can only see the end range of all the couplets - so in English that means 'generally' they can 'see' 255 different addresses .. (the 'end' 255, so x.x.x.1 - x.x.x.255 inclusive)
So here Riddlecomps Router can only address devices which have an IP 192.168.0.1 - 192.168.0.255 - ah but his AP is 192.168.1.277 - its 'scope range' don't fit - so no damn good !
After much hoo-hah & muttering about subnets & other such distractions, we got the message through, & after a further bit of persistence from Riddlecomp he finally got the AP's 'fixed' IP 'unfixed' (by reprogramming it via its browser set-up pages) & inside our routers 'scope' & hey presto, bobs your uncle & fanny's your Aunt & many more unintelligable phrases, coming out to mean success, we have a working network .. yay !!! :)
Just for info you can RESET tcp/ip - which is not the same as uninstalling and reinstalling.
Errrrrrrrrrrrr did you post this one in the right window ? or are you on about toasty winsocks still & can't re-do tcp stacks & stuff - you must be .. :) -Quote:
Originally Posted by NooNoo
I fixed up Riddlecomp already - only took 1/2 a million e-mails :D .. but Ta ! I hadn't sussed this one, bookmarked :thumbs:Quote:
The NetShell utility (netsh) is a command-line scripting interface for the configuring and monitoring of Windows XP networking. This tool provides an interactive network shell interface to the user.
In Windows XP, a reset command is available in the IP context of the NetShell utility. When this command is executed, it rewrites pertinent registry keys that are used by the Internet Protocol (TCP/IP) stack to achieve the same result as the removal and the reinstallation of the protocol.
Maybe i missed something.... Do we know for a fact that the ip address of the AP is x.x.x.127?
What I do when i cannot find the ip address of a dhcp client is I use an ip scanner to scan my range of ip addresses...
I use this one... http://ipscan.sourceforge.net/ipscan.zip
hope this helps!
bb
Yup we know everything dude ! :) (or I like sometimes to think I do :D - but all the facts are now straight)..Quote:
Originally Posted by bbtech6650
Riddlecomp & I had a sub-comittee meeting & a barrage of e-mails flowed betwitx us :D, he's now a happy bunny & everything is working as it should ! ;)
But thanks for taking an interest ! :)