
astronomer |
Gary had a good idea about checking the hosts file, but I suggest you use nslookup on both working and non-working systems. Are they getting information from the same DNS server? If the systems are the same, they should get identical information. If they do, and there are still differences, I world suspect redirection or similar malware causes.
rt

kfettig |
Thank you, astronomer. I never thought to compare DNS servers, and sure enough, the machines that weren’t working were pointing to a different DNS server. I don’t believe that anyone changed those settings. Could malware have done it? I can’t tell you how appreciative I am, as well as the people this problem was affecting! Everything is working fine now.
Thank you!

astronomer |
Malware could definitely have done it. You would be shocked and disturbed at what is now happening with javascript.
I watched a demo where the presenter uploaded script to an IIS server, downloaded it with an innocent client, (just by clicking on the link), and compromised the client. He installed a keylogger and showed the recent common websites visited. After this he showed, on his hack server, the username and password used for the ecommerce site. Then he scanned the local net, found the DSL modem, and cracked it using the manufacturers default admin and password.
This is the next big vulnerability area.
rt