@Cobolt Options

[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

[Cobolt]

Heyas monkster, my dad is asking 'how to do a system restore'. Ty

[MonkeyFiend]

click start > all programs > accessories > system tools > system restore

The rest is self explanatory - with any luck you might have a recent restore point (it's worth a try)

It may muck up software (if the software was installed after the restore points was made) but won't affect music/video/documents etc.,

[Cobolt]

1. The dependancies: tcpip, afc, netbt
doing the rest now!

[Cobolt]

Sadly clicking Next to restore to an earlier point does n'out...

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

DHCP Client was stopped, but you can't start it - it says ' Could not start the SHCP Client Service. Error 1069 - The dependancy service or group failed to start.'
Also, the DNS Service gave the same error as the DHCP message.

3. Yep, same result.

4. 351KB, and the build data is: version 5.1.2600.3394

EDIT 2: Internet explorer says 'Windows has detected a problem with the WINSOCK provider catalog on this computer.' Following the instructions didn't help. WINSOCK status - IRDA protocol is not found in WINSOCK catalog.

Aaaaaaaalso: 'A connectivity problem exists with an installed LSP'

[MonkeyFiend]

good old system restore - rarely much use.

At least we're getting some idea of what's gone wrong now.

The DHCP service has to run.. and yours failed to start due to a dependent service failing, so we need to find what the dependent service is (from the 1. part of my previous post)

I'd guess that an LSP (layered service provider) has been removed from the system but is still being called by the dhcp service which fails as a result. The LSP itself may be legitimate (norton, aviva, zone alarm) or it may be part of virus/spyware etc.,

You can download lspfix (google it) or download from the handy http://sneakymonkeys.com/lspfix.exe mirror

If you run that tool, it will tell you what LSP's you have hooked into your system (don't remove any yet!) - can you post back with what you have?

thx.

[Lawpf2001]

as said previosuly i have a wireless card going free

[MonkeyFiend]

as said previosuly i have a wireless card going free

If it's an LSP problem then it's software realted. Reinstalling the operating system would def fix it, but that's a royal pain in the arse. If they bought/acquired another network card you'd still get the same problem

[Cobolt]

Heyas, sorry about the lack of replies, my dad's been busy with work stuff, but hopefully he cna have another look tomorrow =P

*sigh* I think i'm becoming depressed over this whole matter!

[Lawpf2001]

make a post on this site and see if you get anything back. Theyve always helped when ive had a problem
http://www.overclock.net/

[Cobolt]

Hi Monkey, I can't download ispfix on the affected PC as it won't connect to the internet - the original problem! I'll try downloading it here and putting it on a USB stick...

[Cobolt]

Hi Monkey, the USB stick worked.
Ispfix says:
Winsock2 Repair Utility. No problems found.
The following are listed:
mswsock.dll
winrnr.dll
mdnsnsp.dll
rsvpsp.dll.

Thanks.

[Lawpf2001]

deep intake of breath

[MonkeyFiend]

ok, the only 3rd party lsp I see relates to shitty adobe products (the bonjour service). If you go into start>run>regedit and navigate to:

HKey_Local Machine\System\Current Control Set\services\TCPIP and double click on dependonservice, is there anything listed other than "IPSec"? - if there is any other items listed can you delete them (so the depend on service only shows IPSec) and then restart and try again.

[fido77]

are you sure u have all the updates? sometimes i cannot connect if i don't install an update. and sometimes i cannot connect because of an update, in which case i have to do a system restore to before the update.

[Cobolt]

Hey monkey, sorry for the late reply

In 'depend on service', nothing else is listed.

[MonkeyFiend]

kk, am 90% sure something is up with the winsock...

1 * Click Start, Run and type DEVMGMT.MSC
* In the View menu, click Show hidden devices
* Double-click Non-Plug and Play drivers section
* Double-click the entry AFD, and click the Driver tab
* Set the Startup type to System. (if it's not already)
* Start the service. post the error message if any.
* Similarly start the two other drivers namely:

* TCP/IP Protocol Driver
* NetBios over Tcpip

* Close Device Manager and restart Windows.

2. Can you also just double check these files are in the C:\windows\system32\drivers folder?

afd.sys
netbt.sys

[MonkeyFiend]

and if that fails, things get more complicated...

Step #1
Full uninstall of TCP/IP.
----------------------------------------------------------------------
These steps are copied from http://support.microsoft.com/kb/325356

11. Locate the Nettcpip.inf file in %winroot%\inf, and then open the file in Notepad.
12. Locate the [TCPIP.PrimaryInstall] section.
13. Edit the Characteristics = 0xa0 entry and replace 0xa0 with 0x80.
14. Save the file, and then exit Notepad.
15. In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.
16. On the General tab, click Install, select Protocol, and then click Add.
17. In the Select Network Protocols window, click Have Disk.
18. In the Copy manufacturer's files from: text box, type c:\windows\inf, and then click OK.
19. Select Internet Protocol (TCP/IP), and then click OK.
Note This step will return you to the Local Area Connection Properties screen, but now the Uninstall button is available.
20. Select Internet Protocol (TCP/IP), click Uninstall, and then click Yes.
RESTART

For good measure you should delete the following keys before reinstalling TCP/IP in step #2 (go into regedit from start > run to do this)
HKLM/system/CurrentControlSet/services/winsock
HKLM/system/CurrentControlSet/services/winsock2

Step #2
Reinstall of TCP/IP
----------------------------------------------------------------------
Following the above steps from 11-13, replace the 0x80 back to 0xa0, this will eliminate the related "unsigned driver" error that was encountered during the uninstallation phase.

Return to "local area connection"> properties > general tab > install > Protocol > TCP/IP

You may receive an "Extended Error" failure upon trying to reinstall the TCP/IP, this is related to the installer sub-system conflicting with the security database status.

to check the integrity of the security database
esentutl /g c:\windows\security\Database\secedit.sdb

There may be a message saying database is out of date
first try the recovery option (in a command prompt window)
esentutl /r c:\windows\security\Database\secedit.sdb

if there are any problems, use the repair option (in a command prompt window)
esentutl /p c:\windows\security\Database\secedit.sdb

rerun "esentutl /g c:\windows\security\Database\secedit.sdb" to ensure that integrity is good and database is up to date.

Now return to the "local area network setup"
choose install > protocol > tcp/ip and try again

Reboot

Pray

[MonkeyFiend]

oh and something I forgot to mention... I assume you wanted to fix the PC rather than the embuggerence of a full reinstall (which would fix it) - there's an in-between option called SFC. Essentially it copies over all windows related files with clean ones from your windows CD without touching your other stuff.

The upside is that it will fix any network stack/winsock problems however the downside is the registry will be restored so you will probably need to reinstall most software such as ms-office/steam/drivers etc., again.

However since it wouldn't be a fresh insatll your drivers ad file should still be on the computer. Having said that it's still quite a drastic measure - but suspect there might be a balance against getting the computer fixed quickly..

Make sure you've backed up anything important and that you have a windows CD to hand before running this

A sneaky get around is to open regedit and save your registry to a file. Run the sfc command (below) which will clear most of your registry.

Then if things are working after that, you could try and import the registry file that you saved ealier - if the problem you were having was caused by something in the registry it will break it again. (in which case repeat the sfc command)

If it was something not related to the registry then restoring the saved registry file should make most of the software work again.

From Start > run > cmd

sfc /scannow

[Cobolt]

Hehe, you have just fully impressed my dad XD He expresses his thanks and will have a go a bit later =D
*cheers* Yay for Monkey! *cheers*