Internally I can ftp large files at between 3 and 6 Mbytes/second, it varies some but doesn't appear obviously different for this one compared to the others.Ping time from any machine to the router is consistently 0ms with no latency at startup.Ping time from any machine to an outside service we use is consistently 51-55ms. But on the slow machine there is very commonly 8 seconds or more latency before ping shows any progress. The other machines do not show that. With the slow machine pinging ip address instead of domain name the 8 second or more latency appears gone. So this again seems to point at DNS as the culprit.Yes there is a HOSTS file. About 3 dozen 127.0.0.1 entries, looks like they are all notorious ad banner pushers.

I am having a problem connecting remotely to remote web workplace using a windows xp home computer. Is there a compatibility problem with the xp home version?1 person needs an answerI do too

Windows XP Home can not act as a Host to be Remote connected to, but it can act as a client. I.e,. using it to connect to a Remoter Host.http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx Jack-MVP Windows Networking. WWW.EZLAN.NET

My 2wire router modem model 2701HG is connected to a PC w/Windows XP. Two working printers are connected to the PC via USB cables. A laptop running Windows 7 connects to the router via wireless. The printers were set to share and the laptop printed OK to them. Then we went on vacation and upon returning the laptop showed the printers as offline. I have done everything I could find on the web, including restarting everything and running network setup. On the laptop if I try to install a new printer, even if I enter the \\pcname\printername it will not connect. I rebooted the laptop to Windows Vista installed on another partition, with same result. It seems the laptop cannot connect to the PC. I have disabled all the firewalls except for the router's firewall. What can I do to fix this problem?1 person needs an answerI do too

It turns out the Print Spooler service had to be restarted to enable Print Share once again.