Comments on: Repair Windows XP TCP Network Settings With WinSock XP Fix Utility

By: redondo

redondo — Thu, 04 Mar 2010 13:09:14 +0000

to be more clear!
in the server we have an hyper file control center aplication managing our database.and windev aplication,and this aplication as i said comunication with the comuters clients via port 4900 wich i think its damage…could that happen??

By: redondo

redondo — Thu, 04 Mar 2010 12:40:10 +0000

no,not all computers lose the conectivity only one or two in a month.

so my qustion is : the acofile aplication in the clients computers comunicate with the server via port 4900.is it possibal that this port cause of viruses or something like that could be shuted down or closed?? i ask this quastion cause after re-install xp,evrythings goes normal!!

is there a solution to re-open this port??

By: Chandrashekhar

Chandrashekhar — Thu, 04 Mar 2010 10:22:07 +0000

I found this software very useful to resolve network TCP issue…Below link also suggesting same review
http://techchand.org/559/repair-windows-xp-network-errors-with-winsock-tcp-repair-utility

By: Watching The Net

Watching The Net — Fri, 26 Feb 2010 12:09:55 +0000

@redondo

You already proved it's not a network problem on the desktop by saying:

"Acofile is unable to conect to the adress : 192.168.100.103(acofile is the program name and the adress ip is a server adress).but when i ping the server,it does work,and when i do : run–>\\192.168.100.103 i can get in the server"

Therefore you need to troubleshoot the application and find out why it's not making the connection.

You also mentioned that the program is installed on other computers. Do those computers also lose connectivity at the same time the problem occurs. If they do, then it may be a problem on the server, not on the desktops.

By: redondo

redondo — Fri, 26 Feb 2010 11:29:45 +0000

but after i re-insall windows xp it does work perfectly,only with time i got this problem,i always need to format and re-install xp to make the software work again.this aplication cominicate with the server through port 4900.

if this is an aplication problem,why it does work whene i re-install xp??

think you for answering my quastions

By: Watching The Net

Watching The Net — Fri, 26 Feb 2010 01:39:44 +0000

@redondo

WinSock XP will not fix your problem because you do have network connectivity.

Your problem sounds more like an application problem, not a network problem, and is something that you are going to have figure out what is causing the problem.

By: redondo

redondo — Fri, 26 Feb 2010 00:00:19 +0000

hello evry one!

i'm managing a program wich have database in server,but the program is installed in 6 difrent client computers,one day the program in the client computer couldn't conect to the server,and it gives me the follwing message : Acofile is unable to conect to the adress : 192.168.100.103(acofile is the program name and the adress ip is a server adress).but when i ping the server,it does work,and when i do : run–>\\192.168.100.103 i can get in the server,but the aplication can not get to the server,and after trying 4 or 5 time to run the program,it work,but when i try to re-run it,it gives me the same problem again.

could WinSock XP Fix Utility solve this problem?

any one have an idee what ist exactly my problem?

please help

By: Anonymous

Anonymous — Thu, 21 Jan 2010 01:33:45 +0000

Thanks very much for this software. It works wonderfully and solved a tricky connectivity problem.

By: Mark

Mark — Fri, 03 Jul 2009 06:00:15 +0000

yes tool works great onm XP Pro with service pack 3 and allupdates up to 7-2-2009

By: kennah

kennah — Sat, 27 Jun 2009 05:40:50 +0000

thank u very much for this tool!i just downloaded the tool yesterday and until now it seems that my nw connection is still ok.it worked for windows xp pro sp3.

By: LoungeLizard

LoungeLizard — Sat, 30 May 2009 23:09:35 +0000

My wife's computer developed a problem recently where her browser would not resolve anything. Performing a network repair solves the problem; but after a while the problem re-asserts itself. I created a scheduled task to run a repair every 15 minutes – and that works, for now… But, why did this happen in the first place? When I look at the output of the 'netsh ip reset' there are three entries indicating a "bad entry" for the "Linkage\UpperBind" key entries for the NIC, the NDISWAN, and a GUID value where the "bad value" was REG_MULTI_SZ = SymIM . My wife's machine has Norton's Internet Security on it, so I'm assuming the SymIM is a Symantec generated entry. Any ideas or suggestions what to do to resolve this rather than perpetually running 'schtasks /Create /TN RepairIP /SC MINUTE /MO 15 /TR "netsh int ip reset c:\temp\logs\network-connection.log"'

By: Watching The Net

Watching The Net — Tue, 12 May 2009 01:06:03 +0000

@Steve

The tool is only for XP (re-read the title again). I don't know if works on XP SP3, but if you need to run it on an XP SP3 machine, make sure you run a back and create a restore point first.

By: Steve

Steve — Mon, 11 May 2009 22:05:59 +0000

will this tool work for:

1. XP Pro xp3?

2. Vista x64?
Tks

By: Nick

Nick — Mon, 27 Apr 2009 11:46:13 +0000

Brilliant application, I been banging my head against a brick wall with a customers PC.
Problems included:
Stuck on preparing network connections on boot up
lsass.exe errors causing reboot on bootup
network connection broken
All fixed, thank you

By: Andoman

Andoman — Wed, 18 Mar 2009 03:43:44 +0000

THANK GOD FOR THIS TOOL. This will probably fix your problems if you can only connect to networks under "safe mode with networking".

Here's the story. All of a sudden, without warning, one day my computer would not connect to any type of network. At first I thought it was a wireless problem, then I found it was not recognizing even a wired network. I found out I could connect to a network but only in safe mode with networking. After tons of time spent searching google, I found this utility on a few pages marked, "Network adapters work only in Safe Mode – HELP!"

I loaded this tool and my system was magically fixed. !!!!! I love this file.