totally stuck with XP IP problem - help!

[dje735]

Using XP PRO and SP2 - performed an Office 2003 update and subsequently lost IE Internet access and Outlook email POP3 reception, but can send SMTP mail! Also cannot access other m/c on the network.

Trying to use a hardwired home Belkin network with DSL modem which is still working fine with my laptop and IMac and previously worked fine with the XP pro/SP2 m/c.

Cannot repair the network connection - renewing IP address fails though IP address 192.168.2.5 is correct.

Have tried the winsockxpfix - no improvement but the SPcheck report shows 8 missing DLL and EXE files in XP SNMP - LMMIB2, HOSTMIB, SNMPMIB, EVNTAGNT, EVNTCMD, EVNTWIN, SNMP, SNMPTRAP

Comparing this laptop's settings with the XP pro m/c using ipconfig /all shows only one difference - the WINS PROXY setting on the failed m/c is disabled.

Help! - and thanks in advance for your expertise.

[ByteBack]

Goto > START > RUN > type this CMD > click OK.
Now type "netsh int ip rese" and press ENTER.

This will reset you TCP/IP totally.

Then perform your ipconfig.

If that doesn't do it, then you probably have virus issues or spyware issues or both.

When checking for spyware, run Adaware. After Adaware has completed run Spybot. Running one may not find every spyware program you have, so it's best to run 2.

Hope that helps!

[dje735]

Thanks for the feedback - when I try it I get a one or more parameters are missing / syntax not valid - gives a hint example of
reset resetlog.txt

Can you advise further?

Thanks

[ByteBack]

Opps.. my fault!

The correct command is "netsh int ip reset c:\resetlog.txt"

It has to create a log file in order to complete. In this case the destination for the log will be c:\resetlog.txt.

[dje735]

Thanks for that, operated this time (we have a slight time difference!) but has not resolved the problem.

ipconfig showed 3 Teredo Tunnel adapter as well as the normal which have not showed up before, otherwise repair still fails to renew the IP and I cannot receive email.

On re-booting the network connection now comes up as broken, something that also occurred earlier in this fault. Changing cables for known working ones has no effect. Resolved before just by repeated re-boots of hub and m/c.

Now running Adaware which has come up with 25 recognised/critical objects so far (fairly early on) but is still running! More when it is complete and I have run Spybot too.

cheers