Web Hosting Talk : Other Forums : Computers and Peripherals : Microsoft is blocked for me! Help Needed

[InfiniteTech]

Yeah, each and every service by Microsoft is blocked for me. Sites like, windows.com opens but redirects to microsoft.com/slash/something/here/ and thats it. It wont move any further!


Windows Live XXXX (xxx = mail; messenger; spaces; office; etc) none of them open!

I narrowed it down to my TP-Link TD-W8910G wireless router. My ISP isn't blocking it cause their router opens the site and my Windows Live Messenger. So its gotta do with this router. I have opened all the ports WLM would want, MSN Gaming Zone, HTTP/S (80/443), DNS and so many others.

I am using OpenDNS.com and have also cleared my DNS cache incase something is screwed up at that part of the story.

But why is the domain screwed up? xxxx.microsoft.com also doesn't open. I ran the troubleshooter in WLM and all are checks are fine!

I don't even know what to search for. If it is only the Messenger, okay some screwup with the router firewall. But even the sites dont open. So I assume there could be some software that is restricting it, but then again when I switch over to my ISP provided ADSL modem/router it opens.

Where the heck is the problem?

I am clueless!

Edit: Windows Live Messenger Error Code: 81000306

[dancom96]

What do you get when you go to Microsoft.com?

[InfiniteTech]

Originally Posted by dancom96

What do you get when you go to Microsoft.com?

Waiting for microsoft.com

...
...
...

Timed out waiting for microsoft.com

[InfiniteTech]

More discovery, I cannot access http://manage.resellerclub.com/reseller/ too.

Something is going horribly wrong here.

What is it that these sites require and sites like WHT don't? Even my billing system works (assuming the dependency of SSL).

[ZeroPing]

1. Try this tool
http://www.goheer.com/products/tcptraceroute/

Try tracerouting [TCP] microsoft.com port 80. Where is it failing?

2. Are you using a personal firewall?

[InfiniteTech]

Originally Posted by bluetesting

1. Try this tool
http://www.goheer.com/products/tcptraceroute/

Try tracerouting [TCP] microsoft.com port 80. Where is it failing?

2. Are you using a personal firewall?

lol, I know how to do a trace-route via command line, thanks for the guidance and below is the trace route report.

Tracing route to microsoft.com [207.46.197.32]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     8 ms     8 ms  117.192.0.1
  3     8 ms     8 ms     8 ms  218.248.160.6
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    61 ms    62 ms    61 ms  125.16.156.25
  8    58 ms    57 ms    57 ms  125.21.167.25
  9   244 ms   245 ms   244 ms  12.118.94.85
 10   315 ms   315 ms   315 ms  tbr1.n54ny.ip.att.net [12.122.82.146]
 11   314 ms   315 ms   315 ms  cr1.n54ny.ip.att.net [12.122.16.153]
 12   315 ms   314 ms   314 ms  cr1.cgcil.ip.att.net [12.122.1.190]
 13   315 ms   314 ms   314 ms  cr1.st6wa.ip.att.net [12.122.31.162]
 14   316 ms   315 ms   315 ms  tbr1.st6wa.ip.att.net [12.122.23.170]
 15   315 ms   315 ms   314 ms  12.127.6.33
 16   323 ms   323 ms   323 ms  12.124.173.42
 17   327 ms   326 ms   326 ms  ge-5-3-0-56.tuk-64cb-1a.ntwk.msn.net [207.46.44.1]
 18   325 ms   324 ms   325 ms  ge-0-1-0-0.cpk-64c-1a.ntwk.msn.net [207.46.35.6]
 19   326 ms   325 ms   324 ms  ten3-4.cpk-76c-1b.ntwk.msn.net [207.46.34.118]
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
Trace complete.

But then again, how am I able to browse microsoft.com while using the ISP's ADSL modem/router?

[Biju]

The problem is with your ISP provider and more over check down for some sort of viruses or torjans.

[InfiniteTech]

Originally Posted by Biju

The problem is with your ISP provider and more over check down for some sort of viruses or torjans.

It can't be my ISP cause it works with their ADSL modem router. I poked around and didnt find any good info in its control panel.

I bought Ad-Aware Plus 2007 and running a scan. Its found 150~ infections. But the fact is that 99.99% of all what it found are only harmless tracking cookies (used by advertising companies).

[InfiniteTech]

Hah... From the past 8 hours the local exchange has been having problems and no one has done anything. lol

Thanks for all your help guys!

[AmyWilliams]

Originally Posted by ganesh-rao

Hah... From the past 8 hours the local exchange has been having problems and no one has done anything. lol

Thanks for all your help guys!

The "local exchange" is owned by the ISP? So the problem is fixed now?

[InfiniteTech]

The "local exchange" is owned by the ISP? So the problem is fixed now?

India isn't like the United States. Every ISP owns its own local exchange. I know that it isn't like that at your place.

Also, even after they had resolved their issue. Mine had not. I fixed it by updating my router's firmware. So just update your firmware just for the heck of it and see if it resolves your issue.

Are you using netgear? Even that router has a firmware problem.

[ZeroPing]

Originally Posted by ganesh-rao

lol, I know how to do a trace-route via command line, thanks for the guidance and below is the trace route report.

But then again, how am I able to browse microsoft.com while using the ISP's ADSL modem/router?

A TCP-Traceroute is not the same as an ICMP/UDP traceroute.

Just a week ago, our shared webhost was refusing connections from a dedicated server we run. We tried ping - working. Traceroute - working fine.

TCP-Traceroute showed us that the webhost server itself (and not any router on the path) was dropping our TCP packets.

Not everything is as obvious as we think it is

[page-zone]

Cancel them