Cannot access microsoft.com domain!!!

McAvelli · 18-Jan-2009, 06:36 PM #1

Hi guys,
I was trying to open msdn.microsoft.com, but my browser couldn't open the page, so I thought they have technical problems. Than I tried microsoft.com and I realized that I cannot reach microsoft's domain.

Does anyone have a solution? Is the problem at my browsers, or at my ISP or maybe I have some kind of a virus?

I have installed Firefox 3.0.5 and IE 6.0

P.S. I tried with IP address as well instead of domain (I thought I had dns problem), but still nothing.

Please help...

avisitor · 18-Jan-2009, 06:42 PM #2

Pull up a command prompt and do tracert microsoft.com

Post that here for us to see. (Right click in the command prompt and click Select All then hit enter. Come back here and paste)

McAvelli · 18-Jan-2009, 06:56 PM #3

Quote:

Originally Posted by avisitor

Pull up a command prompt and do tracert microsoft.com

Post that here for us to see. (Right click in the command prompt and click Select All then hit enter. Come back here and paste)

I did that and here's the result:
Unable to resolve target system name microsoft.com.

Thank's for the quick replay..

avisitor · 18-Jan-2009, 06:58 PM #4

Ok, try tracert 207.46.232.182

It's going to be tough because microsoft.com doesn't respond to pings. Can you browse to http://207.46.232.182

It looks like you have a DNS problem.

JohnWill · 18-Jan-2009, 06:59 PM #5

Let's see a TRACERT yahoo.com.

Also, please post an IPCONFIG /ALL from that machine.

McAvelli · 18-Jan-2009, 07:14 PM #6

Quote:

Originally Posted by avisitor

Ok, try tracert 207.46.232.182

It's going to be tough because microsoft.com doesn't respond to pings. Can you browse to http://207.46.232.182

It looks like you have a DNS problem.

I don't think I have DNS problem, since I cannot access even with IP. Itried http://207.46.232.182 but still nothing.
Here's the tracert 207.46.232.182 result:

Code:

C:\Documents and Settings\Xhevat>tracert 207.46.232.182

Tracing route to 207.46.232.182 over a maximum of 30 hops

  1     7 ms     1 ms     1 ms  192.168.1.1
  2    14 ms     7 ms     7 ms  77.28.176.1
  3    13 ms     7 ms     8 ms  62.162.202.145
  4    13 ms    12 ms    12 ms  62.162.201.45
  5    19 ms    13 ms    12 ms  mk-sw-2-Po1.mt.net.mk [195.26.150.37]
  6    21 ms    14 ms    14 ms  MKWR01-Po2.mt.net.mk [195.26.150.54]
  7    33 ms    27 ms    27 ms  pos5-2.border0-ip2.net.telekom.hu [84.1.64.13]
  8    35 ms    28 ms    28 ms  bpt-b1-link.telia.net [213.248.76.189]
  9    53 ms    47 ms    46 ms  ffm-bb1-link.telia.net [80.91.251.182]
 10    56 ms    59 ms    59 ms  prs-bb1-pos7-0-0.telia.net [213.248.64.110]
 11   272 ms   138 ms   475 ms  ash-bb1-link.telia.net [80.91.251.98]
 12   340 ms   139 ms   474 ms  microsoft-ic-119510-ash-bb1.c.telia.net [213.248.89.18]
 13   297 ms   136 ms   477 ms  ge-0-3-0-57.ash-64cb-1b.ntwk.msn.net [207.46.41.57]
 14   287 ms   172 ms   441 ms  gig6-0.core1.was1.us.msn.net [207.46.38.1]
 15   291 ms   170 ms   171 ms  207.46.46.145
 16   588 ms   219 ms   394 ms  ge-1-0-0-0.co2-64c-1a.ntwk.msn.net [207.46.45.94]
 17   478 ms   614 ms   614 ms  ge-0-1-0-0.wst-64cb-1a.ntwk.msn.net [207.46.34.9]
 18   472 ms   614 ms   921 ms  ge-0-2-0-0.tuk-64cb-1b.ntwk.msn.net [207.46.40.22]
 19   757 ms   921 ms   921 ms  ge-0-0-0-0.tuk-64cb-1a.ntwk.msn.net [207.46.41.73]
 20   289 ms   360 ms     *     ten2-4.tuk-76c-1a.ntwk.msn.net [207.46.41.90]
 21   475 ms   614 ms   614 ms  po17.tuk-65ns-mcs-1b.ntwk.msn.net [207.46.35.146]
 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.

avisitor · 18-Jan-2009, 07:16 PM #7

Well, the trace to microsoft.com looks proper.

Howabout nslookup microsoft.com along with what JohnWill wanted in his post.

McAvelli · 18-Jan-2009, 07:18 PM #8

Quote:

Originally Posted by JohnWill

Let's see a TRACERT yahoo.com.

Also, please post an IPCONFIG /ALL from that machine.

I actually tried tracert google.com since it was faster:

Code:

C:\Documents and Settings\*******>TRACERT google.com

Tracing route to google.com [209.85.171.100]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    14 ms     7 ms     9 ms  77.28.176.1
  3     7 ms     7 ms     7 ms  62.162.202.145
  4    18 ms    12 ms    13 ms  62.162.201.101
  5    16 ms    15 ms    16 ms  mk-ws-1-Po2.mt.net.mk [195.26.150.41]
  6    22 ms    14 ms    14 ms  MKWR02-Po1.mt.net.mk [195.26.150.58]
  7    29 ms    22 ms    22 ms  79.101.96.9
  8    54 ms    46 ms    49 ms  de-cix20.net.google.com [80.81.193.108]
  9    59 ms    48 ms    51 ms  209.85.255.176
 10    62 ms    60 ms    56 ms  209.85.248.182
 11   584 ms    63 ms   141 ms  72.14.236.220
 12   678 ms   130 ms   790 ms  216.239.46.14
 13   147 ms   566 ms   139 ms  64.233.175.213
 14   437 ms   153 ms   460 ms  216.239.46.227
 15   640 ms   164 ms   449 ms  72.14.232.141
 16   185 ms   390 ms   181 ms  209.85.243.117
 17   711 ms   614 ms   200 ms  209.85.241.211
 18     *      429 ms   375 ms  216.239.46.208
 19   360 ms   614 ms   614 ms  216.239.48.143
 20   432 ms   605 ms   266 ms  209.85.251.153
 21   432 ms   222 ms   339 ms  74.125.31.6
 22   267 ms   330 ms   614 ms  cg-in-f100.google.com [209.85.171.100]

Trace complete.

And here's the ipconfig all result:

Code:

C:\Documents and Settings\******>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : ************
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
        Physical Address. . . . . . . . . : 00-**-BF-**-18-**
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.34
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 62.162.32.5
                                            192.168.1.1
        NetBIOS over Tcpip. . . . . . . . : Disabled
        Lease Obtained. . . . . . . . . . : Monday, January 19, 2009 12:01:07 AM
        Lease Expires . . . . . . . . . . : Sunday, March 01, 2009 4:01:07 PM

Ethernet adapter Local Area Connection 2:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Bluetooth PAN Network Adapter
        Physical Address. . . . . . . . . : 10-11-11-11-11-11

McAvelli · 18-Jan-2009, 07:22 PM #9

Quote:

Originally Posted by avisitor

Well, the trace to microsoft.com looks proper.

Howabout nslookup microsoft.com along with what JohnWill wanted in his post.

Code:

C:\Documents and Settings\******>nslookup microsoft.com
Server:  mtdns1.mt.net.mk
Address:  62.162.32.5

Non-authoritative answer:
Name:    microsoft.com
Addresses:  207.46.232.182, 207.46.197.32

JohnWill · 18-Jan-2009, 09:30 PM **#10**

The interesting thing is that I get almost the exact same trace to that IP address.

C:\>tracert 207.46.232.182

Tracing route to 207.46.232.182 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms ZyXEL [192.168.0.1]
2 1 ms <1 ms <1 ms ActionTec [192.168.1.1]
3 4 ms 4 ms 4 ms 98.114.133.1
4 5 ms 4 ms 5 ms G3-0-5-791.LCR-07.PHLAPA.verizon-gni.net [130.81.131.136]
5 21 ms 12 ms 12 ms 130.81.17.209
6 13 ms 12 ms 12 ms 130.81.14.58
7 11 ms 12 ms 12 ms ge-7-3-0-57.nyc-64cb-1b.ntwk.msn.net [207.46.34.157]
8 11 ms 12 ms 12 ms ge-0-0-0-0.nyc-64cb-1a.ntwk.msn.net [207.46.37.149]
9 31 ms 97 ms 32 ms ge-1-0-0-0.chg-64cb-1b.ntwk.msn.net [207.46.41.197]
10 97 ms 97 ms 97 ms ge-0-0-0-0.chg-64cb-1a.ntwk.msn.net [207.46.41.209]
11 88 ms 87 ms 87 ms ge-3-3-0-0.co2-64c-1b.ntwk.msn.net [207.46.41.194]
12 86 ms 87 ms 87 ms ge-1-2-0-0.wst-64cb-1b.ntwk.msn.net [207.46.35.189]
13 86 ms 87 ms 87 ms ge-1-0-0-0.tuk-64cb-1a.ntwk.msn.net [207.46.40.26]
14 86 ms 87 ms 87 ms ten1-2.tuk-76c-1b.ntwk.msn.net [207.46.41.94]
15 88 ms 87 ms 87 ms po14.tuk-65ns-mcs-1a.ntwk.msn.net [207.46.35.134]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * 207.46.232.182 reports: Destination net unreachable.

Trace complete.

avisitor · 18-Jan-2009, 09:33 PM **#11**

I get the exact same trace as you, John, just a little variation because I'm on L3 instead of VZ. But, I connect to msn.net at the same point.

The nslookup indicates DNS is properly functioning. I guess we could try stack repairs.

JohnWill · 18-Jan-2009, 09:53 PM **#12**

I guess so, though I don't hold out much hope that something this specific would be a general stack issue. However, since it's easy to try...

TCP/IP stack repair options for use with Windows XP with SP2/SP3.

Start, Run, CMD to open a command prompt:

In the command prompt window that opens, type type the following commands:

Note: Type only the text in bold for the following commands.

Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog

Reboot the machine.

McAvelli · 18-Jan-2009, 10:20 PM **#13**

Quote:

Originally Posted by JohnWill

I guess so, though I don't hold out much hope that something this specific would be a general stack issue. However, since it's easy to try...

TCP/IP stack repair options for use with Windows XP with SP2/SP3.

Start, Run, CMD to open a command prompt:

In the command prompt window that opens, type type the following commands:

Note: Type only the text in bold for the following commands.

Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog

Reboot the machine.

I did this and still nothing!
Since you guys said that you have the same route to microsoft.com and it works for you, is it possible that my ISP has cashed microsoft.com, and that's why it doesn't work?
Because I don't see that any solution works for me!
Thanks for your help...

avisitor · 18-Jan-2009, 10:29 PM **#14**

We both go through the po14 gateway, you go through the po17 gateway.

So, this is just Microsoft's site that's giving your problems, right?

McAvelli · 11:26 PM

Yes just Microsoft's site.

Tag Cloud
access acer asus bios bsod computer crash desktop driver drivers error ethernet excel freeze gaming gpu hard drive hardware hdmi internet laptop malware memory monitor motherboard netgear network printer problem ram registry router security slow software sound trojan ubuntu 11.10 uninstall usb video virus vista wifi windows windows 7 windows 7 32 bit windows 7 64 bit windows xp wireless

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Search
Search for:

Find the solution to yourcomputer problem!

Find the solution to your
computer problem!