seriously, its takes ages to connect to home and office wireless networks.
whats with the usability logic of all these hidden pop-up windows that you find but cant remember how to get back into again, like thing > properties > thing > properties > advanced > thing > properties > REALLY VITAL SETTING BURIED HERE AND CALLED SOMETHING UNINTELLIGIBLE AND LOOKING UNIMPORTANT!
WTF am i meant to get a degree in IT just to connect to the fucking internet?
First step -Does your router filter its wireless by mac addresses (hides itself from everyone except certain chosen computers you have told it are ok) If yes - then you are now finding the mac address of the PC to put into the router so the wireless network can be seen by the PC - had to do some command line thing RUN > cmd > ipconfig /all
got the mac address, aka 'Physical address' put into the router.
Now, can see the wireless network showing up in the 'wireless network connection' > 'choose a wireless network'
select it, click connect, put in the WPA network key /password.
Now its just hung on 'Acquiring Network Address'. This I havn't seen before.
Looking in forums,
-tried some cmd flushdns thing, didnt work.
tried run > services.msc > dhcp cleint > its not stopped or disabled, its 'started' and 'automatic'. restarted it anyway but no fix.
-also have gone to 'network connections' > right click 'wireless network connection icon' > properties > general > Internet Protocol TCP/IP > properties > and yes it is set to 'obtain IP address automatically' and 'obtain DNS automatically'.
IT Does say here - ask your 'network administrator' for appropriate IP settings... This is a clue, perhaps it just cannot get the settings and we need to manually imput them. Fine. What are the settings then...
Now in a window I can't remember how to get back to, I saw that the computer was not being assigned an IP address, it was 0.0.0.0 also submnet mask, default gateway bla bla etc all blank. So I see the PROBLEM, is that the router? or whatever, the computer is not getting its IP address for some reason.
So - we need to either figure out WHY its not getting assigned an IP address, or find out how to give it one that will work. option 2 sounds less time consuming.
well fuck me - the WPA password I typed was wrong. So instead of saying "WRONG PASSWORD try again", its says "ACQUIRING NETWORK ADDRESS" WTF WTF WTF WTF?? this feedback is so illogical... its NOT doing what it says because the password is wrong. why would it say its doing something when it is NOT. Grrrrr I just went on a big google forum trail search for nothing, because the wrong feedback is given.
heres a huge thread on other possible fixes for the same problem
----heres some more fixes anyway for next time this error message happens but for a different reason. Its amazing how many possible fixes there are for this error.
Because when I re-entered the WPA shared key for my home network (open the Wireless Network Connection Status / click on Properties / Select the Wireless Networks tab / select the relevant network from the list under “Preferred Networks” / Select properties / Re-enter the Network Key — note: I found my network key in my router's settings after connecting by wire to the router and visiting 192.168.2.1 — the IP depends on your router), … then all was immediately solved. I had tried many of the things suggested above without any luck.
---
I had the same problem that began right after I renewed my Trend Micro subscriprion for another year. Turns out Trend Micro installed the “Trend Micro Common Firewall Driver” which was causing this. I found this in the network connection properties and duly uninstalled it.
After rebooting the problem was gone for good!
---
If you are trying to connect to a wireless network with win xp and hangs on “connecting to network” it may be the MAC filter on the router.. You must add your wireless adapters MAC to this list before connecting..
---
I think that the last explanation I found a few months sounds plausible in my case. The D-Link router doesn't refresh its address table unless you turn it off and on. That means you have to always go to your router and turn it off in order to reconnect your computer. This is beause Microsoft is more closely aligned with the wireless spec than D-Link is.
---From what I read, the problem we are experiencing is often caused by two points: many routers only reset their DHCP wireless connections upon reboot of the router, 2) windows xp sp2 has follows security protocols more stringently and therefore cannot circumvent #1. The simple solution for me was to use the Alternate DNS configuration tab in Windows XP, which will use some default settings if the IP address is not acquired. This takes a bit longer, because the computer sits tries to first acquire the IP address using DHCP, and only then uses the Alternate Configuration, however, this has worked without any problems. The other option may be to get another router, one which resets the wireless DHCP connections more frequently, but I don't know which routers have this problem, and which don't.
ok round 2: pc internet virtual pc 2007 fuckedness (or AIRFOIL (AIRTUNES?) CAN BREAK YOUR VIRTUAL PC CONNECTIVITY)
so today im happily using my vista virtual machine inside virtual pc 2007 on an XP sp3 host, and then the internet stops working. 'internet explorer cannot display the webpage'. fuck fuck fuck.
illogical. nothing has changed. router hasnt been switched on or off.
internet works in host pc just fine. it was working last night and just now.
how can it just stop working in the virtual PC???? unless someone has hacked them just now. surely not.
i spend an hour looking for solution, changing around settings. then i find...
other person on same wireless connection in another room had turned on AIRFOIL on their mac. not exactly sure how its all setup, but sending the sound (streaming internet radio) from their computer to the loungeroom speakers receiver.
what is weird is that the host machine has no problems with connecting when the airfoil is in use, JUST THE GUEST INSIDE THE VIRTUAL MACHINE. (and just vista guest i think)
i also turned off browser, virtual pc machine, and host machine reboot after the AIRFOIL was turned off. also did the 10 second reset on the modem somewhere in the mix.
an viola, when restart it all, it just works again. WOOOOO!!!
and there is also an extra step i had already done to get it working initially for connecting the virtual PC vista guest to the hosts connection, described here:
and note that in virtual pc console, for each machine click on settings button and networking and the setting should be 2, and 1st is 'shared networking' (NAT) and 2nd is the actual connection. eg. pci fast ethernet or wireless bla bla bla...
---------------------------------------
also, there is a thing in XP virtual pcs, "address not valid" which you might need to press f12 (in browser i think), and untick 'enable proxy servers' for internet to work.
----------
ok so today was having troubles with vista with a new virtual image
-in the vritual pc consoles list, go settings and choose network, shared networking NAT and then for number 2 select wi fi.
-put in the IP manually in the virtual vistas network settings(see original post for exact way to do it.)
-then went to advanced settings, WINS tab and selected enable netBIOS over TCP/IP (just to do it incase it helped)
-did a 10 sec power cycle on the modem
-shut down vista entirely
-then shut down the host machine entirely
-then on reboot, i clicked on the wireless network connection status properties, fiddled with another airport network on our network by reimputting the password. but then didnt connect to it, just connected to the other one which was connected before but had a dialogue like cannot find a certificate for the network. after looking for network address or something in the status, it showed connected and excellent (in host machine). google worked.
-when i opened the vista virtual pc, started to look for etehernet controller to install, then must have accidently clicked on 'set network location', (possibly in the network icon in bottom toolbar) and chosen private, with the city tower building icon, and it sort of auto configured something. when that was done, it worked...
why i dont know but that is the trouble shooting process for vista virtual machine connecting through an xp host that is connected to a airport wifi.
now for the new xp images....
---------------------------------------
also, there is a thing in XP virtual pcs, "address not valid" which you might need to press f12 (in browser i think), and untick 'enable proxy servers' for internet to work.
----------
ok so today was having troubles with vista with a new virtual image
-in the vritual pc consoles list, go settings and choose network, shared networking NAT and then for number 2 select wi fi.
-put in the IP manually in the virtual vistas network settings(see original post for exact way to do it.)
-then went to advanced settings, WINS tab and selected enable netBIOS over TCP/IP (just to do it incase it helped)
-did a 10 sec power cycle on the modem
-shut down vista entirely
-then shut down the host machine entirely
-then on reboot, i clicked on the wireless network connection status properties, fiddled with another airport network on our network by reimputting the password. but then didnt connect to it, just connected to the other one which was connected before but had a dialogue like cannot find a certificate for the network. after looking for network address or something in the status, it showed connected and excellent (in host machine). google worked.
-when i opened the vista virtual pc, started to look for etehernet controller to install, then must have accidently clicked on 'set network location', (possibly in the network icon in bottom toolbar) and chosen private, with the city tower building icon, and it sort of auto configured something. when that was done, it worked...
why i dont know but that is the trouble shooting process for vista virtual machine connecting through an xp host that is connected to a airport wifi.
now for the new xp images....
Posts
