| 5:23 am on Aug 24, 2004 (gmt 0)|
Did you try a cold boot?
Did you try to repair the connection?
Did you try to shut everything down and power up again?
One or the other has always worked for me. A pain in the arse, but I have yet to figure out the real source of the problem.
| 2:17 pm on Aug 24, 2004 (gmt 0)|
Thanks for responding quickly! I tried cold boot, powering down, and repair connection. None worked. When I try repair connection I get message: "the following steps of the repair operation failed: renewing IP address."
Signal strength is still excellent. All other computers in house still connect to wireless network and internet with no problem. This one works only through ethernet connection.
| 2:24 pm on Aug 24, 2004 (gmt 0)|
Double check that you have your DNS/Gateway settings for the wireless card pointing to your access points IP address.
This didn't work for me - but might be worth trying the wireless card on a static IP address also.
| 2:56 pm on Aug 24, 2004 (gmt 0)|
You might make sure that your laptop is setup to obtain it's IP address automatically (possibly got changed somehow). That might be why you are unable to obtain a new IP during repair.
| 3:57 pm on Aug 24, 2004 (gmt 0)|
Laptop is still setup to obtain IP address automatically. It shows an address of 169.254.251.88. Should that change when I reboot? It doesn't.
| 4:00 pm on Aug 24, 2004 (gmt 0)|
|Should that change when I reboot? |
Check it's in the same range as your access point though (i.e. your access point will have an IP of 169.254.251.x where "x" is a number from 0--255).
If they're on the same local IP range, can you PING the access point, or another PC on the local network?
| 4:49 pm on Aug 24, 2004 (gmt 0)|
I disabled Tiny Personal Firewall rebooted and got an internet connection. Never had this problem before. It didn't interfere with my wired ethnet connection. It solves the one problem, but won't I be unprotected? Any suggestions?
| 5:49 pm on Aug 24, 2004 (gmt 0)|
ahh...I was going to suggest a possible firewall problem as I've run into that, but forgot to mention it (oops).
You should still be able to run the prog. it sounds like there is just some setting that is off. I would start it up and look through the settings to see if you can find what is causing the problem. I haven't used that one, but most firewalls have an internet lock that can be activated that stops all internet activity. Possibly that got activated accidentally? Just poke around in the settings and compare them to your other systems that are working.