nbruns
asked on
Fast Internet But Browser Internet Is Slow
Hello all,
I'm baffled over this issue. We just had our Verizon DSL line be switched over to Frontier, as that's happening a lot from what I hear. Since we have a static ip, we were given a new one. Since that change to the new IP, we are having problems browsing the internet. Pages would be slow to come up or not come up at all. We figured it was something to do with Frontier's DNS servers as our VoIP system was working fine as well as FTP and things like that. We could also get to websites just fine using the IP, so DNS is a good bet. We then switched to Comcast (which got us 7 times more speed for only $40 more a month) so we are sitting at about 20 Mbps up and 8 Mbps down per speedtest.net. Got a new IP from Comcast. Upon setting all that up, the same thing is still happening, pages are slow to come up or not at all.
We are on a Windows network here with a domain controller running Windows Server 2008 Standard. Could it be DNS issues on the domain controller? Since that's what our local machines are going through? If it is that machine, what can I do to fix this problem? It's irritating to have fast internet and not be able to use it.
Thanks.
I'm baffled over this issue. We just had our Verizon DSL line be switched over to Frontier, as that's happening a lot from what I hear. Since we have a static ip, we were given a new one. Since that change to the new IP, we are having problems browsing the internet. Pages would be slow to come up or not come up at all. We figured it was something to do with Frontier's DNS servers as our VoIP system was working fine as well as FTP and things like that. We could also get to websites just fine using the IP, so DNS is a good bet. We then switched to Comcast (which got us 7 times more speed for only $40 more a month) so we are sitting at about 20 Mbps up and 8 Mbps down per speedtest.net. Got a new IP from Comcast. Upon setting all that up, the same thing is still happening, pages are slow to come up or not at all.
We are on a Windows network here with a domain controller running Windows Server 2008 Standard. Could it be DNS issues on the domain controller? Since that's what our local machines are going through? If it is that machine, what can I do to fix this problem? It's irritating to have fast internet and not be able to use it.
Thanks.
Go to server responsible for handling DNS and rebuild the cache.
You could also try changing to public DNS servers.
ASKER
@ProtechCT
I'll try rebuilding the cache. I actually stumbled upon that option as I was digging in the server. I'll post back with results.
@askurat1
Changing to public dns on the server or for the router? I tried that on my local machine but doesn't really work as those public dns servers can't resolve to our internal machines.
In addition, I tried using the ping option on our Linksys E2000 router and it actually can't ping some sites (bing.com, msn.com), it comes up with 100% packet loss, but it can ping yahoo.com and google.com just fine.
I'll try rebuilding the cache. I actually stumbled upon that option as I was digging in the server. I'll post back with results.
@askurat1
Changing to public dns on the server or for the router? I tried that on my local machine but doesn't really work as those public dns servers can't resolve to our internal machines.
In addition, I tried using the ping option on our Linksys E2000 router and it actually can't ping some sites (bing.com, msn.com), it comes up with 100% packet loss, but it can ping yahoo.com and google.com just fine.
You would need to do it on the router and in server 2008.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ah ha! Figured it out. You pointed me in the right direction. Being that I'm still learning IT, I was not aware that the DNS IP's from Verizon were inputted as the Forward Zone IP's. All I did was change those to point at the DNS servers Comcast gave us and now browsing is ten times faster. I overlooked that at first but then realized those IP's looked familiar and were old ones. Thanks!
ASKER
The article linked got me right to were I needed to fix the issue. Thanks again.
That makes sense. Wasn't sure if you knew that or not. All though I still think using opendns or some other public dns is better, it is totally up to you.
Thanks!
Thanks!