XP upgrade and TCP/IP

MS has destroyed my life AGAIN. I upgraded an XP home to XP Profesional and it's rooted my TCP/IP.
I can contact my ISP but the connection doesn't go through properly. There are about 300 - 400 bits exchanged and that's it.
Eventually I formatted the hard drive and started form scratch again. As you can see it seems to be working now.
Has anybody a clue what is going on?

 

Lance........Are you using Dial-Up connection, or high speed?
I'm using Dial-Up, and am having some speed issues myself.
My download, and upload speeds are pitiful with XP and AOL.
I have an older computer, running Win98, and the same version of AOL, and the speed is great. Maybe someone can offer us both some suggestions !!!!

 

I'm using dail-up, but it's not a speed issue. I'm not hooking up properly in the first place.
I'm on a local ISP who do a very good (cheap) job.

 

Lots of views, but no posters so I will try.
First off, I have not had a dialup in ages.

You might have a configuration problem, look around here for a thread on optomizing your MTU and such for your connection.
You may be sending the wrong size packets and hiting roadblocks.

 

http://www.tweakxp.com/tweakxp/display.asp?id=1016

If it ever happens again, (after restarting, of course ) try that. Ive had simelar things happen if I did a bad optimiser program..somtimes it made my modem COMPLETLEY dissapeak!

Also you might want to use this program :
http://www.nsclean.com/socklock.html
to stop things like adaware mashing your winsock files while trying to remove spyware. That might have been the cause

 

Sounds very hopeful, Goldfish. Does Adaware munch winsock files?

 

good call matey..

probably a better idea to REPAIR the winsock file rather than just leaving it full of spyware

 

Gentlemen.
Thanks very much indeed all round. So far (1 day) it looks like Sock Lock is doing its stuff.
Can Spybot have knocked the Protocols aroud?
I'm telling my ISP and everybody else I can find.

 

Well, think of it this way. Any spyware, or firewall you remove that taps into the winsock keys in the registry will often leave those entries behind.

So what you end up with is a modified winsock/winsock2 key that cannot be used by the system, because the program that was using those particular settings is no longer functioning or present.


An undocumented and not 100% tested as of yet fix that we have used ( I am a consultant for the level 1 techs for MS support) is to remove the winsock and winsock2 keys and then rebuild TCP/IP. The tweakxp link is good, but it will NOT fix winsock issues.


Back up your registry before trying this.


1. Delete these keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2

2. Reboot. This is important, it rebuilds part of the structure for these hardware services.

3. Reinstall TCP/IP through the GUI. Go to Network Connections, right click on a Network Connection, go to Properties. Go to install, highlight Protocol, click ADD. Click on Have Disk... where it says copy manufacturer files from, type:

C:\windows\inf


Click OK.

Highlight Internet Protocol (TCP/IP) and then click OK. Click OK or Close all the way out.


http://www.gci-net.com/~silver256/4.gif

4. Reboot.

5. Test for resolution.


Possible side effects:

Any application using your winsocks is now broken.

 

"MS has destroyed my life AGAIN. I upgraded an XP home to XP Profesional and it's rooted my TCP/IP.
"


I can't help but mention this. Please don 't take this the wrong way, its not meant to be a flame at all. MS didn't do this to you, you did this to you. Clean installs are ALWAYS better than upgrades. I am guessing (correct me if wrong) that this was an OEM XPH installation and you upgraded to a retail XPP. Even the OEMs reccomend against doing that. Don't kid yourself, the OEMs modify XP more than any other OS, especially in the field of WPA. Not to mention the fact that who knows what garbage they have installed.

 

Lyney baby,
I know that I did it by upgrading. I know clean upgrades are better., and I very seldom DO kid myself.

So I'm just to accept meekly that MS do not produce a very good product, and without quite a lot of experience and skill I shouldn't really carry out a task that MS says I should eb able to do?

Sock Lock seems to have cured things, and now I can get stuck into BBs like this. (What is an OEM, please?)

 

Original Equipment Manufacturer, ala HP, Compaq, etc.

I can tell you right now, and trust me, I've seen HUNDREDS of installs of XP, this is far more common on OEM to retail upgrade than from retail to retail.

Like I said, who knows what garbage they install. You can blame MS all you want, but upgrades are shoddy regardless of OS.

If your winsock was hosed, it was because of third party software installed, period. MS can't make an OS thats compatible with all software out there, or transition 3rd party apps perfectly any more than Apple or any other software company can.

 

"So I'm just to accept meekly that MS do not produce a very good product, and without quite a lot of experience and skill I shouldn't really carry out a task that MS says I should eb able to do?"

XP is a good product. No, it isn't perfect, but you cannot name an OS that is, either.

As for MS saying you should be able to? FYI, MS doesn't even support OEM to retail upgrades. When you call them, its best effort support, as in, they will do their best to help, but no guarantees.

 

BTW, glad you solved your issue. If it comes up again, and that app doesn't work, try my resolution in this thread

 

I agree, best route to go, and if it isn't explained on how to do this in the manual, you can follow this:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;316941

 

Adynalyne

Sorry, I should have said thanks for your efforts earlier. So far Sock Lock is doing its stuff, and I hope no problem ever again.

.