March 20, 200917 yr Activity Packets Sent --- 1,364 Received --- 7 1. I have tried shutting down my virus protections and its not that. 2. I am sure the WEP is correct as it is CONNECTED. When I enter an intentionally wrong WEP it will not connect. 3. It was working fine for a very long time, then suddenly it stops. 4. It is set to obtain IP automatically 5. All my other computers have no problem connecting just fine to this network. 6. The router is 3 meters from the computer, and I have an antenna. Edited March 20, 200917 yr by TonySoprano
March 20, 200917 yr Does it get an IP number from the router/dhcp server? You can check this by right clicking on the network connection and choose status, or type 'ipconfig' in a command prompt.
March 20, 200917 yr generally i wouldnt anwser but as its tony soprano then i will try.. Like they person above said do a ipconfig and see if you get a IP.. if it starts with 169 then that means it is NOT gettin a IP.. so that wil be your problem..if you are gettin a IP then the DNS is your problems so you could change that in network properties>>dns number 208.67.220.220 or 208.67.222.222
March 20, 200917 yr Author IP starts with 192 I tried going to TCP/IP and changing Obtain DNS automatically to the numbers you gave me but it still does not change anything.
March 20, 200917 yr Author if you are saying to use google, than by my OP it should be pretty clear that i have exhausted that option.
March 20, 200917 yr Try using a fixed IP address (and turn off DHCP). Maybe its just my own bad luck, but I have yet to see DHCP work well with encryption on any piece of wireless consumer hardware.
March 21, 200917 yr if you are saying to use google, than by my OP it should be pretty clear that i have exhausted that option. I was actually saying to just ping a site and to see if it maybe program related - though it might be best just to ping your gateway to start with. so other things to try turn off encryption at both ends. uninstall card - remove card - boot - shutdown - fit card - install drivers try a LAN cable ( you might have a corrupted tcp/ip stack )
Create an account or sign in to comment