Cant connect to wireless access point via browser.

Printable View

Show 40 post(s) from this thread on one page

April 28th, 2004, 04:43 AM
riddellcomp

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
April 28th, 2004, 05:21 AM
riddellcomp

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 ?
April 28th, 2004, 05:34 AM
confus-ed

So I'm not really very happy with this answer, but I can't make it clearer !

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 !
April 28th, 2004, 05:43 AM
confus-ed

Quote:

Originally Posted by riddellcomp

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 ?

Oooo ! Where did that appear from !?!?

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..
April 28th, 2004, 05:57 AM
riddellcomp

Quote:

Originally Posted by confus-ed

Oooo ! Where did that appear from !?!?

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 ?

No not exactly. I connected the ap directly to the NIC in the pc and changed the Ip in the NIC properties to 192.168.0.210 as instructed. But I still couldnt see the AP, I couldnt ping it either. Therefore wouldnt the problem lie between the PC and the NIC as we have bypassed the router in this case?

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.gif
April 28th, 2004, 06:35 AM
confus-ed

Quote:

Originally Posted by riddellcomp

Yes and google tells me winsock is for win98/se only.https://forums.windrivers.com/images.../2007/09/1.gif

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 ..

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...
April 30th, 2004, 07:42 AM
riddellcomp

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.
April 30th, 2004, 09:10 AM
confus-ed

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 !!! :)
April 30th, 2004, 01:25 PM
NooNoo

Just for info you can RESET tcp/ip - which is not the same as uninstalling and reinstalling.
April 30th, 2004, 02:03 PM
confus-ed

Quote:

Originally Posted by NooNoo

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:

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.

I fixed up Riddlecomp already - only took 1/2 a million e-mails :D .. but Ta ! I hadn't sussed this one, bookmarked :thumbs:
May 1st, 2004, 09:25 AM
bbtech6650

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
May 1st, 2004, 09:31 AM
confus-ed

Quote:

Originally Posted by bbtech6650

Maybe i missed something....

Yup we know everything dude ! :) (or I like sometimes to think I do :D - but all the facts are now straight)..

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 ! :)

Show 40 post(s) from this thread on one page