bhgewilson
asked on
can't reach finance.yahoo.com
This problem is really wierd. We have a client who just moved. They moved to another suite in the same bldg. The ISP is also the dial tone provider. They did change equipment when they went from one suite to the other. Now that they are moved and everything is settled down they complain that yahoo.com is very slow. I went in and looked to find out that finance.yahoo.com is very slow if it comes up at all. I then tried travel.yahoo.com and sports.yahoo.com. The client has two companies inside one suite. Both have dedicated servers for their own companies running Windows Server, DNS and exchange.
I guess it could be the router but the router tech support (zyxel) says it is not them. The ISP says it is not them. The ISP told me to look at EDNS to see if that could be the problem with the 2003 box. Any suggestions as I am stuck on this one.
Thanks,
Brad
I guess it could be the router but the router tech support (zyxel) says it is not them. The ISP says it is not them. The ISP told me to look at EDNS to see if that could be the problem with the 2003 box. Any suggestions as I am stuck on this one.
Thanks,
Brad
Try a tracert to yahoo.com and see what kind of latency you have between links.
ASKER
latency was consistent when we could and when we could not get to the site. Can you think of anything else?
Lets see if this is simply a DNS issue:
finance.yahoo.com translates to http://216.109.119.237
travel.yahoo.com translates to http://68.142.196.239
sports.yahoo.com translates to http://206.190.35.230
What kind of speed do you get visiting the IP addresses of the sites compared to the domain name?
finance.yahoo.com translates to http://216.109.119.237
travel.yahoo.com translates to http://68.142.196.239
sports.yahoo.com translates to http://206.190.35.230
What kind of speed do you get visiting the IP addresses of the sites compared to the domain name?
ASKER
same response. The site will eventually come up but when it does after about five minutes all of the pictures are missing like the gateway took a hiccup and it used cached settings.
However saying that the sites are smoking fast today with nobody there.
However saying that the sites are smoking fast today with nobody there.
ASKER
CLOSE question.
We had DNS on router for B subnet mask. Changed to "C" and it worked.
We had DNS on router for B subnet mask. Changed to "C" and it worked.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.