@Cobolt Options

[MonkeyFiend]

ok to get some idea of why t'internet is broked, we need some info...

1. What make is your wireless router?
2. on your computer, if you click start>run>type 'cmd' and press ok, then in the black screen type 'ipconfig' what is your IP address listed as?
3. Are you using any 3rd party programs to handle wirless e.g. netgear wireless utility or is it done through windows?

From this we can tell whether the computer is actually connecting to the wireless router....

4. click start>control panel>network connections>look for network connections* and open it (if you can't see it, select 'switch to classic view' on the left first. Next right-click on your wireless network adapter and select properties, then the wireless networks tab. Is your connection in the preferred connections list? if so click on it and select properties... what is the network authentication and data encryption set to?

5. Because that was a nerdy post, I'll finish on a bad joke.. how do you get pikachu on a bus?.......................................................... you poke-him-on (apologies)

ta,

Monkey

[MonkeyFiend]

lol, not having much luck are you?

1. Sometimes the network stack can get cocked up by overenthusiastic av/firewalls (zone alarm and norton especially)

from the Start Menu select run, type 'regedit' and click OK
open the following folders, HKEY_LOCAL_MACHINE, then SYSTEM, CurrentControlSet, Services, then Dhcp.
open the key DependOnService

Can you tell me what dependencies e.g. tcpip, afc, netbt etc., are there?

2. click start > run > 'services.msc' Look for remote procedure call service, check if this is started/enabled. If not start & enable it and reboot.
2.a also check the DHCP service is started/enabled.

3. go to start > run > cmd, then cd c:\windows\system32 and try running ipconfig from here, same result? (if not then there's an environment variable issue, although this is unlikely)

4. in the c:\windows\system32\drivers\tcpip.sys file - if you properties on it, can you tell me the filesize and build date of this file? Some spyware can replace this file and run a process to stop you restoring a correct version.

5. Although the in ip reset failed, can try it against the winsock itself: start > run > 'netsh winsock reset catalog' (without the '), reboot and try again.

6. A very obvious one that I always forget about.. do you have a system restore point? to restore the system back to a time when things were working?

7. This can also be caused by the wrong drivers installed on the network card or wireless adapter - worth checking this right drivers are there

ta,

Monkey