network weirdness

[firepages]

Hi , I lost my simple crossover-cable based connection between 2 machines , after lots of farting around & a lot of googling I found that resetting the TCP/IP stack (winXP) with netsh solves the problem , but every time I restart the problem returns ... & I can't ping 192.168.0.1 let alone the other computer.

Again , resetting TCP/IP via netsh works.. but only until reboot , & no I have nothing unusual starting up that should mess with this stuff (apart from internal (&common) windows services)

any one got any ideas ?

[Unit]

you could put the netsh command in your startup script.. Plug it into a batch file and set it to run whenever you logon.

[firepages]

Hi , that crossed my mind too , but I would still love to know what on earth is going on ... I am close to my regular XP re-install so maybe I will do that till then.

Cheers for the reply

[oracleguy]

You try using system restore?

The other thing you can try is going into the registry and manually removing 2 registry keys under HKLM/SYSTEM/CurrentControlSet/Services.
And remove the Winsock and Winsock2 keys.

Then reboot, and then go to your network connections, right click your network connection, choose properties, add services, say you have a disk to install from, and provide the location as /Windows/inf
Then you can select TCP/IP and install it.

Word of warning, I've never actually tried this, only read it some where.

[firepages]

:D lol , looks scary :D

saying that , I made a copy of your post and when its time to reinstall XP (closer each day;)) I will give it a go first to see what happens & post back.

cheers for that !

[Celtboy]

sounds like the tcp/ip stack just bugged out. Quite common with older versions of the MS OS....yet never any less annoying.

[Celtboy]

resolution? uninstall TCP/IP completely, reboot, and then reinstall.

[firepages]

its XP Pro(sp1) & TCP/IP is part of the OS so you cant just uninstall it anymore , netsh is supposed to reset the stack , and it does , but on my comp whatever is causing the issue is happening again on boot , all of my ip config is lost on reboot :(

[Celtboy]

do you have any IPSEC policies in place?

[Celtboy]

Also, does anything show up as failed in the event viewer?

[oracleguy]

its XP Pro(sp1) & TCP/IP is part of the OS so you cant just uninstall it anymore , netsh is supposed to reset the stack , and it does , but on my comp whatever is causing the issue is happening again on boot , all of my ip config is lost on reboot :(

Supposedly (I haven't ever tried it) the stuff I post will cause Windows to re-install the TCP/IP drivers and fix the stack.

[cpradio]

its XP Pro(sp1) & TCP/IP is part of the OS so you cant just uninstall it anymore , netsh is supposed to reset the stack , and it does , but on my comp whatever is causing the issue is happening again on boot , all of my ip config is lost on reboot :(

That isn't true. Well in a way it is. You can't "uninstall" it but you can "reinstall" over the current protocol. However, here is what solved my network issue.

Backup and Delete the following Registry Folders:
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
Reboot
Open Network Connections Folder, right-click on the network connection and Select Properties
Click on Install. Choose "Protocol", and click "Add"
Click "Have Disk...", Enter "\windows\inf", click OK
Select "Internet Protocol (TCP/IP)", click OK
When the process is complete, Reboot.

FYI, when you opent he Properties you will still see 'Internet Protocol (TCP/IP)' listed but when you choose 'Install' it will overwrite it. This successfully fixed my network issue. Mine involved a computer accessing our service station's DNS and IP address instead of our network DNS and IP address.