I do have a 3rd computer. It will take a while to set up. I will get started
on it after work today. It will take me an hour just to get it out of the
closet. I think you might be right about being easier. I have to take
adapter out of sparky, will that be alright or do you think that is the
problem? Thanks
"Chuck" wrote in message
...
On Mon, 6 Dec 2004 22:34:37 -0600, "Rick and Deb"

wrote:

This is going to be alittle harder to do but here we go.

SNIP

Thanks again, I,ve be watching you help other people, amazing.

It will be indeed amazing if we can get you straight.

So, Rick is still a problem. Any chance you can transport Rick to another
LAN?
Right now, I am not totally sure that Sparky isn't still part of the
problem.
Standard diagnostic procedure requires isolating each portion of a
problematic
system, and trying Rick against another computer would be a big help. Or
maybe
connect another computer to the LAN with Sparky.

If not, let's get to work on Rick.

Make sure latest drivers for the network adapter are loaded - check with
D-Link
website for driver update.

Test network adapter from (My Computer - Hardware - ) Device Manager.

Check for corrupted LSP / Winsock.
http://support.microsoft.com/?id=318584
http://support.microsoft.com/?id=811259

Give LSP-Fix http://www.cexx.org/lspfix.htm, WinsockFix
http://www.tacktech.com/display.cfm?ttid=257, or WinsockXPFix
http://www.spychecker.com/program/winsockxpfix.html a shot.

If no help yet, reset TCP/IP.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the
command
window.

Be patient and persistent. If this doesn't do it, we'll start
diagnostics.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.