R
RodrYguez
Hi,
I have been scratching my head on it since the 12th of February. This
is really odd.
I can't connect on any address beginning with www.microsoft.com at
all, but all other websites are ok.
http://windowsupdate.microsoft.com works
but
http://www.microsoft.com/isapi/redir.dll?prd=ie&clcid=0x040c&pver=6.0&ar=ienews&os=N6
doesn't work, and also when trying to access to www.microsoft.com, i
get a DNS page error, but i can access support.microsoft.com and every
other websites.
Norton Antivirus, Trojan remover, AdAware, PestPatrol and Spybot (all
with the very last definitions) and even the Mydoom Worm Removal Tool
Version 3.0 made by Microsoft did not spot anything at all. No
infection is detected.
The hosts file is clean and pinging microsoft.com resolves on
207.46.245.214 and times out.
Cache has been severally flushed without any success.
Internet Explorer Temporary Internet Files folder has been emptied as
well.
Now i have tried the following test : if i use a *direct connection*
via A4proxy hearing 127.0.0.1 on port 8080, everything works ok.
So what is this damn huge mystery ?
Thanks,
Rod
I have been scratching my head on it since the 12th of February. This
is really odd.
I can't connect on any address beginning with www.microsoft.com at
all, but all other websites are ok.
http://windowsupdate.microsoft.com works
but
http://www.microsoft.com/isapi/redir.dll?prd=ie&clcid=0x040c&pver=6.0&ar=ienews&os=N6
doesn't work, and also when trying to access to www.microsoft.com, i
get a DNS page error, but i can access support.microsoft.com and every
other websites.
Norton Antivirus, Trojan remover, AdAware, PestPatrol and Spybot (all
with the very last definitions) and even the Mydoom Worm Removal Tool
Version 3.0 made by Microsoft did not spot anything at all. No
infection is detected.
The hosts file is clean and pinging microsoft.com resolves on
207.46.245.214 and times out.
Cache has been severally flushed without any success.
Internet Explorer Temporary Internet Files folder has been emptied as
well.
Now i have tried the following test : if i use a *direct connection*
via A4proxy hearing 127.0.0.1 on port 8080, everything works ok.
So what is this damn huge mystery ?
Thanks,
Rod