Unable to reach MSN and Microsoft

[Paul Bergson [MVP-DS]]

Not sure if anything can be done, more of a what is going on question. From
my residense I am unable to reach multiple large websites, suchas as MSN,
Microsoft and NetFlix. I do a tracert and the output is below. What has me
kind of scratching my head is I'm being sent to 10.x.x.x address, I don't
believe these should ever be visible on the public internet.

I'm stumped, it appears there is a route issue.
1 <1 ms <1 ms <1 ms 192.168.0.1
2 41 ms 40 ms 40 ms dlth-dsl-gw01-193.dlth.qwest.net
[65.102.106.193]
3 42 ms 41 ms 41 ms dlth-agw1.inet.qwest.net [65.102.106.93]
4 41 ms 40 ms 42 ms dlt-core-01.inet.qwest.net [205.171.165.13]
5 41 ms 42 ms 45 ms dlt-core-02.inet.qwest.net [205.171.165.10]
6 45 ms 44 ms 45 ms min-core-01.inet.qwest.net [205.171.5.146]
7 56 ms 57 ms 55 ms cer-edge-13.inet.qwest.net [67.14.8.206]
8 55 ms 55 ms 55 ms 65.118.28.46
9 61 ms 55 ms 55 ms ge-7-3-0-0.chg-64cb-1a.ntwk.msn.net
[207.46.47.176]
10 105 ms 101 ms 100 ms ge-3-3-0-0.co2-64c-1b.ntwk.msn.net
[207.46.43.153]
11 101 ms 103 ms 103 ms 207.46.46.92
12 110 ms 100 ms 100 ms ge-7-0-0-0.co1-64c-1b.ntwk.msn.net
[207.46.43.173]
13 101 ms 101 ms 100 ms 10.22.8.10

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

[Frankster]

"Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message
news:uos$htwgKH...@TK2MSFTNGP05.phx.gbl...

Well, considering your extensive knowledge in this area I hesitate to
comment... but I gotta ask...

Have you ran Malwarebytes Anti-Malware? (http://www.malwarebytes.org)

It sure does sound like this might fix it.

-Frank

[Paul Bergson [MVP-DS]]

No, it isn't an AV issue. I have checked into this. How it is being routed
to a public address inside of Microsoft seems to tell me that it has a
poisoned route of some kind.

From the trace route you can see it is outside of my box. I briefly spoke
with Quest (My DSL provider) and their solution was to shut off my dsl modem
for an hour. ??? This is like 8 hops away and has nothing to do with my
side, but I couldn't get him to understand that. He then told me to contact
the internet assigned numbers board. Since they are listed as the owners of
this public address. It made me laugh and I knew it was time to move on.
:-)

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Frankster" <fr...@SPAM2TRASH.com> wrote in message
news:m5Sdnf4jxMFxc63W...@giganews.com...

[Phillip Windell]

Hi Paul,

I ran across a guy yesterday with problems of that nature. It was caused by
conficker or some variant of it. In his case he could not reach MS,
Symantec, and many other "security" related Sites. It screwed with his DNS
resolution abilitiy. So,..not saying for sure it is your problem, but you
should double check one more time for infections just to be sure.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message

news:O82ZKjyg...@TK2MSFTNGP04.phx.gbl...

[Frankster]

Well, one other comment...

Just recently, after building a new 2008 DC, I found that I could not reach
"qwest.net". No ping. No web, no nothing. Just page not found. Turns out
that during the early stages of setup I had used an address of 192.168.1.x
for the new DC (an isolated router - to keep it from seeing my existing 2003
DCs on my 172.22.x.x network). Then later, I changed the new DCs IP to the
intended address within my network and replaced the old 2003 DCs.

After the above I could not reach qwest.net. Turns out that my new DC had
registered the 192.168.1.x address into DNS as qwest.net. I removed the
erroneous A record from the DCs DNS and all was well after that.

So... have you looked for any extraneous/errant DNS A records within your
own network?

Just a thought...

-Frank

"Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message

news:O82ZKjyg...@TK2MSFTNGP04.phx.gbl...

[Paul Bergson [MVP-DS]]

Turns out both PPoA and PPoE were enabled on my DSL modem and I guess some
web sites don't like both enabled. I just turned off PPoA and "Bang" I was
back in business.

Thanks for all the feedback though, really appreciate it. :-)

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message
news:O82ZKjyg...@TK2MSFTNGP04.phx.gbl...