J
Justin Miller
Hi All
After many hours of reading this newsgroup and frustration trying to figure
out why Outlook 2003 wouldn't shutdown on certain machines, I have found a
possible solution that works for me on Windows XP and may work for others:
The problem on my machines was actually caused by issues with the TCP/IP
stack. I suspect that these problems were introduced after the installation
of third-party software. I noticed that there were file differences on the
affected machines that weren't on the machines that worked. The most
prevelent file was us_lsp.dll. This file was present on all the machines
where Outlook wouldn't shut down but not present on the working machines. I
wasn't able to find out what this file is but I was able to find out about
LSP's or Layered Service Provider's. They load on top of the windows TCP/IP
stack (winsock) to provide "added" functionailty. In reality, it appears it
is related to some malware programs. To fix it I had to basically
reinitialize the TCP/IP stack using the netsh tool and fix some registry
keys.
There is also a tool that will do all this for you: WinsockFix
http://members.shaw.ca/techcd/WinsockXPFix.exe
Good luck and I hope it works for others
Justin
After many hours of reading this newsgroup and frustration trying to figure
out why Outlook 2003 wouldn't shutdown on certain machines, I have found a
possible solution that works for me on Windows XP and may work for others:
The problem on my machines was actually caused by issues with the TCP/IP
stack. I suspect that these problems were introduced after the installation
of third-party software. I noticed that there were file differences on the
affected machines that weren't on the machines that worked. The most
prevelent file was us_lsp.dll. This file was present on all the machines
where Outlook wouldn't shut down but not present on the working machines. I
wasn't able to find out what this file is but I was able to find out about
LSP's or Layered Service Provider's. They load on top of the windows TCP/IP
stack (winsock) to provide "added" functionailty. In reality, it appears it
is related to some malware programs. To fix it I had to basically
reinitialize the TCP/IP stack using the netsh tool and fix some registry
keys.
There is also a tool that will do all this for you: WinsockFix
http://members.shaw.ca/techcd/WinsockXPFix.exe
Good luck and I hope it works for others
Justin