Cannot access www.microsoft.com?

From our Windows Server 2012 Standard (not R2), I can get to google.com and do a query .... it comes back with hits, but clicking on ANY link gives me the 'Server Not Found' error.   I'm trying to fix a Windows Update error.  Anyone see this before?
MichelineSystems AdministratorAsked:
Who is Participating?
 
Hello ThereConnect With a Mentor System AdministratorCommented:
Set additional DNS as 8.8.8.8 and 8.8.4.4.
0
 
Hello ThereSystem AdministratorCommented:
Check your antivirus settings.
Disable Firewall and see if FW settings blocks the Internet connection.
0
 
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
IE Enhanced Security is on perhaps?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Dr. KlahnPrincipal Software EngineerCommented:
it comes back with hits, but clicking on ANY link gives me the 'Server Not Found' error.

Would you clarify this a bit for us?  From the above, the impression that I get is:

I can do a Google search.  Google responds with a page of links.  If I click on any link -- any link at all, to any site -- I get a "Server not found" error.

If that is the case, then there is likely a problem with Google redirection.  When you click on a link in a Google search page, it does not take you directly to that site.  Instead, it redirects through a Google server so that they can collect information about your system, and then it redirects to the actual target site.
0
 
MichelineSystems AdministratorAuthor Commented:
BrianB -- turned off temporarily the IE Enhanced Security in order to troubleshoot this.    Just turned off the firewall... to test... and still can't get to any other websites besides google.com, performing a query... getting hits, but can't get beyond this.   Weird.
0
 
MichelineSystems AdministratorAuthor Commented:
Dr. Kahn -- Oh.  Thank you for that info.   I thought when clicking on a link from the search results would bring me directly to the website.   So I tried to go directly to yahoo.com and comcast.net and yahoo.com.   Same 'Server Not Found'.
0
 
MichelineSystems AdministratorAuthor Commented:
Owner sitting here reading over my shoulder and said.... oh, this started happening when I moved the server from my office to my home.   I haven't been able to get on the interest through the server since that time.

There is only one server and one workstation (used to have 5 workstations)
IP configuration is as follows:
Server 2012 Standard
   IP Address:  192.168.5.1
   Subnet Mask: 255.255.255.1
   Default Gateway:  192.168.5.254

   Preferred DNS server:  192.168.5.1
   Alternate DNS Server:  127.0.0.1
0
 
Hello ThereSystem AdministratorCommented:
In your another post you said:
No problem pinging to 8.8.8.8 from the server.

Try to ping 8.8.4.4.
0
 
Hello ThereSystem AdministratorCommented:
Change subnet to 255.255.255.0
0
 
Dr. KlahnPrincipal Software EngineerCommented:
Owner sitting here reading over my shoulder and said.... oh, this started happening when I moved the server from my office to my home.

(flame on)
(hides head in hands)  Well, imagine that.
(flame off)
0
 
MichelineSystems AdministratorAuthor Commented:
Hello There -- Changed subnet to 255.255.255.0 -  same issue.

Successfully pinged 8.8.4.4
0
 
MichelineSystems AdministratorAuthor Commented:
Hello There -- Added additional DNS as suggested -- Yay!   That solved the issue!  Now I'll turn the firewall back on and IE Enhanced Security and see if I can get the Windows Updates to work properly.  I'll post back in a few....
0
 
Hello ThereSystem AdministratorCommented:
Nice.
0
 
MichelineSystems AdministratorAuthor Commented:
Still working on updates.   I should have done a few at a time....  97 items updated.... rebooted and now I have "Failure configuring Windows updates - reverting changes - do not turn off your computer".  :(    So I will reboot once more and attempt to do a few at a time.
0
 
MichelineSystems AdministratorAuthor Commented:
OMgoodness!  Still reverting changes.....   guess it will be awhile.   I'll post more this evening.
0
 
MichelineSystems AdministratorAuthor Commented:
Successfully did ALL the updates!   Thank you so much for your help on this 'Hello There'!  Much appreciated!
0
 
Hello ThereSystem AdministratorCommented:
Awesome!
0
 
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
That's great, but please don't leave the DNS like that. A system shouldn't point to an inside and outside DNS.
0
 
MichelineSystems AdministratorAuthor Commented:
Brian B -- Can you point me to where I can find the 'best practice' on how to set this up for our servers?   I've always had an internal and external DNS configured.   This other setup I'm thinking of has one domain controller (SBS Server 2011 Standard), a data server (Server 2008 R2), and a SQL server (Server 2008 Standard).  This is the current setup:

DC -- SBS Server 2011 Standard:  
192.168.30.60    IP Address
255.255.255.0    Subnet Mask
192.168.30.1      Default Gateway (Netgear router)

192.168.30.60    Preferred DNS server
4.2.2.2                 Alternate DNS server


DATA -- Server 2008 R2
192.168.30.50    IP Address
255.255.255.0    Subnet Mask
192.168.30.1      Default Gateway (Netgear router)

192.168.30.60    Preferred DNS server
4.2.2.2                 Alternate DNS server


SQL - Server 2008 Standard
192.168.30.65    IP Address
255.255.255.0    Subnet Mask
192.168.30.1      Default Gateway (Netgear router)

192.168.30.60    Preferred DNS server
4.2.2.2                 Alternate DNS server

Please don't beat  me up guys... just looking for some guidance.
0
 
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
I'll give you the basic reason as to why you shouldn't have an inside and outside address. If the system switches over and starts using a secondary DNS, it is not going to be able to find any internal resources. Makes sense? An outside DNS server won't know the internal addresses of your network.

Leave the external name lookups to your DC. You DC should only point to itself for DNS and another internal resource.

This article gives some staring points and refers to other RFC items for more reading: https://technet.microsoft.com/en-us/library/cc959288.aspx
0
 
MichelineSystems AdministratorAuthor Commented:
Thanks Brian,   I’ll read it today and make changes this weekend.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.