Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Can't get to google or company web

Posted on 2004-11-01
7
Medium Priority
?
192 Views
Last Modified: 2010-04-19
I am about to go insane trying to solve this problem.  It goes like this...
Installed SBS2003 with 11 clients on network.
all working perfectly for few months
Now for some reason (nothing chnaged I am aware of) I can no longer get to google from the server or workstations
can also not access http://companyweb/ intranet.  Both were working perfectly up to a week ago.
I can ping google.com.au (or .com) but not www.google.com.au ( or .com).
The DNS is setup to use my ISP's dns servers as forwarders and works for all other sites that I am aware of.
an nslookup sessions shows...
C:\Documents and Settings\Administrator>nslookup
Default Server:  server.kiddco.local
Address:  192.168.16.1
www.google.com
Server:  server.kiddco.local
Address:  192.168.16.1

DNS request timed out.
    timeout was 2 seconds.
*** Request to server.kiddco.local timed-out
> server 61.9.208.14
Default Server:  dns1.qld.bigpond.net.au
Address:  61.9.208.14
www.google.com
Server:  dns1.qld.bigpond.net.au
Address:  61.9.208.14

Non-authoritative answer:
Name:    www.google.akadns.net
Addresses:  66.102.7.104, 66.102.7.147, 66.102.7.99
Aliases:  www.google.com


61.9.208.14 is one of my forwarders.  result is the same for any google site.

Companyweb just give me a 11004 error from isa every time I try to access it from any internal station.

Can anyone PLEASE help.
Rossco
0
Comment
Question by:rmarston
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
7 Comments
 
LVL 23

Expert Comment

by:rhandels
ID: 12464244
Hi,

Try adding the providers DNS servers to your own machines DNS setting and make sure you can send DNS request to the internet through yuour firewal (UDP port 53).. If this works, something's wrong with the forwarder setup or the connection of the SBS server.

Also, try to reboot the DNS server and try to do a ipconfig /flushdns on the SBS server (first the flushdns off course..)
0
 

Author Comment

by:rmarston
ID: 12466718
hi,
no problems getting dns requests through isa beacause every other site other than *.google.* and companyweb, works perfectly, so I don't think it is a problem with my forwarder setup.  

DNS server has been started stopped restarted booted, you name it soooo many times it is absurd. have also already tried /flushdns, /registerdns on all machines including server to no avail.

The wierd thing is I can ping google.com but not www.google.com or groups.google.com etc etc.  The IP I get from a google ping is the same as doing it on a pc setup to bypass the sbs2003 box.  This PC gets to google no probs so it is obviously something with the sbs2003 box.  It's DNS server just wont resolve these 2 sites for some reason.

Thanks for the input though.  Any other thing I might try?
0
 

Author Comment

by:rmarston
ID: 12470643
I have found an answer to my problem so question topic can be closed.  Must say I was expecting more response to the problem.  I wonder why hardly anybody responded...  Oh Well. Live and learn.
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
LVL 23

Expert Comment

by:rhandels
ID: 12470657
Hi rmarston,

People only respond if they think they can help, also, we are here for our own fun, we don't get paid to give answers, so if a lot of people are on EE, you will get more responses...

Also, could you please post the solution, so the question can be closed?? If you want to close the question, you can post a close and refund question on the support area on the top right corner...
0
 

Author Comment

by:rmarston
ID: 12477721
My mistake.  I was under the mistaken impression that the large amount of money it cost me to join implied a professional servicebeing offered.  I guess I should have read the fine print prior to forking out my hard earned cash. "caveat emptor". Oh well...

The solution was that my dns service was a little confused with the world for some reason unknown.  The dns server had decided suddenly that it did not like UDP packets greater than 512 being returned from a request.  seems www.google.* is about the only site we use were this is the case as appaerntly EDNSO probes are enabled by default.  The solution to this problem was to load 2003 support tools and use the following command line to disable EDNSO responses to DNS requests.

dnscmd /Config /EnableEDnsProbes 0

It, for some reason known only to a shadowy MS boffin, is case sensitive as I discovered.  That's a zero on the end not a capital o to btw.
Seems odd to me that only googles EDNSO responses were larger than 512 but a quick packet inspection of several DNS requests revealed that to be true in my case.  I have no idea at all why it suddenly decided to behave like this.

That solved the google part of the equation.  The companyweb component was solved by deleting and recreating the cname alias in the forward lookup zone for companyweb and setting it to the FQDN of the server. in my case server.kiddco.local . Hey Presto!
Please lose question and delete points whatever that means...
0
 

Accepted Solution

by:
PAQ_Man earned 0 total points
ID: 14169714
PAQed with points refunded (500)

PAQ_Man
Community Support Moderator
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…
Suggested Courses

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question