microsoft.com names not resolving
-
Wednesday, June 24, 2009 8:26 PMI have a new Small Business Server 2003. It looks like everything is working right. I can access any web site except *.microsoft.com.
nslookup resolves the name, but if I try ping, it tells it cannot resolve the name. I have tried turning off the firewall to no avail. I have rebooted the server and flushed the dns numerous times.
Any ideas?- Moved by Max Wang_Chinasoft Wednesday, April 27, 2011 11:12 PM forum consolidation (From:Networking)
All Replies
-
Thursday, June 25, 2009 6:34 PMHi Aharon,
To resolve, or convert a domain name into an IP address, does the server actually resolve correctly?
When you ping, even though it times out, do you get an IP address? Does it show:
pinging www.microsoft.com [ip address] with 32 bytes of data
When you do an nslookup, what IP address does the name resolve to? Is it correct?
If it does not resolve properly, check your DNS and check your hosts file.
If you type 207.46.193.254 in the browser's URL bar and you do not get Microsoft's Web Site, do a tracert to see if the packets are being dropped somewere along the way.
Miguel Fra / Falcon ITS
Miguel Fra www.falconits.com- Edited by Falcon IT Services Tuesday, November 17, 2009 2:25 AM
-
Thursday, June 25, 2009 7:46 PM1. nslookup resolves correctly.
2. ping does not resolve at all.
3. If i type the ip address or even the real name, it goes there.
Aharon -
Friday, June 26, 2009 3:15 AMSo if I understand correctly:
1. NS Lookup resolves correctly
2. Ping www.microsoft.com does not reply, it times out or gives you an error.
3. If you type www.microsoft.com in your browser it goes to Microsoft's web page?
What do you mean by ping tells you it cannot resolve the name? What exact error message does it give you?
Can you ping other web sites?
Miguel Fra www.falconits.com -
Friday, June 26, 2009 3:50 PMThe reply to a ping is
Ping request could not find host www.microsoft.com. Please check the name and try again.
Other than the microsoft.com domain, networking is FULLY functional.
Aharon -
Friday, June 26, 2009 5:36 PMOK Aharon,
you said that
"3. If i type the ip address or even the real name, it goes there."
Sooo..
a. you can type www.microsoft.com in your browser and it displays microsoft's web page
b. you can nslookup microsoft.com and it works
The only thing you cannot do is PING microsoft, right?
Normally, I would say that echo request is turned off on the router that you are pinging and so the router does not respond to a ping command. Microsoft is a bigcompany, and like many big companies they employ caching servers from companies like Akamai and others (I don't know if or who they use, this is just a theory). So you might be pinging an IP address that does not respond to ping whereas another user in a different geographic location might ping the same url and ping a different IP address that does respond to the ping command.
I am not an expert on how Akamai and other caching services work, so as I mentioned, this is only a theory on one possibility of what is happening. The fact that you can surf microsoft's web sites and other web sites does indicate that your system is not experiencing a problem.
What's weird is that you are getting the error message "Ping request could not find host". Even if the router does not respond to Ping, you should still get a timeout error and the host name shoud be resolved. Weird.
Does the same thing happen to worksations connected to your LAN or is it just the server?
Miguel Fra www.falconits.com -
Friday, June 26, 2009 6:24 PMNo. Not right. IE does not go there. Gives me the same as the ping.
When you do nslookup on the name it turns out the microsoft.com domain are all aliases. If I take the real name it works. However, that is not good as all the links use microsoft.com as their name.
My LAN is working fine and I can access anything from anywhere else on the LAN. In fact, this is how I do this posting.
Aharon -
Friday, June 26, 2009 9:56 PMHi Aharon,
If you do an NSLOOKUP from the server and from the lan, are the DNS server the same?
Try setting up a forwarder on DNS server and clear cache see if that helps.
Also, look at this article:
http://windowsitpro.com/article/articleid/42188/solving-a-web-site-access-problem.html
Miguel
Miguel Fra www.falconits.com -
Saturday, June 27, 2009 12:03 AMHi Miguel,
nslookup yields the same (correct) answer.
I have tried dns forwarders, even specifying is at the hosts file.
I just tried that article. Did not help.
AHaron -
Saturday, June 27, 2009 12:32 AMHi Aharon,
Does your firewall have a log file that you can look at right after pinging Microsoft and see if there are any telling signs? What about windows server logs? Anything in the DNS logs?
If your firewall has good logging, you may see dropped packets, etc.
After you applied the changes from the article as stated above, try rebooting just in case any registry values have to be re-loaded.
Other than that, I am out of ideas. I hope someone else can add to this post. I will keep my eyes peeled for anything that might be useful.
Miguel
Miguel Fra www.falconits.com -
Saturday, June 27, 2009 3:41 AMHi Miguel,
The firewall is irrelevant in this case. The name is not resolving at the local computer. It is to be something in the security setting of the server itself. I have heard that sometimes windows has hard time with aliases, but I cannot get anybody from Microsoft to answer the question. They are too busy to make their product work.
Aharon -
Saturday, June 27, 2009 1:24 PMHi Aharon,
Try changing the MTU on the server. It could be that something is going on with packet fragmentation between server and firewall.
Miguel
Miguel Fra www.falconits.com -
Monday, June 29, 2009 5:59 PMHi Miguel,
Its been a while since I worked with a Windows Server (now I know why). How do I change the MTU on an interface? -
Monday, June 29, 2009 6:44 PMHi Aharon,
First disable EDNS on server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
add EnableEDNSProbes and set the value to 0
If that does not work, try to change the MTU try different sizes both on server and router.
To change MTU size on adapter
- Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<ID for network interface>
- On the Edit menu, point to New , and then click DWORD Value .
- Type MTU , and then press ENTER.
- On the Edit menu, click Modify .
- In the Value data box, type the value of the MTU size, and then click OK .
- Quit Registry Editor, and then restart the computer.
Please back up both registry keys before proceeding. If this does not fix you problem, rever the registry back to the default settings.
Miguel
Miguel Fra www.falconits.com- Edited by Falcon IT Services Monday, June 29, 2009 7:57 PM
- Locate the following key in the registry:
-
Monday, June 29, 2009 10:21 PMNo. Did not work.
-
Monday, June 29, 2009 10:47 PMHi Aharon,
Sorry, I am out of ideas. If anything else comes up, I'll post.
Miguel
Miguel Fra www.falconits.com -
Monday, June 29, 2009 11:41 PMHere is some more data. I turned the dns server debug log to the maximum detail. It looks like for any other address the system asks the dns for resolution, but for microsoft.com the query never arrives to the dns server. Seems like it is somehow hardwired into the system, but not in a good way.
Aharon -
Tuesday, June 30, 2009 12:58 PMCheck the hosts file that there is not a static entry.
Miguel
Miguel Fra www.falconits.com -
Tuesday, June 30, 2009 4:34 PMI actually tried to put an entry in the hosts file. And it does not look like it looks there. It seems to be something hard wired into the system. For instance any of the domains in msft.net (also Microsoft) works.
Aharon
-
Tuesday, June 30, 2009 6:28 PMHave you tried this?
make sure you remove any entries from hosts and clear dns cache
create a zone in your dns server for microsoft.com
manually enter the a record and it's corresponding IP address
manually enter any canonical names
Does it work now?
Honestly, I can't imagine something DNS being 'hardwired'. If you do the steps above, give test.microsoft.com the following A record -> 74.169.172.82
If you land on my site, then that means that microsoft.com it not hard wired (p.s. I made an entry into my IIS header just files for this experiment)
Miguel
Miguel Fra www.falconits.com -
Tuesday, June 30, 2009 8:51 PMActually, like I wrote before, it does look like a hardwire issue. I have tried, as you suggested to created a microsoft.com zone. I have put in there test with your address. nslookup resolves it, but IE and ping do not. Again, the dns does not show a record of it being queried.
Aharon -
Tuesday, June 30, 2009 10:33 PMNow that's weird!!!!!!
Aharon, hopefully somebody sees this and can add to it as I am out of ideas. If you do figure it out, please post back. I am very curious.
Miguel
Miguel Fra www.falconits.com -
Wednesday, July 01, 2009 5:36 PMI agree. It is weird. Microsoft support is taking their time trying to solve it. In fact, since this is a fresh installation they cannot claim I did anything wrong.
Aharon -
Sunday, July 05, 2009 12:00 AMAharon,
When you set enable EDNS to NULL in the registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
add EnableEDNSProbes and set the value to 0
did you reboot the server so that the new values can be reloaded?
Miguel
Miguel Fra www.falconits.com -
Monday, July 20, 2009 6:23 PMCheck this:
http://social.technet.microsoft.com/Forums/en/partnerwinserversbs/thread/63485123-a8e9-4d06-8608-39c580da1089
Miguel
Miguel Fra www.falconits.com -
Thursday, November 12, 2009 2:50 AM hi aharon.late reply.i have the same problem. the MS DNS client can resolve microsoft websites. but ping (and IE) cannot. browsing internet is OK, but updating Windows or accessing microsoft websites is not possible.because the server was infected by a trojan, i have suspected the services vital to micorsoft were modified (startup settings). i did the following to resolve the problem.1. temporary replaced my TCP/IP DNS settings to point to opendns (208.67.222.222 / 208.67.220.220)2. temporarily stopped DNS Client service3. started/reset startup settings of the following: Automatic Updates, Background Intelligent Transfer Service, and Event Log#1 is causing the tcp/ip client (IE) to not recognize microsoft.com websites#3 was modified by trojan. so i have to get them back to the default startup settings (automatic).did an system update.then revert back to the original setup.this resolves my problem.--edel
- Proposed As Answer by StephenZF Wednesday, November 18, 2009 12:13 AM
-
Wednesday, November 18, 2009 12:13 AMThanks a lot for the help Edel - I've spent about 4 hours on this so far and your post just saved me from reinstalling the whole thing!
-
Monday, January 04, 2010 6:09 PM
Thanks Edel - this fixed my problem also - I was pulling my hair out.
-
Friday, March 18, 2011 8:16 AMThanks a lot Edel. This helped.
